XOOPS 2.5.6 Final Released

The XOOPS Development Team is pleased to announce the release of XOOPS 2.5.6 Final.

This release is focused on making XOOPS 2.5.6 compatible with PHP 5.4.x, on security enhancements, and on updating external libraries to their latest versions:

- Smarty 2.6.27- TinyMCE 3.5.8- jQuery 1.8.3- jQueryUI 1.10

Since this version includes security fixes, it is highly recommended to update to this version ASAP!

See the Changelog for more details.

IMPORTANT NOTE: -----------------------------------Due to changes related to security, it might happen that in one or two modules saving of the Permissions in Admin might not work. We are finalizing the Basic Module Pack, where all modules have been tested on XOOPS 2.5.6. Please check the News on XOOPS Website for a special announcement about the updated modules, or ask on the XOOPS Forums. Or you can read more detailed information about how to fix it yourself in /docs folder in the file: "fixing_permissions.txt"

Please post and discuss all issues related to this release in this Forum

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, and change the folder names. 4. Ensure that directories: - uploads/, - uploads/avatars/ - uploads/images/ - uploads/ranks/ - uploads/smilies/ - xoops_lib/modules/protector/configs/ and files: - mainfile.php and - include/license.php are writable by the web server 5. Access the folder where you installed the htdocs/ files using your web browser to launch the installation wizard

Installing Protector in XOOPS-----------------------------------We also highly recommend the installation of the PROTECTOR module which will bring additional security protection and logging capabilities to your site.

Upgrading from a previous version-----------------------------------

Upgrading from 2.5.5 to 2.5.6 Final:

1. Get the right update package from the sourceforge file repository 2. Overwrite files in XOOPS directory on your server with the content of /htdocs * make sure that you copy the content of /xoops_lib to whatever directory you keep it on the server now (it should be your current XOOPS_TRUST_PATH directory), then delete the /xoops_lib directory. There can NOT be two directories with the content of /xoops_lib 3. Go to www.yoursite.com/upgrade and run the Upgrade from there. Once done, delete the folder /upgrade 4. If not done as part of the Upgrade above, run Update af the the "System" module from the modules administration interface. Other modules, especially "Profile", "PM", and "Protector" are recommended to update as well

Upgrading from previous versions older than 2.5.5 (Full Update):

0. Verify the system requirements, in particular the version of PHP. Backup your XOOPS database and site directory. (There are several ways to do these actions, which are discussed elsewhere.) Turning your site off is optional. Change the permissions on mainfile.php and /include/license.php to be writable, for example: File Normal For upgrade mainfile.php 400 700 /include/license.php 444 777 Get the XOOPS 2.5.6 package from the SourceForge file repository. 1. In the upgrade package folder, move the "upgrade" folder inside the "htdocs" folder, if it's not already there. Remove the install folder from the "htdocs" folder, if it's there. Remove the mainfile.php file from the "htdocs" folder, if it's there. If you've moved the xoops_data and xoops_lib folders outside your site's root directory, move these folders out of the "htdocs" folder in the upgrade package folder. 2. Delete the /modules/system directory on your current XOOPS site (to get rid of any old unnecessary files). 3. Overwrite the files in the XOOPS directory on your current XOOPS site with the content of "htdocs" folder of the upgrade package. (There are several ways to do this action, which are discussed elsewhere.) As noted above, if relocated, overwrite the files in your current xoops_data and xoops_lib with the content of those in the upgrade package. 4. If you have Protector previously installed, open the "mainfile.php" file , and remove the Pre-check and Post-check lines (if they exist): include XOOPS_TRUST_PATH.'/modules/protector/include/precheck.inc.php' ; include XOOPS_TRUST_PATH.'/modules/protector/include/postcheck.inc.php' ; 5. At your site's address (URL), login as administrator. Access /upgrade/ with a browser, and follow the instructions (and any for updating your XOOPS database). After all updates have been applied (green checkmarks), note the link in the Updater to update the "system" module, and do so. 6. Delete the "upgrade" folder from your site's "htdocs" directory. 7. Update (reload) other modules, especially "Profile", "PM", and "Protector," if necessary. 8. Change permissions on the files noted above back to their normal state. 9. Turn your site back on, if you turned it off earlier.

Debug information display level-----------------------------------

Since XOOPS 2.3.1 debug information display level is enabled as a temporary solution for 2.3* to show debug information to different level of users: to all users, to members or to admins only.The configuration can be set in /xoops_data/configs/xoopsconfig.phpAs a default, the display level is set for 2 (Admin only).

Files integrity check-----------------------------------

The full XOOPS package is released with a script able to check if all the system files have been correctly uploaded to the server. To use it, follow these instructions:

1. Upload the checksum.php and checksum.md5 files located in the XOOPS package root to your XOOPS server folder (putting them next to mainfile.php). 2. Execute checksum.php with your browser 3. If necessary, re-upload the missing or corrupted system files 4. Remove checksum.php and checksum.md5 from your server

Modules-----------------------------------

This release contains only the "system-related modules". You are invited to browse the XOOPS modules repository to if you need additional functionality. Note: as a new repository is being built, the current repository is not up-to-date, PLEASE VISIT INDIVIDUAL DEVELOPERS' WEBSITES TO MAKE SURE YOU ARE USING LATEST VERSION OF MODULES.

We would like to thank all developers who contributed fixes to this release (Mage, ForMuss, Trabis, Mamba, DCrussader, XavierS, Cesag, Timgno, Culex, Luciorota, Geekwright, Tatane, PMartina, Paul, Alain091, Voltan, Xoobaru), and all our users who helped us with testing.

great news! And I've tested it immediately! I have found a bug in the meta section:

Defining individual meta tags and description via preferences -> meta tags and footer is impossible. you can do changes, but if you have a look into the code, you will finde the "old" xoops meta tags and description ...

1) Please report any issues in the XOOPS Forums, in this thread2) Quote:

Defining individual meta tags and description via preferences -> meta tags and footer is impossible. you can do changes, but if you have a look into the code, you will finde the "old" xoops meta tags and description ..

With XOOPS everything is possible

You just need to clear your cache in the Admin, or you can run "Update" of the System module, and it should work just fine...

Reminder: if you take the translated file help.html from the website Transifex, I suggest you to take the English original file and edit from it, because the beginning of the code is truncated. Transifex not recognizing the code of XOOPS (i.e $xoops_url ; xoAdminIcons home.png), and it modifies or deletes it.

Congratulations to each member of the XOOPS development team for reaching this milestone. End users do not get to see the sacrifices and brain knocking they endure behind the scenes to pass the finish line, so this is to acknowledge that with appreciation.

Wow... who messed up all translations ?Now with this pointless renaming, who knows what is translated and what is not ?I'll clone it when got time to update my language files in future if there any changes...

The upgrade from X2.4.5 (windows-1256) to X2.5.6 (utf-8) via xotools (by Tarik) was fantastic, but I notice that "Use jGrowl redirect" not found in Preferences page and _config table in database too, I think there something missing in /upgrade/upd-2.4.x-to-2.5.0/index.php file.