Important note: XOOPS 2.5.8 requires some database updates for full function. Be sure to follow the instructions below under Upgrade Required if you are updating an existing system.
Requirements
Much attention was given to keeping the same system requirements between XOOPS 2.5.7 and 2.5.8.
The minimum PHP version is 5.3.7, while use of a currently supported PHP version, 5.5 or higher, is strongly recommended. XOOPS 2.5.8 will be the last XOOPS version to support PHP 5.3 and 5.4.
MySQL versions 5.0 or higher are required, with version 5.5 or above (or compatible MariaDB version) recommended.
Please Report Any Issues
Please report any issues you encounter with this release so that we can make XOOPS better for everyone. If you are registered on GitHub, just open an issue. We will also monitor the XOOPS forums.
Fixes and Enhancements
Without the contributions of many, this release would not exist. A big "Thank you!" goes to everyone that has contributed. In alphabetical order, the list includes:
Lots of effort has been put into making XOOPS better, cleaner, safer and more compliant with current standards and best practices.
Security
This release includes fixes for multiple issues (CSRF, weak password hash, and directory traversal) reported by hyp3rlinx. Also, fixes for a potential privileged information disclosure issue reported by Cédric MONTUY.
Passwords are now hashed using PHP's password_hash() function. A library that brings compatibility to users with PHP versions earlier than 5.5 is included.
The new XMF library (see below) includes support for JWT, which can be very useful in securing AJAX and REST processing.
Ready for PHP 7
The world of PHP is in constant motion. The recent release of PHP 7 brings with it huge improvements, but also compatibility issues. The very popular Ubuntu server in it's 2016.04 LTS release uses PHP 7 by default - and XOOPS is now ready. There are some growing pains though.
MySQL support using the mysql extension has been deprecated for quite a while, and PHP7 removes it completely. XOOPS 2.5.8 now uses the mysqli exclusively. Any database access using standard calls to the XoopsDatabase classes will use the newer mysqli extension. Some modules are using direct database calls through PHP mysql_* functions. These will continue to work under PHP 5, but it is recommended that module developers consider remediation of any such calls.
Another thing that changes in PHP 7 is "All of the E_STRICT notices have been reclassified to other levels." In previous XOOPS versions, E_STRICT warnings have been suppressed when using the debugging logger. These are no longer suppressed to give developers insight into what may need to be fixed. We've tried to make sure XoopsCore runs clean, but modules may produce debugging output you have not seen with earlier versions.
Custom administration themes may have issues due to a long existing bug in the XoopsSystemGui::validate() definition.
XMF Included
XOOPS Module Framework library, the XMF library, is now included, and is used in the core in several places. XMF is a library of standard classes useful in module development. It can be very useful in the near future, as all of its classes are forward compatible with the next generation of XOOPS.
XOOPS no longer ships with Flash banners, and instead uses HTML5.
Lots of updates, clean ups and fixes.
Upgrade Required
There are database changes with this version. There are no new requirements for a fresh installation, but for updating an existing system, follow the recommended upgrade process. In a nut shell:
- Make a full backup of site files and database. (We've done lots of testing, but it is always best to be safe.)
- Copy the contents of the distribution htdocs directory into your web root directory.
- Copy the contents of htdocs/xoops_lib to your relocated/renamed xoops_lib as applicable.
- Copy the distribution upgrade directory into your web root directory.
- Point your browser to http://your-site-url/upgrade/ and follow the prompts.
- Log in and step through any needed updates.
- At the end, follow the link* to upgrade the system module.
- Also update pm, profile and protector modules if installed.
- Remove the install and upgrade directories from your web root.
Your site should be ready to use.
* There are several template changes in 2.5.8, so it may be difficult to navigate the system until the system module is updated. If you missed the link at the end of the updater, you can use direct access it with: your-site-url/modules/system/admin.php?fct=modulesadmin&op=update&module=system
* Please Note: The new passwords are incompatible with older XOOPS systems - in the database they are longer and use radically different hashing mechanisms. Moving forward is automatic, but going backward takes manual intervention.
Upgrade to xoops 2.5.8 isnt goes smooth as i expect xfguestbook module = cant edit or modify form options, white screen and the error is
Call to undefined method xfgbFormSelectCountry::XoopsFormSelect() in /**public_html/modules/xfguestbook/class/xfgbformselectcountry.php on line 35, referer: http://**modules/xfguestbook/admin
un-commenting line 35 get me rid of the white screen bit this time it isnt save any changes i made in the form options so useless*/
Re: XOOPS 2.5.8 Final Available
Yurdal,
Which version of xfguestbook & PHP are you using?
Re: XOOPS 2.5.8 Final Available
Quote:
Upgrade to xoops 2.5.8 isnt goes smooth as i expect xfguestbook module = cant edit or modify form options, white screen and the error is
Call to undefined method xfgbFormSelectCountry::XoopsFormSelect() in /**public_html/modules/xfguestbook/class/xfgbformselectcountry.php on line 35, referer: http://**modules/xfguestbook/admin
This is because some of the old modules will have problems with newer versions of PHP. In this case, this old PHP4 code:
class xfgbformselectcountry extends XoopsFormSelect { public function xfgbFormSelectCountry($caption, $name, $value=null, $size=1, $nullopt=false) { $db =& XoopsDatabaseFactory::getDatabaseConnection(); $this->XoopsFormSelect($caption, $name, $value, $size);
had to be updated, to use "__construct" as a constructor, and to call its parent's constructor:
class XfgbFormSelectCountry extends XoopsFormSelect { public function __construct($caption, $name, $value = null, $size = 1, $nullopt = false) { $db = XoopsDatabaseFactory::getDatabaseConnection(); parent::__construct($caption, $name, $value, $size);
I've made these and few other updates to xfGuestbook, and you can download it from my GitHub. Check it out and let me know if it works for you.
I guess, we'll have to set up a special repository for modules that have been exclusively tested on XOOOPS 2.5.8
Request: But what you could do for us, is to help us with the tutorial for xfGuestbook. You can fork it from the XoopsDocs*/
Re: XOOPS 2.5.8 Final Available
just downloaded and updated, it works fine now
Re: XOOPS 2.5.8 Final Available
Great job!
I'm back and I work on a new module for 2.5.8: xmcontact
I will also create a very simple content module: xmcontent
I'm happy for XOOPS
Re: XOOPS 2.5.8 Final Available
I have problems after upgrade from 2.5.7.2 to 2.5.8, when I go to modulesadmin to upgrade the system module I get noting and have the next error:
Warning: Smarty error: unable to read resource: "db:system_modules.tpl" on the file /class/smarty/Smarty.class.php and line 1094
PHP 5.5.35 mySQL 5.6.30
Re: XOOPS 2.5.8 Final Available
Quote:
I have problems after upgrade from 2.5.7.2 to 2.5.8, when I go to modulesadmin to upgrade the system module I get noting and have the next error:
I assume that you've run the
/upgrade
right?
Go to Admin/Maintenance and clear the Cache then run the System update.
Let us know if that worked...
Re: XOOPS 2.5.8 Final Available
Hi Mamba
I use the scriptaculus upgrade, and can´t access to maintenance, appear the same problem
Re: XOOPS 2.5.8 Final Available
The system module must be updated or the upgrade will not work correctly.
You can access the update function directly with this URL:
Change the (your-site-url) part to match the base URL for your site.
Also, there is a link on the final page of the upgrade scripts which also takes you directly to the system module update, so you could rerun the upgrade instead.
Re: XOOPS 2.5.8 Final Available
Thanks Master Now is ok. Bad decision to use scriptaculous update, better do it manually.
Re: XOOPS 2.5.8 Final Available
Both the hash security upgrade and PHP7 is a massive step forward! This is great. Both of those probably worked back into 2.5 quite naturally from the R and D already done on 2.6 so whoever made this decision, thanks.
Re: XOOPS 2.5.8 Final Available ~: Bugs
Hey guys, i am unbroken, I found the best thing for injuries for computing is Dymethal Sulphone - Sulphur as a pill it cured all my RSI Electro Shock 30yr Typing Style attack that happened to me that landed me on the couch for 18 months...
Can you remember to send me the Final before release so I can test the environment correctly... Anyway I have found a couple of bugs in the release, I have made a couple of YouTube.com Videos of the bugs that are found here:~
The empty pages in the system admin area are a sign that you did not update the system module after the upgrade. That step can't be skipped this time around.
The Xmf\IPAddress error is an indication that autoloader is not active. The autoloader is started by including class/xoopsload.php as part of the include/common.php, so a custom start up might need to be adjusted.
How can we download the langu files in once from Transifex? Im busy translating to Turkish for 2.5.8 and the 2.6.0 versions buit i want to try them in real life, is there som kind of button to accomplish this in Transifex ?
Re: XOOPS 2.5.8 Final Available
Quote:
I'm busy translating to Turkish for 2.5.8 and the 2.6.0 versions but i want to try them in real life, is there some kind of button to accomplish this in Transifex ?
The second one is the better way, even if more complicated. There is an excellent tutorial on how to do it, and even if it is about Joomla, it's pretty easy to follow and do the same for XOOPS:
I've done it last year for the Publisher and you can see the result here on GitHub
The Publisher configuration file, which is the most important, is here in the .tx folder
I feel that we should have such a configuration file for each module (and of course, for the Core), so each translator could download the files to his/her local PC and translate them as needed, and then upload them to GitHub to our Language files.
Once you have these GitHub Language files downloaded to your local PC, and they are connected via the Transifex "config" file to Transifex translations, you could:
a) translate the files on Transifex, download them using the "client" and commit them via Git to GitHub
b) translate them manually on your local PC, commit them to GitHub via Git, and then "push" them to Transifex using the "client"
Of course, the goal would be to do something similar to how GitBook works, i.e. you can edit a book either on GitHub or in the GitBook Editor, and once done/committed, the other one will be updated without any extra work on your side. See here a little workflow for XOOPS
Re: XOOPS 2.5.8 Final Available
Mamba thank you for your explanation, i get a trojan error if i want to use windows client for Transifex and im not gonna take a risk :)
I have finished the Turkish version for 2.5.8 and 2.6.0 verions please add them to the standard XOOPS files so that other people can make use of it
Re: XOOPS 2.5.8 Final Available
Quote:
Mamba thank you for your explanation, i get a trojan error if i want to use windows client for Transifex and im not gonna take a risk :)
That's the first time I've heard about it! What version of the client did you use? I used the 64bit Python 3.5 version, and had no issue on Windows 10.
Quote:
I have finished the Turkish version for 2.5.8 and 2.6.0 verions please add them to the standard XOOPS files so that other people can make use of it
Awesome!!! Thank you so much!!!
Re: XOOPS 2.5.8 Final Available
I have troubles with Protector module:
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 130968 bytes) in /home/**/xoops_lib/modules/protector/include/precheck.inc.php on line 6
This is a dedicated server with 16 GB Ram ! When this occurs the site gives white pages, and i have to disable the protector module to gain my website back
Xoops 2.5.8, php 5.6 and mysql 5.6 versions are running
EDIT: I Found it , it was de rmcommon module that cause the problem disable it does the trick
Re: XOOPS 2.5.8 Final Available
After update i cannot to make login, the username and password are corrected but not can to login.
Re: XOOPS 2.5.8 Final Available
Quote:
After update i cannot to make login, the username and password are corrected but not can to login.
Did you do the /upgrade?
You need to do it.....
Re: XOOPS 2.5.8 Final Available
I cannot upgrade because the login form to upgrade don't accept my username or pw My actual xoops version is 2.5.7.2 Thank you.