Posted on: 2012/8/21 3:53
I have some opinions about all the parts of this alpha release but now I should response about the new extensions concept quickly.
actually, they are not extensions at all but as core team stated they are "system extensions" which is very very confusing and make all people wrongly think they are something like joomla extensions and they are different from other modules. But really there is no difference between them and other common xoops modules other than a cosmetic feature
that i will explain below.
The core team decided from a long time ago to create new modules based on the current features in system module. the examples are profile and pm.
A more accurate and comprehensive definition for them is: "modules that make old hardcoded features in system module extensible and modular". We are all familiar with them because profile and pm modules are "system extensions" modules for years. there is no difference between these new modules in 2.6 alpha and profile, pm modules.
Turning these features in system module to stand alone modules will free system/core from many unrelated duties and more importantly open the way for module developers to work on them without touching core files.
they have xoops_version.php file and install/uninstall just like other modules. therefore the true location for them is inside modules directory.
The only thing that make everybody think they are different is the different menu in admin (just a different look) which is nothing more than a cosmetic feature.
I mean it just show
them in a different menu while there is nothing different in the under layer coding.
and that is because of adding 2 options in xoops_version.php.
$modversion['extension'] = 1;
$modversion['extension_module'] = 'system';
by adding those 2 options in any module you can turn it to an extension!
eg: I add to newbb and force it to be as a system extension!!!!!!(very funny)
I was blind because i never imagine that this little feature will bring these kind of misunderstanding in the whole xoops.org forum.
So those 2 options in xoops_version.php is seems very confusing and its little nice looking advantage is not necessary in compare with a lot of confusing that will bring up in 2.6.
Anyway we dont need any extensions like joomla extensions in xoops. one of the xoops few
power points over other CMSs is its simplicity. you have core - module - theme and a new comer will work with them just fine. If we add extensions concept it will be more complicated for people especially newcomers.
Also im not the enemy of cosmetic features like that. The admin menu of 2.6 is very nice and will attract new comers but i as a webmaster need an understandable admin more than a nice looking one.
Also 100 features is missing in core and 1000 is missing in modules. whenever we could add those features we can put time and add cosmetic features.
I will talk about other parts of this release today.
just one thing: this 2.6 will move xoops 10 years forward because i can not remember any release with this huge development from 2.0.18 until now.
Install gives a blank page after step 10, all other steps including step 10 don't give any errors or missing extentions. It's on a shared hosting server.
in this url:
same configuration. somebody should investigate this bug.
Yes, With version 1.7.2 blocks are moved
Adding a new feature: System Extensions. Some parts of the system module are now separate "system extensions" (eg. Banners, Avatars, Smilies).
An interesting mistake.
The core team forgot to add those 2 options to banners module. so now you have banners module in the module menu while you have other modules in extension menu!!!!
In the news article it states:
" Some modules in the Admin will also become Extensions (eg. Protector). All these Extensions are runing as modules, but they cannot be renamed, and they will be shown in a separate menu module"
Core team create these module and decide to make them just a very basic module. you as module developer can create your own modules. eg: red_banners, red_smilies, red_avatars, ...
We dont have any developments in xoops modules in the past 5 years so now IMO by releasing xoops 2.6 we dont have any module for this brand new core.
The below activities are not development:
- make old modules compatible with new core release and php and mysql
- add module admin class to old modules (cosmetic feature)
- create basic modules that have not features of the old modules. xoops dont need any more basic module. we just need full features.
So we need a real development in modules for 2.6.