What's New for Users ----------------------------------- Some of the new features that might interest users: - Default character set encoding has been changed to UTF-8; - Enabled "auto login" or "remember me"; - CAPTCHA is enabled for registration and comment system; - Block clone enabled so that webmasters have more flexibility; - XOOPS editor package is provided and most visual editors are avilable, e.g. FCKeditor, TinyMCE, etc.; - Side-wide editor; - Mask is added for start page; - Implemented new installer with user experience improvement experiments; - Upgrading scripts from 2.0* and 2.2* to 2.3; - Permissions for access to user profile page is configurable; - Extensible Profile module; - Private Messages Module; - Extended DHTML as default, with inline preview enabled; - EXM/ThAdmin Admin GUI as options. What's New for Developers ----------------------------------- 1 Improved XOOPS ORM by enabling extensible persistable object handler: - The improved persistable object handler supports almost all common methods for database access and data treatment, so that developers do not need to write their own classes or methods; - Custom handler is supported. Developers can add their own handler if they want more functionality or to replace XOOPS native handlers. 2 Improved text sanitizer: - Custom extension is supported. Developers can add new filters or methods to sanitizer based on their specific needs. - Built-in extensions, which can be disabled or enabled (e.g. for Flash, YouTube, images, Wiki, syntax highlight, text filter, etc.) - Combined with improved persistable object handler (see above), text input from users will be filtered automatically for security considerations. 3 Custom Frameworks support: - Module developers can add their own library or frameworks (located in XOOPS_ROOT_PATH/Frameworks) which can be shared by other modules. - PEAR, Geshi have been provided as custom libraries in Frameworks. - Once the code inside Frameworks is proven stable and valuable, they will be adopted by XOOPS core and moved into XOOPS core package. This way we can build a standard, efficient channel for third-party developers to contribute. 4 XOOPS editor packages are now supported officially: - A XoopsEditor handler is built to accept third-party editors; - Three editors, including Textarea, Dhtmltextarea, and Extended Dhtmltextarea are provided in XOOPS core. FCKeditor, TinyMCE, Koivi are now provided as third-party add-ons. 5 XOOPS CAPTCHA is built into XOOPS core: - CAPTCHA has been added to registration and comment forms. - Module developers can add CAPTCHA very easily to their applications. 6 XOOPS Control Panel GUI is introduced: - Old administration interface has been kept as legacy - A new interface is designed, although very rough at this stage - Custom interfaces are allowed, ThAdmin by MusS and Kris is the first one introduced 7 XOOPS file and folder engine is added, based on CakePHP. 8 XOOPS Cache engine is built based on CakePHP. 9 Some other improvements and new resources: - XoopsLocal for localization; - XoopsLoad emulating SPL autoload in PHP5; - XoopsUtility as a collection for miscellaneous methods used by XOOPS; - Block clone feature is activated to save module developers' efforts; - Enabled character set and collation support for MySQL 4.1+; - Upgraded Smarty to 2.6.19; - Upgraded phpmailer to 2.0.0; - Added XOOPS data and library folders for forward compatibility with XOOPS 3.0; - Added XOOPS_TRUST_PATH for compatibility with some modules, e.g. protector 10 For more changes, please check changelog.txt What's New for Theme/Template developers ----------------------------------- 1 Rel attribute for anchors is now supported. Developers/designers are encouraged to use (X)HTML compliant "rel" attribute instead of "target". 2 Control Panel GUI handler is introduced thus designers now get the power to make beautiful backend interfaces. System requirements ----------------------------------- PHP: Any PHP version >= 4.3 (PHP 4.2.x may work but is not officially supported, PHP 5.0+ is strongly recommended) MySQL: MySQL server 3.23+ (MySQL 5.0+ is strongly recommended) Web server: Any server supporting the required PHP version (Apache highly recommended) Downloading XOOPS 2.30 Final ----------------------------------- Your can get this release package from the sourceforge.net file repository. Both .zip and .gz archives are provided. Installing XOOPS 2.30 Final ----------------------------------- 1. Copy the content of the htdocs/ folder where it can be accessed by your server 2. Ensure mainfile.php and uploads/ are writable by the web server 3. For security considerations, you are encouraged to move directories xoops_lib (for XOOPS libraries) and xoops_data (for XOOPS data) out of document root, or even change the folder names. 4. Make the directory of xoops_data/ writable; Create and make the directories of xoops_data/caches/, xoops_data/caches/xoops_cache/, xoops_data/caches/smarty_cache/ and xoops_data/caches/smarty_compile/ writable. 5. Access the folder where you installed the htdocs/ files using your web browser to launch the installation wizard We also highly recommend the installation of the PROTECTOR module which will bring additional security protection and logging capabilities to your site. To install protector module with a fresh new installation of XOOPS 2.30, copy /extras/mainfile.dist.php.protector to /htdocs/mainfile.dist.php BEFORE installing XOOPS. To install protector module with upgrading from a previous version to XOOPS 2.30, copy /extras/mainfile.dist.php.protector to /upgrade/upd-2.0.18-to-2.3.0/mainfile.dist.php BEFORE upgrading XOOPS. Upgrading from a previous version ----------------------------------- Upgrading from XOOPS 2.0.* above 2.0.14 and 2.2.* (using the full package) 1. Move the "upgrade" folder inside the "htdocs" folder (it's been kept out as it's not needed for full installs) on your local machine 2. Delete htdocs/mainfile.php, htdocs/install/, htdocs/cache/, htdocs/extras/, htdocs/template_c/, htdocs/themes/ and htdocs/uploads/ from the "htdocs" folder on your LOCAL machine 3. Upload the content of the htdocs folder on your LOCAL machine over your existing files on your server 4. For security considerations, you are encouraged to move directories xoops_lib (for XOOPS libraries) and xoops_data (for XOOPS data) out of document root, or even change the folder names. 5. Make the directory of xoops_data/ writable; Create and make the directories of xoops_data/caches/, xoops_data/caches/xoops_cache/, xoops_data/caches/smarty_cache/ and xoops_data/caches/smarty_compile/ writable. 6. Ensure the server can write to mainfile.php 7. Access使用浏览器访问 /upgrade/，并按照以下步骤操作：8. 按照说明更新您的数据库 9. 再次对 mainfile.php 设置写保护 10. 从您的服务器中删除升级文件夹 11. 从模块管理界面更新 "system" 模块，建议也更新其他模块。从任何XOOPS版本（从2.0.7到2.0.13.2）（使用完整包）升级：1. 将 "upgrade" 文件夹（由于它对于完整安装不是必需的，所以暂时移除）移动到您本地的 "htdocs" 文件夹中 2. 从您本地的 "htdocs" 文件夹中删除 htdocs/mainfile.php, htdocs/install/, htdocs/cache/, htdocs/extras/, htdocs/template_c/, htdocs/themes/ 和 htdocs/uploads/ 3. 将您本地的 "htdocs" 文件夹的内容上传到您服务器上现有的文件中 4. 从您的服务器中删除以下文件夹和文件（它们属于旧版本）：* class/smarty/core * class/smarty/plugins/resource.db.php 5. 确保服务器可以写入 mainfile.php 6. 为了安全考虑，建议将 xoops_lib（为XOOPS库）和 xoops_data（为XOOPS数据）文件夹从文档根目录移动出来，甚至更改文件夹名称。 7. 将 xoops_data/ 文件夹设置为可写；创建并将 xoops_data/caches/、xoops_data/caches/xoops_cache/、xoops_data/caches/smarty_cache/ 和 xoops_data/caches/smarty_compile/ 文件夹设置为可写。 8. 访问使用浏览器访问 /upgrade/，并按照以下步骤操作 9. 再次对 mainfile.php 设置写保护 10. 从您的服务器中删除升级文件夹 11. 从模块管理界面更新 "system" 模块，建议也更新其他模块。对于非UTF-8站点的升级：XOOPS 2.30 已采用UTF-8作为默认字符集。然而，将现有网站从非UTF-8字符集转换为UTF-8可能会出现一些问题。在解决这个问题之前，如果您不是经验丰富的用户，在升级现有网站时建议您进行以下设置：- 在升级过程中，在 "数据库字符集和排序规则" 步骤中选择 "不更改" 选项 - 如果在新的全局.php 文件中将它更改为 UTF-8，请在 /languages/yourlanguage/global.php 中修改以使用已更改的 _CHARSET 值

定义('_CHARSET', 'UTF-8');

升级XoopsEditor包：在XOOPS 2.30最终版包中包含五个编辑器：dhtmltextarea和用于纯文本的textarea，fckeditor，tinymce和koivi用于所见即所得的HTML。由于fckeditor和tinymce编辑器中存在一些目录结构更改，建议在上传新插件之前删除现有插件。如果您在模块中使用fckeditor，请按照/fckeditor/modules/中的文件修改模块特定的配置，尤其是如果您使用“article”模块。文件完整性检查 ----------------------------------- XOOPS完整包随脚本发布，用于检查所有系统文件是否已正确上传到服务器。使用方法如下： 1. 将XOOPS包根目录中的checksum.php和checksum.md5文件上传到您的XOOPS服务器文件夹（将它们放在mainfile.php旁边）。 2. 使用浏览器执行checksum.php 3. 如有必要，重新上传丢失或损坏的系统文件 4. 从您的服务器上删除checksum.php和checksum.md5 Modules ----------------------------------- 本次发布仅包含“与系统相关的模块”。如果您需要额外的功能，请浏览XOOPS模块存储库。注意：由于正在构建新的存储库，当前存储库可能不是最新的，请访问个人开发者的网站以确保您使用的是模块的最新版本。如何贡献 ----------------------------------- Bug报告： http://sourceforge.net/tracker/?group_id=41586&atid=430840 补丁和增强： http://sourceforge.net/tracker/?group_id=41586&atid=430842 功能设计： http://sourceforge.net/tracker/?group_id=41586&atid=430843 发布公告： https://lists.sourceforge.net/lists/listinfo/xoops-announcement XOOPS开发团队 2008年9月20日