Discussion Forum

jmason03

Member

Registered: January 9, 2014

Posts: 123

BigTree/Extension Upgrade Issue

I'm having an issue (using 4.2.1 clean install) upgrading to 4.2.2 and it is also affecting trying to upgrade extensions (specifically the one most recently published for Form Builder) and I can't quite figure out what it causing it.

I believe I have narrowed down the bug to something happening in the installLocal (BigTreeUpdater) function. As part of debugging, I've been having the function die right after the call to backupDatabase to make sure everything is getting moved correctly but my core files never get moved to the backups folder. The backups folder and the core-4.2.1 folder are both created and the backup.sql file is stored inside them where it's supposed to be. However on the screen I'm getting a warning for the rename function that moves the old core into the same folder saying "access is denied (code 5)". So I figured something was wrong with either the permissions of the backups (sub)folder when it was being created but the sql file is created in there with no issues so it clearly has read/write permissions for that. Then I thought the permissions might be messed up with the core folder so I duplicated the backupDatabase call to put a second copy of backup.sql in the main core folder and it did that fine as well.

Now if I let the installLocal run all the way through without me killing it, BigTree acts like the upgrade was successful except the message returned says that I upgraded to 4.2.1 (which I'm already on). When I look at the core files and compare them with what  I know are updated files from 4.2.2 they don't match so nothing is getting updated. Another weird part is that in the cache/update/core folder the files that were extracted from the update.zip are no longer there but the entire folder structure for the core folder is. Now if I kill the installLocal function before it runs the rename that moves the new core from cache/update/core to core/ then all the files are there extracted properly.

So I'm stuck wondering why it looks like there is a permissions problem but I'm able to create files in all these folders but not move them? The same rename problem looks like it also plaguing extension upgrades when they're both called. Any ideas you have on what problem I might be experiencing would be most appreciated!

timbuckingham

Administrator

From: Baltimore, MD

Registered: April 2, 2012

Posts: 974

Re: BigTree/Extension Upgrade Issue

My best guess is that the /core/ folder isn't moveable but for some reason you can write within it. The updater checks to see if the server root (the directory above /core/) and /core/ are both writable before performing a local install.

It's possible some weird PHP security settings are preventing it from moving the /core/ folder into /backups/. That would then cause the new core to move over which is why it would still say it updated to 4.2.1.

Could you can email me a copy of php.ini and send me a phpinfo() dump?

In the meantime if you need to upgrade I recommend just replacing the /core/ folder manually (extract it from the downloadable zip, rename it to core-new or something, upload via FTP, rename your existing core to core-old and rename core-new to core). We have to do that frequently on some temperamental servers that have were firewall settings.