Errors upgrading from 2.7 to 2.8.2

[MissyW]

I have followed the instructions to upgrade from 2.7 to 2.8.2, but got the following errors when running the upgrade-script.php :-

Code:

Notice: Use of undefined constant DEFAULT_THEME - assumed 'DEFAULT_THEME' in C:\xampp\htdocs\James-wb2\framework\initialize.php on line 132

Notice: Use of undefined constant DEFAULT_THEME - assumed 'DEFAULT_THEME' in C:\xampp\htdocs\James-wb2\framework\initialize.php on line 133
WebsiteBaker Project
WebsiteBaker Upgrade
WARNING
Warning:
It is not possible to upgrade from WebsiteBaker Versions before 2.7.0.
For upgrading to version 2.8.2 you must upgrade first to v.2.7.0 at least!!!

However, the existing version was definitely 2.7 (I have a backup copy, and when I log in to admin, it says version 2.7)

I then remembered to install the 2.8.2 fixes rev 2484 (and by the way, this is not mentioned in the upgrade instructions). So I downloaded the fixes, extracted the files and overwrote them to my directory, but I still get the same errors from the upgrade-script (even after clearing my browser cache). 

[ruebenwurzel]

Hello,

the issue is in the database. The upgrade-script in pre 2.8.x versions did not change the version in the database. But this can be fixed by adding the version manually in the settings table. Use Phpmyadmin and change in your database in the settings table the version to 2.7.0. Then Upgrade script should work fine.

To update from 2.7.0 to 2.8.2 please use the full package of WB 2.8.2. Unzip this Package, delete the install dir and the config.php and make a backup of the frontend.css from news and form mudul. Upload then this package to your Webserver. Before running the upgrade-script you should also upload the fixed-file package from the official Download Page.

After all files are uploaded (be shure that all files are replaced) run the upgrade-script. This should now work without issues.

Matthias

[MissyW]

Thanks, Reuben.  The database settings table said 2.7 in the existing version, but when I changed it to 2.7.0 as you instructed, I was able to run the upgrade-script.