I did indeed mean migrating from the second-to-last version of WB (our modules no longer work with the current version... everything has been “locked,” which is the main reason we suddenly decided to move away from it).

Fortunately, I still have enough credits with our mutual friend Claude.

It came up with a solution:
- Make a copy of the current WB environment (files and SQL), which can be done using the WB backup module;
- Create a new WBCE environment—in other words, a fresh installation;
- Install the (third-party) modules and templates used in the WB environment;
- Add the module-specific data to the tables in the WBCE environment.
- Copy the contents of the Pages and Media folders in the WB environment to the new WBCE environment.

Since I’m not really a techie, I’m having a script written for each WB environment that I can then run myself.

I’m currently migrating everything to v1.6.8 because, for now, I’m missing the editor in the new development version.

In short: there’s no simple solution for migrating. On the other hand, just like in photography, the saying “garbage in, garbage out” applies. With the solution above, you set up a new, clean environment where only the data is migrated.

The mysqli_connect error might mean that the PHP mysqli extension is not installed/activated. Please check.
The error about wbce_update_unzip.php might mean that the file was not uploaded, or the access rights are wrong, or there are issues with the zip extension.
You might want to try updating the "hard" way, e.g. unzip the installation/update package locally and upload it file by file via FTP and then call /install/update.php manually.

Christian

You are right, index.php was missing and now it's working.
I should have noticed that.
Very strange that index.php is missing every time. I'm using Filezilla for uploading.

//Jan-Eric