Upgrade Error from 2.10 to newest 2.13

WebsiteBaker Support (2.13.x) > General Help & Support

(1/1)

gonzo99:
Hello bakers,
I am on the way to upgrade the website of a friend. Last time I did that was in 2017 with 2.10 and the site was dean since 2021 because of the rising PHP versions.
I did the following:
1. Backup of all files from the website and the database.
2. Uploading unzip.php and the WebsiteBaker-2_13_6_R237.zip package.
3. Run unzip.php, starting the link in the admin panel, updating the config.php was successful.
4. Confirming all the switches and start.

For a short moment the upgrade runs and then stops at:

--- Code: ---WebsiteBaker Upgrade
This script upgrades an existing WebsiteBaker 2.10.0 (r66) installation to 2.13.6 (r237) Patch 237.
The upgrade script changes the existing WB database to reflect the changes introduced with newer versions.

Step 1 Your database db124350001 has 7 total tables from 7 included in package
Step 2 : clear Translate cache if exists
Step 3 : Adding/Updating database core tables
Upgrade Core Tables OK
Step 4 : Adding/Updating publ_date sections table
Upgrade sections Table (publ_end field) OK
Upgrade sections Table (empty title field) OK
Step 5 : Updating Administators system permission
Updating Administators system permission OK
Step 6 : Modify PRIMARY KEY in settings table and add missing entries
Upgrading table `settings` succesfully done OK
Step 7 : Updating default_theme/default_template/default editor in settings table
default_theme: already exists. OK .
default_template: already exists. OK .
wysiwyg_editor: already exists. OK .
Step 8 : Adding/Updating settings table
redirect_timer: already exists. OK .
sec_anchor: already exists. OK .
er_level: already exists. OK .
website_signature: already exists. OK .
dsgvo_settings: already exists. OK .
twig_version: already exists. OK .
groups_updated: already exists. OK .
page_icon_dir: already exists. OK .
system_locked: already exists. OK .
string_dir_mode: already exists. OK .
string_file_mode: already exists. OK .
user_login: already exists. OK .
confirmed_registration: already exists. OK .
page_newstyle: already exists. OK .
page_oldstyle: already exists. OK .
jquery_version: already exists. OK .
show_start_datetime: already exists. OK .
rename_files_on_upload: already exists. OK .
debug: already exists. OK .
media_width: already exists. OK .
media_height: already exists. OK .
mediasettings: already exists. OK .
media_version: already exists. OK .
Mediaversion already updated OK
Mediasettings no updrade needed OK
sec_token_fingerprint: already exists. OK .
sec_token_netmask4: already exists. OK .
sec_token_netmask6: already exists. OK .
sec_token_life_time: already exists. OK .
wbmailer_smtp_port: already exists. OK .
wbmailer_smtp_secure: already exists. OK .
Step 9 : Upgrading menu_link
Adding field redirect_type to mod_menu_link table
'redirect_type' already seems exists. OK .
Step 10: Remove deprecated and old files
Step 11: Remove deprecated and old folders
Step 12 : Upgrading all core addons with a newer version
[01] : Upgrade Core Addons admin/media
[02] : Upgrade Core Addons admin/settings
Step 13 : Force Upgrading all addons with a newer or equal version
[01] : Upgrade module WBLingual from version 2.0.9 to version 2.0.9 OK
[02] : Unproofed Modules anynews are not be upgrading automatically
[03] : Unproofed Modules backup are not be upgrading automatically
[04] : Unproofed Modules bookmarks are not be upgrading automatically
[05] : Upgrade module captcha_control from version 2.2.3 to version 2.2.3 OK
There was an uncatched exception
array_merge(): Argument #2 must be of type array, null given
in line (686) of (/framework/helpers/PreCheck.php):
--- End code ---

...and that's it.
I can go back to the admin panel and have a look through the settings, but I just don't know what to do.
Been running WB for a very long time, even on my own website, but I never run into any error while upgrading.

Hopefully someone knows what to do. Thanks in advance.

Adding last line from /var/log/php_error.log.php

--- Code: ---Mon, 10 Feb 2025 21:40:20 +0000 [E_WARNING] /framework/helpers/PreCheck.php:[686] from /framework/helpers/PreCheck.php:[689] bin\helpers\PreCheck::rm_full_dir "Undefined array key "file""
--- End code ---

sternchen8875:

--- Quote ---[05] : Upgrade module captcha_control from version 2.2.3 to version 2.2.3 OK
There was an uncatched exception
array_merge(): Argument #2 must be of type array, null given
in line (686) of (/framework/helpers/PreCheck.php):
--- End quote ---

What is the next module in the folder /modules after the captcha_control-folder?
this one makes the problems
normalize, it must be one from the ModuleWhiteList (see this file in install-folder of the WB-package)

for a fast help, you can rename the file upgrade.php to something else, recommended: upgrade_orig.php (orig for "original") in this next folder after captcha_control-folder

If the upgrade-script not found a file with the name "upgrade.php" in the module-mainfolder, it goes to the next folder

But.....
i'm wondering about the error message and not sure, whats happend. The only point in the upgrade-script, where it use the function rm_full_dir() is there, when it start to remove some old files. The error say's, the function search in a directory, but this is empty, no files inside or it cannot read this folder.
but normalize, its not the right time, to start the function rm_full_dir()
i miss the other core modules in your upgraded list. next core-module after the captcha_control-module is the ckeditor, then code-module, then droplets etc. And the upgrade-script check only the core-modules, means everything in the folder /modules inside of the wb-package

the upgrade-script was nearly finish, when it stops, it checks the version numbers from the core-modules and upgrade this version-numbers, if needed.
After that step, it remove some unneeded files and thats all - so we can say, WB has to work

you can start the upgrade-script again (and again and again) if you want. Maybe the connection was broken for a second, but check the modules

if you get the same error, we can look at this, but need access to WB and FTP - or you send me a ZIP-File from the whole modules-Folder

gonzo99:
Oh wow, thanks a lot for your detailed comments.
And yes, renaming the upgrade.php file in the ckedit directory hit the nail. The upgrade script now completes and the site is online.
There are lots of errors now like the old template which cannot be used anymore, the aged newsletter module which has been working up to 2.10 and others.
But I am willing to fight these errors. :-) Again, thanks a lot for your comments, I appreciate that very much.

sternchen8875:
(Y)

We are here if you need help :wink:

Navigation

[0] Message Index

Go to full version