Maybe a short followup post, and explain my motivation.
Their are two types of importent data, one the content, second the date. All websites powered by xoops in languages other then English are forced to use numeric date notations (eg 12-02-2007), while notitions with real day and month conversions would aprove the users experience (seeing wednesday instead of only 12). It's hard for me to explain it in English, let me know if my issue isn't clear enough.^^
In 2006 I reported a bug in Xoops that there is a real problem in date notations in languages other then English. The bug was confirmed by Marcan and Mith, but Skalpa never had the time to review/solve the problem.
Short explenation:
When dates are called like: Wednesday 12th of May, you can't let Xoops translate it into Dutch for example (it would be displayed/renamed to "woensdag 12 mei"). We have tested it with other languages/server configurations etc, but it seemed the main problem lies in the Xoops core.
SF bugreport:
http://sourceforge.net/tracker/index.php?func=detail&aid=1499945&group_id=41586&atid=430840
Xoops forum thread:
http://www.xoops.org/modules/newbb/viewtopic.php?topic_id=42500&viewmode=flat&order=ASC&type=&mode=0&start=0
edit: typo
Oh I understand now steve. Yes this could work.
Anyway, again :
Quote:
So the best thing is probably to accept that our mainfile on the SVN will get changed from time to time, but we can live with it. We can always revert the changes, it's no big deal...
I rather like how Nekro arranged them - separating fixes, etc - so it is easier to read.
We've already had some collisions on committing changes and the changelog is suffering the most. We need some sort of agreement on how to handle this so we keep this from getting too crazy.
marcan - I only export to another directory when I start, not for every edit. I make changes and test in my copy and when I am satisfied, I make the changes to the sandbox copy and commit.
Leaving the mainfile out of the distribution is OK with me, as long as the installation processes still work.
Just have to try and remember ... just like I need to remember to comment any changes
Quote:
I have only worked with SVN/CVS a little, so I export a copy of my sandbox to my local server for testing. When I'm happy with it, I merge the changes into my sandbox copy, then commit to the repository.
Quote:
Dave_L wrote:
You realize, of course, that we'll be talking about you behind your back.
You realize, of course, that we'll be talking about you behind your back.
WOW! #6 is Stunning! I love it!
Quote:
Dave_L wrote:
Another approach could be to not include a mainfile.php in the distribution package; the file would be created during installation. But that introduces another complication: the directory containing mainfile.php would have to be writable.
Maybe Steve's method is the only way of doing it. That's my method too. It also solves the issue of temporary changes for testing and debugging.
Another approach could be to not include a mainfile.php in the distribution package; the file would be created during installation. But that introduces another complication: the directory containing mainfile.php would have to be writable.
I'm just being paranoid. More than anything, I'm too lazy to learn yet another chat system.
Well Jmorris, I can tell you this, it's more safer to close your port 80 and just stick to the irc protocol^^
Excellent James,
Try to bring him to work with us to include this in ImpressCMS.
I know this is a bit premature, but I'll mention it anyways because I'm currently working on it.
I'm working with the developer of http://www.oiopublisher.com/ on squashing any bugs and improving the XHTML rendering of the system. It's a very promising ad management system that supports the following ad formats:
* Banners/Buttons
* Global/Per Post Text Links
* Paid Posts
* Custom Ad Services
* Modular backend with "Conversation" module
* Google compliant with a nofollow option
Simon (the Dev) is very much interested in opening the development and extending the application to other platforms. He has some excellent concepts lined up for the application and I think it would be an ideal candidate to replace the outdated banner manager in the core as a "modular" replacement.
I'll have more information on this soon. For now, we're working on the latest release which will include a "conversation" module for social blogging.