xThemes 1.5 beta has been released and is available for download from the downloads section of Xoops Mexico. This new version is a complete rewrite of the module, which improves performance and gives greater functionality, while allowing the design and development of better XOOPS themes. It is very important to know that this version is not compatible with earlier versions of xThemes. This means that themes developed for earlier versions will not work in this version because the framework has been changed radically.
Among the new features available to xThemes 1.5 are:
✔ Multi-theme support. ✔ New multi-level system menus that can be integrated into the theme. ✔ New configuration system for themes that allows to develop themes more quickly and a more easily uses. ✔ Better integration of the themes with the whole system. ✔ Support for theme plugins and smarty plugins. ✔ Global availability of xThemes classes and methods. ✔ Preview themes before being installed. ✔ Multi-language support for themes. This means that items can be easily translated.
The comments are owned by the author. We aren't responsible for their content.
Re: xThemes 1.5 Beta has Arrived!
Cool! Looking forward to testing it!
Re: xThemes 1.5 Beta has Arrived!
Great Work!
Re: xThemes 1.5 Beta has Arrived!
oops !
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'NOT EXISTS `xt_menus` ( `id_menu` int(11) NOT NULL AUTO_INCREMENT, `theme` i' at line 1
Re: xThemes 1.5 Beta has Arrived!
Error: Fatal error: Call to undefined function __() in E:\xampp\htdocs\xoops255\modules\xthemes\xoops_version.php on line 31
Re: xThemes 1.5 Beta has Arrived!
Please mention your XOOPS and PHP version.
I assume, you're using XOOPS 2.5.5 and PHP 5.2.x, correct?
Re: xThemes 1.5 Beta has Arrived!
This error happen when rmcommon has not been installed previously... however I've included the prevention to avoid this error for next update (in a few hours)
About MySQL error... this problem may be caused by version of MySQL. Don't worry, the fix is ready for next update...