Hi,
Thanks for pointing me where to look for the language modules, I kinda thought maybe I was overlooking something obvious. I'm still pretty new to XOOPS, that's my excuse (sheepish grin).
So in this case, it was my oversight in not looking in the obvious place, and once there I found the files well organized.
I still think the modules listing could be better organized. It's very good of the authors to release their modules etc for the rest of us to use, and imposing some naming conventions may not be a good idea, especially as in some cases the category or main keywords may not fit some narrow definition.
An alternative suggestion, maybe a list of alias names that point to the modules, then these alias names could be categorized, eg
calendar modules
menu modules
Unfortunately, I don't have the time or knowledge to do this, but we need to avoid the situation that happened to Red Hat users and RPM hell.
I think that given the ease of installation of XOOPS and modules along with boldly applying OO concepts by the core team and others, we will see XOOPS grow in popularity compared to say eXOOPS and Postnuke etc. so the number of modules will just grow and grow.
rrbert

Hi,
I'm looking for the French language pack for xoops-2.0.6
There is some fairly good documentation for the multilanguage pack XOOPS_ML_v1_3.zip on how to configure it for various languages, the example language being French. The author says that of course, for this to work, you also need the French language pack. I guess if I could read French, I could find it on some French language XOOPS site, but I haven't found it yet.
Anyhow, this seems to be a growing problem (finding the relevant module). There is already some structure on the downloads page (Themes, Modules, Languages, etc), but I think more is needed. For instance, we could have a category Superceded ( or Old). Most people are interested in the current stable release, so when an author releases a new version, they move the older version out. This may help reduce some clutter.
Perhaps somebody could write some guidelines on module naming conventions, and request that authors of modules please try to choose suitable names and follow some conventions for the filename. For example, an alphabetical listing of modules lists:
A simple flash counter
Advanced Contact Module
Agenda-X 2.1
Well, I think Agenda-X 2.1 is probably well named and belongs in the A's, but the other 2 may be better named Counter-Flash and
Contacts-Advanced or something.
My suggestion is:
Keyword-[optional extra word]-v[version number]
and also encourage similar consistency in filenames.
Thanks,
rrbert

7dana problems fixed, thanks
Hi, thanks for the suggestions, it seems I was not carrying out the step of updating the modules (or maybe update module .html files wasn't set to yes). Anyhow, I dropped my database, did a fresh install, and now religiously update the modules after every theme change.
The 7dana themes work fine, although I still have to fix their permission problems.
rrbert

7dana-round theme also gives blank page.
Hi, I tried the suggestion of checking the file permissions.
Sure enough, all the permissions were 600, so I changed them to 644, (755 for directories), but still get a blank page. I can't see anything, so I can't log in to set the theme back to the default.
I guess I'll just drop my database and do a clean install.
Maybe this is a problem with 7dana themes, I think I'll avoid them in future.
rrbert

Hi Chiayi,
I had the exact same problem I think. At first, after following some false leads, I turned on register-globals(in php.ini), but it didnt help and is not necessary.(Its best to leave register-globals = Off)
I then did a complete re-install, and this time noticed that 2 of the install screens actually give a choice of 3 buttons to press.
Screen 'check PATH & URL' says click the button below to confirm your settings (previously I just clicked the next button) so I clicked the center button labelled 'reload'.
Anyhow, it dropped me back to the beginning of the install, then I just click through all the screens, because it remembers the settings, and I was able to log on no problems.
(by the way, this is a test install on my own machine, so no firewall, but its not directly in htdocs, but in htdocs/xoops)
rrbert