How to easily update from 2.8.1 to 2.8.2

[ruebenwurzel]

Hello,

here is a very short descreption how to easily update from WB 2.8.1 to WB 2.8.2:

Step 1 - Preparing your existing system:
- Login to your backend and set "Settings" - "Backend-Theme" to "wb_theme" and don't forget to store.

Step 2 - Upload the changed files:
- Download "Websitebaker-2.8.2_changed_files.zip"
- Unzip the "Websitebaker-2.8.2_changed_files.zip" to your lokal machine
- upload all files to your Webspace. Be shure that all existing files are overwritten.

Step 3 - Cleanup Files and Folders on your Webspace:
- Delete File admin/preferences/details.php
- Delete File admin/preferences/email.php
- Delete File admin/preferences/password.php
- Delete Folder modules/backup
- Delete Folder modules/droplets/js
- Delete Folder templates/classic_theme

Step 4 - Upgrade the database:
- call in your Browser www.yourdomainname. com/upgrade-script.php

Step 5 - Delete the upgrade-script:
- Delete File upgrade-script.php

Have fun with WB 2.8.2

Matthias

[ruebenwurzel]

Fatal Error while running the upgrade-script

Reason:
Some older modules calls the "config.php" again when running the modules "upgrade.php".

Fix:
Login in your backend and use the Admin-Tool "Advanced File Editor" (AFE) to edit the upgrade.php from this modules. Uncomment or delete lines like "require_once('../../config.php');" or similar wich points to the config.php

Start then the upgrade-script.php again.

Matthias

[ruebenwurzel]

Pages dir is not "pages"

If you have changed your pages dir from "pages" to something other, please copy the "index.php" from the pages dir in the changed File Package to your pages folder.

Matthias

[maverik]

German Version

[Luisehahne]

Hi,

to solve the problem with overwritten config.php by upgarde to 2.8.2  we renamed the config.php to config.php.new.

INFO for a new install!
Before upload the package by FTP you first have to rename this file again to config.php and set it writeable on your webspace.

In one of the next days, we publish a patch where we fixed all your sending issues. Sorry for all the trouble. On download page there is a ready fixed package 2.8.2. Most of the fixed files are for upgrading to 2.8.2.

Thanks to all who send us the issues.

Dietmar

@edit change config.php.bak to config.php.new

[bupaje]

Thanks for all your hard work.

[dbs]

is the latest fix from the downloadpage included?

[ruebenwurzel]

@dbs

Yes, in the changed Files Package all fixes and changes from the SVN are included. The package will be updated as soon as i got knowledge from changes.

Matthias

[ruebenwurzel]

Error with EmailOutput Filter is already defined

If you use the Droplet "EmailFilter" on one of your pages you got an error when running the upgrade-script.

Reason: WB uses normaly the Admin Tool "Frontend Output Filter" for Filtering Emails. If you additionally use the doplet, wich does exactly the same the classes are defined twice wich produces the Error above.

Solution: Remove the droplet "EmailFilter" from your pages. It is not neccessary.

You may ask why there exists a droplet wich is not necessary. As we included the Droplets in the core of WB it was planned to remove the Frontend Output Filter and replace his functions with droplets. But this isn't realized.

Matthias

[Stefek]

The package will be updated as soon as i got knowledge from changes.

*thumbsup*
And thanks again for your efforts in making WB even better.

Regards,
Stefek

[dbs]

from me too all thumbs up    (right smilie is missing in the toolbar)

i hope in the future it will give only two versions for download:
update-fix (for all new files after stable)
full-version (incl. all fixes)

[ruebenwurzel]

Hello,

i hope in the future it will give only two versions for download:
update-fix (for all new files after stable)
full-version (incl. all fixes)

Sorry for this little bit confusion, but unfortunately the users starts to test WB 2.8.2 with the released stable Version. Normally this should be done in the RC Stadium. The Fixes we now had to made, are all fixes wich have had been found earlier. So now we have a unpatched Version 2.8.2 wich is released on 25.07. and a update-fix package wich will be adapted as soon as there is something to fix.

As far as i know 2.8.2 should be the last Release of the WB 2.8.x versions. After 2.8.2 there only should be released patch files for 2.8.2. But I think it is not the badest Idea to make in the near future a 2.8.3 wich includes all this patches. But this is a decision of the dev-team. It don't matter if there will be a 2.8.3 or not as long as the users got Patch files to hold their system actually.

Matthias

[webby]

Hi

I'm runing a 2.8.x version Revision 1299. I will like to upgrade to 2.8.2.
Is it the same procdure for upgrading as 2.8.1 to 2.8.2 ?

Thanks!

Webby

[ruebenwurzel]

@webby

WB 2.8.1 was Rev. 1287. If you have Rev. 1299 it should be the same procedure as for Upgrading from 2.8.1 to 2.8.2.

Matthias

[webby]

Hi Matthias

I'm getting an error when i'm running the upgrade-script file (upgrade-script.php), after your upgrade-procedure... "2.8.1 to 2.8.2".

A blank white error-site with this error-text (see the attach file)

And if I close the error-site now and call the website (www.xxxxx.dk), the install-procedure is auto-starting, as if I was starting a brand new installation!?

What to do...?

Webby

[ruebenwurzel]

Hello,

wich files did you upload? The whole WB 2.8.2 stable package or the changed-file package?

It looks like you have overwritten your config.php with a clean newone.

Matthias

[webby]

Hi again

The whole WB 2.8.2 stable zip.... at: http://www.websitebaker2.org/en/download/latest-version.php ?
So what do I do now?
Find the old config.php in my backup or?
Where to find the changed-file package?

Webby

[maverik]

see thread above http://www.websitebaker2.org/forum/index.php/topic,21997.msg148129.html#msg148129
first post you find the link to changed files zip

if you have a copy from config.php in your backup you can upload with ftp and all must be fine, i hope

[webby]

Hi Matthias

Ohhh I haven't see the link in your descreption, and thats why I have used the WB 2.8.2 stable zip!? (Daammm!)

So what can I do now: Just find the old config.php with tfp, and then run the upgrade.php-script again or shall I upload the hole "changed-file.zip instead? Or?

Thanks you.

Webby

[ruebenwurzel]

Hello,

So what do I do now?

You must restore your config.php.

Find the old config.php in my backup or?

I hope. If you have used the standard WB backup tool, you will have no backup from config.php. If you have used another backup-tool, you will only have a backup if you have also made backup of your files. The config.php should look like this:

Code:

<?php

define(&#39;DB_TYPE&#39;, &#39;mysql&#39;);
define(&#39;DB_HOST&#39;, &#39;xxxxxxxx&#39;);
define(&#39;DB_USERNAME&#39;, &#39;xxxxxxxx&#39;);
define(&#39;DB_PASSWORD&#39;, &#39;xxxxxxxx&#39;);
define(&#39;DB_NAME&#39;, &#39;xxxxxxxx&#39;);
define(&#39;TABLE_PREFIX&#39;, &#39;xxxxxxxx&#39;);

define(&#39;WB_PATH&#39;, dirname(__FILE__));
define(&#39;WB_URL&#39;, &#39;http://www.xxxxxxxx.xxx&#39;);
define(&#39;ADMIN_PATH&#39;, WB_PATH.&#39;/admin&#39;);
define(&#39;ADMIN_URL&#39;, &#39;http://www.xxxxxxxx.xxx/admin&#39;);

require_once(WB_PATH.&#39;/framework/initialize.php&#39;);

?>

Replace the "x" with the datas from your hoster.

Where to find the changed-file package?

You find all in the first post.

So what should you do now:
1.) Replace the config.php with the one from your backup or create a newone from the example
2.) Download the "changed_file" Package from the first post, unzip it and upload all files to your webspace
3.) Run the upgrade-script again.

Have fun

Matthias

[webby]

Thanks I will try that  !

Webby

[webby]

It works!

Buy the way - shall I delete the "install-folder" ?

Thanks again.

Webby

[ruebenwurzel]

Hello,

Buy the way - shall I delete the "install-folder" ?

Yes the install folder can be deleted.

Matthias

[webby]

Hi again Matthias

Oops... - after the upgrade og an other WB-site (works perfect), I was trying to change the admin-backend-theme to "classic theme" and then it crashed with this error (se attach).
How do I roll back or change the backend-theme-settings to the old WB-theme again?

Webby

[ruebenwurzel]

Hello,

please read again the first post and follow the instructions.

Classic_theme isn't longer supported from WB and should be deleted before running the upgrade-script.

Matthias