Hi:
I’m currently running EE 1.4.1, and just tried to upgrade to the latest version, 1.6.2. However, I ran into the dreaded:

error twice, first when the update script attempted to go to EE 1.5. At this point, I searched the EE forums for a solution, which suggested I do a compare of the config file using config-check.php located here and manually updating the file to match- that got me through until once again I encountered the same error when trying to go up from EE 1.5 to EE 1.6. As I didn’t want to risk seriously corrupting the database, I’ve just downgraded back to EE 1.4.1 until I have a better understanding of how to fix the problem at its core.

By searching the forums, the Error 1050 problem when updating seems to be a pretty common one. I see the general explanation for the cause is that config.php isn’t chmod 666, but I’m certain mine is. Is there anything else I can do to ensure the update script runs properly the next time I attempt an upgrade? Assuming the file is chmod correctly, is there anything else on a server that may be contributing to EE crapping out and returning this specific error when running the update script?

Thanks,

It sounds like two possibilities- EE is having trouble writing to the config.  Might contact the host- ask them proper permission for a php script to write to a file.  Or if anything else might be interfering.

Second option- it is writing to the script, but for some reason pulling up a cached copy.  This is more rare and doesn’t sound like what you’re experiencing.  But if it is- it’s easy to spot.  Run the first update link- sounds like that goes ok- right?  Then, before you update again, ftp in, grab config.php and see if it actually updated.  The version number should have changed.  If it DID change- it’s writing successfully.  But it’s being served from cache. 

Make sense?  So what I’d do- run that first update, report back whether config.php changed for you.

Hi:
Assuming it’s the more obscure caching issue instead, what’s the solution? I recall when I ran into Error Number 1050 the first time upgrading from EE 1.4.1 to EE 5.0, upon manually opening up config.php, the version number *was* changed, but it was missing a few other lines that I added in thanks to “config-check.php”. Doesn’t that mean the script was able to write to config.php, just not fully for whatever reason?

Thanks,

No, if it can change the version number in config.php then the file is writeable, and we needn’t worry about that. At some point (EE 1.5?) most of the configuration options went from config.php to the database, so this is what you might be experiencing. What’s your current status?