Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted April 6, 20168 yr This file hasn't been updated so I replaced it with the default download build and still getting this on the last stage of the upgrade.
April 6, 20168 yr Author thank you! that worked. any idea what would prevent it from working with the upgrade process?
April 7, 20168 yr I had the same thing - I resorted to downloading the full 4.1.10 release from the client area and uploading this one file by itself and that error then went away. Comparing the file in 4.1.10 to what I already had though and it was identical, so not sure what this error was all about.
April 7, 20168 yr When I changed the Admin.php file, it had no effect. Still the same error. /admin/upgrade was the solution. Tanks! Martin
April 8, 20168 yr On 4/6/2016 at 6:13 PM, 0xMerlin said: thank you! that worked. any idea what would prevent it from working with the upgrade process? This was an issue with the md5 filesum cache.
April 9, 20168 yr What is the full manual upgrade procedure - i.e. can I just copy the .zip to the main forums path, and unzip it, and let it overwrite the existing install with impunity, or what the is correct method - I can't find it documented anywhere?
April 9, 20168 yr Author 2 hours ago, dalbert said: What is the full manual upgrade procedure - i.e. can I just copy the .zip to the main forums path, and unzip it, and let it overwrite the existing install with impunity, or what the is correct method - I can't find it documented anywhere? Yes, i just drag over the files. Only the updated files are added. After I drag them over run the upgrade for any database changes to take effect.
April 9, 20168 yr 56 minutes ago, 0xMerlin said: Yes, i just drag over the files. Only the updated files are added. After I drag them over run the upgrade for any database changes to take effect. Thanks ... Gave it a shot ... Will wait for them to get with me on my ticket.
Archived
This topic is now archived and is closed to further replies.