XOOPS: XOOPS 2.3.0 RC 发布

发布者: phppp于 2008/7/28 4:10:00 16173次阅读
XOOPS 开发团队很高兴地宣布发布XOOPS 2.3.0 RC。
XOOPS 2.3 版本的目标是将现有的2.0和2.2分支合并,并为我们的下一代系统XOOPS 3.0搭建桥梁。
通过XOOPS 2.3版本,用户将能够了解一些即将在XOOPS 3.0中可用的新特性,同时开发者可以更好地理解XOOPS的发展方向,设计师可以了解未来将支持哪些特性。
将尽可能保证前后兼容性。为2.0.*和2.2.*编写的模块将与2.3兼容;为2.3开发的应用程序将自动与XOOPS 3.0兼容。
鼓励开发者基于XOOPS 2.3编写他们的应用程序模块,以便他们可以整合一些新特性,并确保轻松迁移到XOOPS 3.0。
RC版本将冻结此版本的关键特性,并在此特定版本中引入一些小的改进。

Sourceforge 仓库下载。

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. 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; - Permissions for access to user profile page is configurable. 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 RC ----------------------------------- Your can get this release package from the sourceforge.net file repository. Both .zip and .gz archives are provided. Installing XOOPS 2.3 Beta ----------------------------------- 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 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. Access/upgrade/,并遵循以下说明。7. 按照说明更新您的数据库 8. 从您的服务器上删除升级文件夹。从此版本的XOOPS(2.0.7至2.0.13.2)升级(使用完整包):1. 将“升级”文件夹移动到您的本地机器上的“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,从模块管理界面更新“系统”模块。文件完整性检查 ----------------------------------- XOOPS 完整包附带一个脚本来检查是否所有系统文件都正确上传到服务器。要使用它,请按照以下说明操作:1. 将位于 XOOPS 包根目录中的 checksum.php 和 checksum.md5 文件上传到您的 XOOPS 服务器文件夹(放置在 mainfile.php 旁边)。2. 使用浏览器执行 checksum.php。3. 如果需要,重新上传缺失或损坏的系统文件。4. 从您的服务器上删除 checksum.php 和 checksum.md5。模块 ----------------------------------- 包中除了系统模块外不包含任何模块。请您浏览 XOOPS 模块仓库以获取更多模块。注意:由于正在构建新的仓库,当前仓库可能不是最新的,请访问开发者网站以确保您使用的是最新版本的模块。我们还强烈推荐安装 Protector 模块,这将为您的网站带来额外的保护和日志记录功能。如何贡献 ----------------------------------- 缺陷报告: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 开发团队