[SOLVED] wrong SITE_APP_VERSION found, prevents upgrade
Permalink
Am trying to recover from botched upgrade attempt. I did back up my database, and the concrete folder, but not the other site files (stupid, I know :( )
when I attempt to upgrade I get the following error:
-----------------------------------
Upgrading from 5.3.2
Upgrading to 5.2.1
Your current website uses a version of Concrete5 greater than this one. You cannot upgrade.
-----------------------------------
I checked the config table in my database and confirmed the correct version is there:
5.2.0RC1
so is all lost? is the spurious version information stored in the cache somewhere?
any help greatly appreciated. many thanks!
humbly and with gratitude,
Bodhi
when I attempt to upgrade I get the following error:
-----------------------------------
Upgrading from 5.3.2
Upgrading to 5.2.1
Your current website uses a version of Concrete5 greater than this one. You cannot upgrade.
-----------------------------------
I checked the config table in my database and confirmed the correct version is there:
5.2.0RC1
so is all lost? is the spurious version information stored in the cache somewhere?
any help greatly appreciated. many thanks!
humbly and with gratitude,
Bodhi
Thanks Ryan. The problem was indeed in the cache. I deleted the contents of files/cache/
and files/cache_objects/ and upgraded to 5.3.2 *almost* without a hitch. :)
when I (while logged in to the dashboard) returned to the site, I got a fatal error:
-----------------------------------------
[function.require-once]: failed to open stream: No such file or directory in /home2/hwbguild/public_html/concrete/libraries/loader.php on line 187
Fatal error: require_once() [function.require]: Failed opening required '/home2/hwbguild/public_html/concrete/config/../helpers/concrete_support.php' (include_path='.:/usr/lib/php:/usr/local/lib/php:/home2/hwbguild/public_html/libraries/3rdparty:/home2/hwbguild/public_html/concrete/config/../libraries/3rdparty') in /home2/hwbguild/public_html/concrete/libraries/loader.php on line 187
-----------------------------------------
to overcome this, I punted a bit, guessing that loader.php was constructing an invalid path that was intended to be:
'<mysite>/concrete/helpers/concrete/support.php'
Unable to debug the loader code, I copied the file
/concrete/helpers/concrete/support.php
to
/concrete/helpers/concrete_support.php
and got things running again.
I'll send an email to Andrew to see if he can shed some light on this issue, and report back here.
and files/cache_objects/ and upgraded to 5.3.2 *almost* without a hitch. :)
when I (while logged in to the dashboard) returned to the site, I got a fatal error:
-----------------------------------------
[function.require-once]: failed to open stream: No such file or directory in /home2/hwbguild/public_html/concrete/libraries/loader.php on line 187
Fatal error: require_once() [function.require]: Failed opening required '/home2/hwbguild/public_html/concrete/config/../helpers/concrete_support.php' (include_path='.:/usr/lib/php:/usr/local/lib/php:/home2/hwbguild/public_html/libraries/3rdparty:/home2/hwbguild/public_html/concrete/config/../libraries/3rdparty') in /home2/hwbguild/public_html/concrete/libraries/loader.php on line 187
-----------------------------------------
to overcome this, I punted a bit, guessing that loader.php was constructing an invalid path that was intended to be:
'<mysite>/concrete/helpers/concrete/support.php'
Unable to debug the loader code, I copied the file
/concrete/helpers/concrete/support.php
to
/concrete/helpers/concrete_support.php
and got things running again.
I'll send an email to Andrew to see if he can shed some light on this issue, and report back here.
I found the fix here:
http://www.concrete5.org/index.php?cID=8972...
In a reply titled "Had the same problem" posted by chunksmurray.
As described in the fix, I had a modified legacy header_required.php file sitting in my /elements folder overriding the newer file in /concrete/elements.
Deleting it fixed the problem. Yippee!
http://www.concrete5.org/index.php?cID=8972...
In a reply titled "Had the same problem" posted by chunksmurray.
As described in the fix, I had a modified legacy header_required.php file sitting in my /elements folder overriding the newer file in /concrete/elements.
Deleting it fixed the problem. Yippee!
Typically if you want to recover from an upgrade, you'd restore your database and restore a matching version of concrete's core (the /concrete folder)
If you've already done that, try deleting all of the files in /files/cache/* And /files/cache_objects