Thread

Thanks for posting that, Adam. The reason I asked about the config.php file is because, like I said earlier, the Upgrade Wizard only calls the update file ud_009.php when it’s having issues accessing config.php. I’ve seen folks have problems upgrading when there are unusual things in their config.php.

So let’s try this: go through your CP and save any first-party settings that are set in your config.php file between after this line:

// Dynamic paths for cross-server compatibility

When I say “save any settings”, I mean actually find the screens in the CP that contain these same settings and click Save at the bottom. That makes sure the settings are actually saved to the database and aren’t only in the config.php file. We need that to happen so that you can then remove everything in your config.php file between

// Dynamic paths for cross-server compatibility

and

// END EE config items

Once you’ve done that, retry the upgrade. Let me know how you get along!

Hi Adam, just checking in.

I finally got the chance to test this, and it’s still generating the same error unfortunately.

Hi Adam,

Could you post here the config.php you used to try to perform the upgrade, from the beginning through the line that reads:

// END EE config items

?

Hey Adam,

This line in your config.php file appears to be the culprit:

$conf['protect_javascript'] = "n";

Can you remove that and then try the upgrade again?

Nailed it. The upgrade went through error free.

Defeated by the almighty typo :(
Thanks for slogging through this with me guys.

Thanks for the followup Adam and extremely glad this turned out to be a simple typo. Feel free to start a new thread if you have any more questions.