Coping with the v2.0.9 Upgrade

Unlike most previous releases, the release of v2.0.9 has seen it's share of problems. Though most of these are minor issues, they can seem to be an obstacle if not addressed. Here's some things to watch out for, and steps to correct these issues:

Git Pull upgrade creates a merge conflict and the site 'crashes':

'Git' is supposed to prevent this, but for some reason when updating (git pull) a 'git' maintained site from 2.0.8 (or the patches) to 2.0.9, you'll receive a notice of a merge conflict and the site will no longer work. The problem lies in two files (exponent_version.php and framework/modules-1/calendarmodule/class.php). There are a couple different options to fix this, so you'll find the details in this forum post. We are working to alleviate this issue!

Menus don't work the same as before the upgrade:

Even though the new navigation controller includes some compatibility to still allow old style navigationmodule modules to work...this apparently isn't true in all circumstances, especially complex menus. The solution is to update the calls and the templates/views to the new 2.0 navigation module format. This is a fairly simple change as it entails copying and renaming those custom templates. You'll find the details in this forum post.

My customized site 'crashes':

This occurs if you are running customized modules (controllers) on your site. Because PHP v5.4.x enforces greater code standards, we've had to update some of the main code which in turn requires updates to any custom modules (controllers). This is a fairly simple update as it entails adding the 'static' keyword to the static functions inherited from the parent expController class. You'll find the details in this forum post.

We'll keep this article up to date as things progress.

About the author

Comments

Sam
said
on October 19, 2012

I am having problems with url redirect I believe through code in the default .htaccess file. I'm hosting at 1and1.com. They have identified the problem with the default .htaccess. 1and1 states
"We did checked your website and webfiles and it shows that your .htaccess that cause the issue. Please try to check the syntax of your mod_rewrite or disable the .htaccess file to fix the error 500."

# To redirect all users to access the site WITH the 'www.' prefix,
# (http://example.com/... will be redirected to http://www.example.com/...)
# adapt and uncomment the following:
#RewriteCond %{HTTP_HOST} ^example.com$ [NC]
# RewriteRule ^(.*)$ http://www.example.com/$1 [L,R=301]
#
# To redirect all users to access the site WITHOUT the 'www.' prefix,
# (http://www.example.com/... will be redirected to http://example.com/...)
# uncomment and adapt the following:
# RewriteCond %{HTTP_HOST} ^www.example.com$ [NC]
# RewriteRule ^(.*)$ http://example.com/$1 [L,R=301]