OK. I few information about Joomla and Xoops.

1. 'Menu' system in Joomla could be managed in administrator mode. Also, a few of transmenu from third parties. So, lets start a group to develop a menu module which could be have ways to show in horizontal or vertical with dropdownlist or transmenu features.

2. Multilingual, xlanguage in XOOPS is better, IMHO, additional language by using joomfish can only be maintained by administrator. I will suggest joomla to have a modules like xlanguage.

3. module upgrade, XOOPS is best, the flow is designed carefully and best of best that all CMS should study.

4. joomla components are lack of themes selection. webmaster have to change coding of .php files but easy still.

5. XOOPS site themes is limited in core, coding built on left, right, centerleft, centerright. It is not free for managing places. e.g. top or bottom of header for a transmenu. Well, joomla is good enough. That is why some devs doing transmenu for them.

6. Search, XOOPS provided a way for modules to join and use the core search, so that no separated search needed. However, for some specified modules, a detail specified search may be necessary like shopping and forum.

7. XOOPS makes use smarty where we have to put a lot of data in array. Well, it is not using passby reference to template. Loading crisis will exist if you 're going to make a hot site. Joomla makes use php as php is a template itself. (more disscusion about this could be found in forum and post there if you wanted. )


So, a few points to make this thead useful.

Under XOOPS 2.2.3a, couldnt check $xoopsModuleConfig['allow_register'] outside module such as in /user.php

This index is in module profile, while it seemed that it wasn't loaded in user.php, so checking is unavailable.

Is there a correct way to check the setting in user.php?

Then, will XOOPS include the data porting between database from MySQL to PDO or Oracle and vice versa?

Quote:

Thanks JMorris, its not easy to get opinions here. Only two after 24 hours. Devs are busy.

Well, LazyBadger, thanks also for your information. But wish you could make it with more respect.

Suddenly, I have two more questions to ask.

1. Which one provides an easier coding to develop module by a fresh well-trained php devs (study time to catch the coding standard for it) AND an experienced(over one year) XOOPS devs for XOOPS module / mambo devs for mambo... component?

PS. IMO, component should mean something, such as "Notifications", that could be called and used in core and modules. But mambo seems re-define it.

2. Which one provides faster running system in coding and database optimization viewpoints?

mCity

Quote:A User view!

Quote:A Technical webmaster view!

Thanks! Morris!
You showed us two points of view from Users AND Technical Webmasters.

Well, as a technical webmaster, I am thinking trying it and port it to be a XOOPS modules with very high quality themes for that modules

Making use their themes technique for our own module would be very interesting. Don't forget XOOPS could set which module for front page. Yes, then, it is for the site already.

The experts are in this thread

Or, you may find more experts in searching with keyword "SEO", that is the way I found you.

I backuped the php of XOOPS and database of MySQL 4.0 and move to new Mandrake10.2 with MySQL 4.1 and now I got a front page with no blocks.

Now searching around and got you...

Your problem may be caused by MySQL 4.1
I got the problem and so search anyone using MySQL 4.1 with similar result.

thanks irmtfan
you're right! I forgot update it.
and now, fixed.