Please disregard the 'View article...' shown at the bottom of many posts as this is the result of restoring old forum posts from a backup.
v2.3.9 now available
If you are already running v2.3.0, v2.3.1, v2.3.2, v2.3.3, v2.3.4, v2.3.5, v2.3.7, or v2.3.8 you are encouraged to upgrade. If you are running an older version, we recommend you test the installation before upgrading a production server. You MUST be logged in as an admin user to upgrade Exponent.
As with previous releases (beginning with v2.3.3), we no longer support servers running PHP v5.2.x. If you are not running at least PHP v5.3.x, you will see a blank page when attempting to browse to the site, and an error message if attempting to install or upgrade. We also no longer automatically display a login box on the 'maintenance' view. You must specifically attempt to log on with the siteurl/login.php command and the database must be up and running.
If you update via 'git' you may experience a merge conflict due to the MANY changes. The best remedy is to have saved your database (eql file), files archive, and config.php file and when performing the 'git pull', if you receive a 'merge conflict', do this:
If you are updating from any version prior to v2.2.0 and you've been updating your themes and custom modules in accordance with all the previous updates, this will be a simple update like the others. However, if you still have some patched old school stuff (your theme makes calls to exponent_theme_xxx or has custom old school module views), you may have some tweaking to do first. What this means for the site admin is:
As with previous releases (beginning with v2.3.3), we no longer support servers running PHP v5.2.x. If you are not running at least PHP v5.3.x, you will see a blank page when attempting to browse to the site, and an error message if attempting to install or upgrade. We also no longer automatically display a login box on the 'maintenance' view. You must specifically attempt to log on with the siteurl/login.php command and the database must be up and running.
If you update via 'git' you may experience a merge conflict due to the MANY changes. The best remedy is to have saved your database (eql file), files archive, and config.php file and when performing the 'git pull', if you receive a 'merge conflict', do this:
git fetch origin master git merge -s recursive -X theirs origin/master
If you are updating from any version prior to v2.2.0 and you've been updating your themes and custom modules in accordance with all the previous updates, this will be a simple update like the others. However, if you still have some patched old school stuff (your theme makes calls to exponent_theme_xxx or has custom old school module views), you may have some tweaking to do first. What this means for the site admin is:
- When you install this software version, it'll seem as if the site has been wiped because all the modules and content will disappear UNTIL YOU RUN AN UPGRADE (as recommended)
- All of the old school modules will be upgraded and deleted (calendarmodule, simplepollmodule, navigationmodule, containermodule, formmodule/formbuilder, etc...)...all those files in the /framework/modules-1 folder
- Any old school module custom views MUST be upgraded/edited manually. See the post in the 2.0 Installation forum for details.
Comments
FYI, a 'git status' command would likely show what merge conflicts there were.