![[Main Page]](/modules/mediawiki/images/mediawiki.png)
Update XOOPS to the latest version
XOOPS 2.0.17.1 release notes
The XOOPS development team is pleased to announce the release of XOOPS 2.0.17.1
This is a maintenance release containing several bugfixes.
Read the full Change_Log for details.
Important: See too: Lasted Security Patch Reported by phppp in 2007/10/1.
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
Your can get this release package from the sourceforge.net file repository. Both .zip and .tgz archives are provided.
see you too Archive compression tools
Installing XOOPS
1. Copy the content of the htdocs/ folder where it can be accessed by your server 2. Ensure mainfile.php, cache, templates_c and uploads are writable by the webserver 3. 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.17.1 (easy way)
1. Get the update package from the sourceforge file repository 2. Overwrite your existing files with the new ones
Upgrading from XOOPS 2.0.14/2.0.15/2.0.16/2.0.17
(using the full package) 2.0.17.1
1. Move the "upgrade" folder inside the "htdocs" folder (it's been kept out as it's not needed for full installs) 2. Delete htdocs/mainfile.php, htdocs/install/, htdocs/cache/, htdocs/extras/, htdocs/template_c/, htdocs/themes/ and htdocs/uploads/ 3. Upload the content of the htdocs folder over your existing files 4. Access <your.site.url>/upgrade/ with a browser, and follow the instructions 5. Follow the instructions to update your database 6. Delete the upgrade folder
Upgrading from XOOPS 2.0.17
fix-me please
1. Get the update package from the sourceforge file repository 2. Overwrite your existing files with the new ones 3. Be sure mainfile.php is writable 4. Go to <your.xoops.url>/upgrade/ and follow the upgrade instructions 5. Delete <your.xoops.root>/upgrade/ from your web root 6. Write protect mainfile.php 7. Update the system module in the administration menu 8. Clear your cache and templates_c folders
Upgrading from XOOPS 2.0.16
1. Get the update package from the sourceforge file repository 2. Overwrite your existing files with the new ones 3. Be sure mainfile.php is writable 4. Go to <your.xoops.url>/upgrade/ and follow the upgrade instructions 5. Delete <your.xoops.root>/upgrade/ from your web root 6. Write protect mainfile.php 7. Update the system module in the administration menu 8. Clear your cache and templates_c folders
Upgrading from XOOPS 02.0.13/2.0.14/2.0.15 (easy way)
1. Get the appropriate update package from the sourceforge file repository (the 2.0.16 - 2.0.17 upgrade package) 2. Overwrite your existing files with the new ones 3. Access <your.xoops.url>/upgrade/ with a browser 4. Follow the instructions to update your database 5. Delete the upgrade folder
Upgrading from XOOPS 2.0.14/2.0.15 (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) 2. Delete htdocs/mainfile.php, and htdocs/install from the full package 3. Upload the content of the htdocs folder over your existing files 4. Access <your.xoops.url>/upgrade/ with a browser 5. Follow the instructions to update your database 6. Delete the upgrade folder
Upgrading from any XOOPS ranging from 2.0.7 to 2.0.13.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)
2. Delete htdocs/mainfile.php, and htdocs/install from the full package
3. Upload the content of the htdocs folder over your existing files
4. Delete the following folders and files from your server (they belong to an old version):
* class/smarty/core
* class/smarty/plugins/resource.db.php
5. Empty the templates_c folder (except index.html)
6. Ensure the server can write to mainfile.php
7. Access <your.xoops.url>/upgrade/ using your browser, and follow the instructions
8. Write-protect mainfile.php again
9. Remove the upgrade folder after use
10. Update the "system" module from the modules administration interface
Files integrity check
The full XOOPS package is released with a script able to check if all the system files were correctly uploaded to the server. To use it, follow these instructions:
1. Upload the xoops_md5.php and xoops.md5 files located in the XOOPS package root
to your XOOPS server folder (putting them next to mainfile.php).
2. Execute xoops_md5.php with your browser
3. If necessary, re-upload the missing or corrupted system files
4. Remove xoops_md5.php and xoops.md5 from your server
Revealing the blank page backtrace log
XOOPS displays a basic error page when a fatal error preventing it to run is encountered. To help you diagnose the cause of the error, this page contains additional messages that are hidden by default. To reveal them, use your browser "select all" function (for most browsers, you can use "Ctrl+A").
Incompatibility with some modules
Beginning with XOOPS 2.0.14, a change in the core template methods resulted in some incompatibilities with some modules that do not have their templates under (dirname)/templates/ as many XOOPS modules do. Some example are: wraps, 3dforum etc..
If you use one of these modules, you may fix this problem by replacing the resource.db.php file located in the class/smarty/xoops_plugins/ folder by the one provided in the package "extras" folder. This file is the patch provided by Gijoe on peak.xoops.ne.jp.
This issue is one that will be addressed further in later core releases, to provide better compatibility.
We would like to thank GiJoe from peak.xoops for his work with this issue.
Modules
The packages do not contain any module apart from the system one. You are invited to browse the XOOPS modules repository to get some. Note: as a new repository is being built, the current repository is not up-to-date, PLEASE VISIT DEVELOPERS' WEBSITES TO MAKE SURE YOU ARE USING PROPER VERSION OF MODULES.
We also highly recommend the installation of the Protector module which will bring additional protection and logging capabilities to your site.
