Thread

I’ve got a site running 2.1.3 and I spent a lot of time preparing the files for the upgrade to 2.5.2 - updating the system file but making sure the 3rd party folders, themes directories, index, admin, config and database files etc were all included and pointing to the right places where relevant.

I did all of this in a local directory and then uploaded that to the server root. I took the site offline, and to run the update I switched the existing site directory and the new one so that a) I still had the original site files and b) it should have been a quick, straightforward update(!)

As soon as I switched the folders over I got a 500 error on the index page, but the admin side of things worked ok and the installer kicked in to run the update. I wasn’t sure what caused the 500 error but thought it might be that the old database structure somehow wasn’t compatible with the new index file. I ran the update and that went fine, but as soon as it finished and I removed the installer file I started getting 500 errors on both the front and back end. At this point panic started setting in… 😊

I’ve reverted all site files and the database to their previous 2.1.3 state and the site is back up ok, but I don’t really know how to progress this - because of the unhelpful nature of the 500 error I don’t know what’s causing it - whether it’s a 3rd party addon that needs updating, or something else that I could prepare for. I tried commenting out the htaccess file to see if that was the problem, but it made no difference.

I’m trying to get a local version of the site running on my laptop so that I can do all the upgrade work locally, but if anyone has experience of this happening to them or can offer any more robust update advice I’d be most grateful!

OK I’ve got my local environment running the site and I’m in the same situation as I got to previously - the admin side of things is offering to update but I’m getting the 500 error at the front. I’ve set debug to 1 in the config and I can see an error:

A PHP Error was encountered

Severity: Notice

Message: Undefined property: EE::$security

Filename: libraries/Extensions.php

Line Number: 185

Fatal error: Call to a member function sanitize_filename() on a non-object in /path-to-system/expressionengine/libraries/Extensions.php on line 185

I found another thread suggesting that it could be caused by an incomplete upload, but these files were pulled directly from a freshly unpacked EE zip. Any other ideas very very welcome!!

I could really use some help on this, even if it’s just pointers as to where to start. The site is pretty huge and has been running for over a year, so I don’t want to have to remove all the 3rd party stuff if I can help it as I risk damaging the content/relationships etc… but if I have to do that, I do have a local version to find the faults with and hopefully narrow down the issue… just not sure where to start.

OK, I got my local build *almost* working (a couple of minor errors with debug set to 1, but nothing I haven’t seen before). I uploaded all of the files, connected to the database that’s already been upgraded and I’m back to square 1.  Exactly the same error as in my initial post.

In the interim I’ve had absolutely zero support with this issue and am utterly disappointed at the lack of assistance from EllisLab. The upgrade procedure is opaque at best and with so many updates coming out all the time are we supposed to update every EE site we’re responsible for every time? And charge our clients for the time it takes to iron out the inevitable bugs and errors that appear with each one?

There must be another way - Magento updates all happen online via the cp (or at least they did last time I looked)

PLEASE CAN SOMEONE SUGGEST SOMETHING USEFUL TO HELP ME FIX THIS ISSUE??

Did you update all your 3rd party addons to the latest versions before you upgraded?

Not all of them, no - there must be 30 if you count the plugins and extensions too… I guess I’ll have to update all of that stuff (where possible) first and then try the upgrade…?

It’s always worth doing when you upgrade as a matter of course, some older addons don’t work with newer version sof EE so can cause problems.

I’ve got the front-end up fine (based on a copy of the live site, which I’m going to systematically upgrade, third party stuff first) but I’ve run into an age-old problem that the recommended fix isn’t working on. When I try to access the cp, I get:

An Error Was Encountered
Unable to load the requested file: account/login.php

The recommended fix (many times) in the forums is to add this to the config.php file:
$config[‘theme_folder_path’] = “/Users/paul/Sites/mysite.new/www/themes/”;

I’ve done this and double-checked my document root path, and it’s all correct, but the error is persistent. Is there anything else I should try?

OK, redownloaded my whole themes directory and it’s let me in this time 😊 Time to start updating modules…

Ah, could have been missing files!

Hey Paul_B,

Where are things at now? Any more progress since the 9th?

Please let me know.

Cheers,

OK, I got everything working. My solspace modules gave me a couple of extra headaches that are straightforward to fix once you know that they’re the problem! Here’s what I did in case it helps anyone else.

1) I manually updated all third party modules first, one at a time (which broke the 2.1.3 build anyway as some weren’t compatible with pre-2.4.0)

2) Then I cleared all caches, and updated the config.php file - set allow_extensions to ‘n’

3) Updated all of the core files. Logged in, ran ‘update modules’, then went into each solspace module individually and ran the update inside each of them (with extensions set to ‘y’, I just got php errors and no CP access). Also NSM .htaccess manager was a pain as I’d previously been running 1.0.5 and had to go into the database to remove the rows related to this extension, and then re-instate the htaccess rules.

4) Then re-synced all file manager images and the site was back up.

Like I say, just in case someone else is tearing their hair out, I hope something from above might help…

Hey Paul_B,

Glad to hear it! Thanks for sharing all that info.

If you need anything else, please just let me know by opening a new thread.

Cheers,