XOOPS: XOOPS 2.3.0 测试版 1 发布
发布者: phppp于 2008/7/6 2:10:00 已被阅读 12496 次XOOPS 2.3.0 测试版 1 发布说明
---------------------------------------
XOOPS 开发团队很高兴宣布发布 XOOPS 2.3.0 测试版。
XOOPS 2.3 版本的目标是将现有的 2.0 和 2.2 两个分支合并,并为下一代的系统 XOOPS 3.0 建立桥梁。
使用 XOOPS 2.3 版本,用户可以了解一些将在 XOOPS 3.0 中可用的新功能,而开发者可以更好地理解 XOOPS 开发的方向,设计师可以了解未来将支持哪些功能。
将尽可能保证 backward 和 forward 兼容性。为 2.0.* 和 2.2.* 编写的模块将在 2.3 上运行;为 2.3 开发的应用程序将自动与 XOOPS 3.0 兼容。
鼓励开发者将应用程序模块写成 XOOPS 2.3,以便它们可以集成一些新功能并确保轻松迁移到 XOOPS 3.0。
一些在测试版中带来的特定改进:XOOPS 2.2 的升级脚本、与 XOOPS 3 的向前兼容性和全局 WYSIWYG 编辑器。
下载 从 Sourceforge 仓库 XOOPS 2.3.0 测试版 1 核心包和附加包
适用于 Smarty 缓存路径的快速修复
/class/template.php,行 #68,改为
$this->cache_dir = XOOPS_VAR_PATH . "/caches/smarty_cache";
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 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.; - Side-wide editor; - Mask is added for start page; - Implemented new installer with user experience improvement experiments 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 Beta ----------------------------------- Your can get this release package from the sourceforge.net file repository. Both .zip and .tgz 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