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 datafile 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. What's New for Users ----------------------------------- So far the 2.3.0 Alpha does not give user many new features although it has great potential of adding new features very easily. 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.; - Mask is added for start page; - Implemented new installer with user experience improvement experiments What's Next ----------------------------------- - XOOPS Design Team will continue to improve themes and Control Panel interface which is not completed yet - Developers will collect feedback and make the package stable as soon as possible - Modules and add-ons will be taken care, e.g. profile module, PM module, frameworks, etc. System requirements ----------------------------------- PHP Any PHP version >= 4.3 (PHP 4.2.x may work but is not officially supported) MySQL MySQL server 3.23+ Web server Any server supporting the required PHP version (Apache highly recommended) Downloading XOOPS 2.3 Alpha ----------------------------------- Your can get this release package from the sourceforge.net file repository. Both .zip and .gz archives are provided. Installing XOOPS 2.3 Alpha ----------------------------------- 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 Upgrading from a previous version ----------------------------------- Upgrading from XOOPS 2.0.* above 2.0.14 (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. Access使用浏览器访问 upgrade/，并按照以下步骤进行。7. 按照指示更新您的数据库。8. 从您的服务器上删除升级文件夹。从 2.0.7 到 2.0.13.2 版本的任何 XOOPS 升级（使用完整包）：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. 访问/升级/ 使用浏览器，并按照说明进行操作 9. 再次对 mainfile.php 写保护 10. 从您的服务器删除 upgrade 文件夹 11. 从模块管理界面更新 "系统" 模块 从 XOOPS 2.2.* 升级（使用完整包）将在下一个版本中可用。文件完整性检查 ----------------------------------- 完整的 XOOPS 包随附一个脚本，可用于检查是否所有系统文件都已正确上传到服务器。要使用它，请按照以下说明操作： 1. 将位于 XOOPS 包根目录中的 checksum.php 和 checksum.md5 文件上传到您的 XOOPS 服务器文件夹（将它们放在 mainfile.php 旁边）。 2. 使用浏览器执行 checksum.php 3. 如果需要，重新上传缺失或损坏的系统文件 4. 从您的服务器删除 checksum.php 和 checksum.md5 揭示空白页面回溯日志 ----------------------------------- 当遇到致命错误阻止其运行时，XOOPS 将显示一个基本的错误页面。为了帮助您诊断错误的原因，此页面包含一些默认隐藏的附加消息。要显示它们，请使用您的浏览器 "全选" 功能（对于大多数浏览器，您可以使用 "Ctrl+A"）。 模块 ----------------------------------- 这些包除了系统模块外，不包含任何模块。我们邀请您浏览 XOOPS 模块存储库以获取一些模块。注意：由于正在构建新存储库，当前存储库不是最新的，请访问 开发者网站 确保您正在使用模块的最新版本。我们还强烈建议安装保护模块，这将为您的网站带来额外的保护和日志记录功能。令人兴奋的消息：更多开发者变得活跃，最近有新的开发者加入开发团队，随着 XOOPS 2.3.0 测试版发布，将带来更多功能和模块。如何贡献 ----------------------------------- 错误报告：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 开发团队