WebsiteBaker Community Forum

WebsiteBaker Support (2.13.x) => General Help & Support => Topic started by: mikejd on October 30, 2021, 04:53:46 PM

Title: Backend problems following upgrade
Post by: mikejd on October 30, 2021, 04:53:46 PM
I was having difficulties with the backend of my website running v2.12.2 and someone suggested I could upgrade to v2.13. I did this and my previous problem which seemed to be with the CK Editor persisted. Then I started having other problems with pages loading and getting error messages about missing files.

I can open the Administration  but then have errors for some of the main menu choices which are making the whole thing unusable.

Pages
OK
Modify pages:
Template Error: filename: file /homepages/39/d578174769/htdocs/wb/admin/themes/templates/pages_expert_modal.htt does not exist.
Halted.

Media
OK

Add-ons
There was an uncatched exception
missing template file addons.twig
in line (1123) of (/framework/class.wb.php):

Preferences
OK

Settings
OK

AdminTools
OK

Access
There was an uncatched exception
missing template file access.twig
in line (1123) of (/framework/class.wb.php):
Title: Re: Backend problems following upgrade
Post by: hgs on October 30, 2021, 05:19:13 PM
I hope you have a backup of the site and database.

Were there any error messages during the upgrade?

How was the upgrade done?

We recommend the method with unzip.php, usually there are no problems.

If it doesn't work at all, we can take a look ourselves with the appropriate access data.
Title: Re: Backend problems following upgrade
Post by: mikejd on October 30, 2021, 07:08:06 PM
I was able to backup the files but not the database. I may have a previous database backup but I can't access at the moment. The site is working fine, it's the administration that's a problem.

I upgraded using the unzip.pup file, and I don't think there were any error messages.
Title: Re: Backend problems following upgrade
Post by: hgs on October 31, 2021, 08:08:26 AM
Sorry for the questions, but I ask step by step.

1. So you uploaded the zip file of WB 2.13 and the unzip.php via ftp?
2. You have unzipped the zip file of WB 2.13 with the call in the browser?
Code: [Select]
http(s)://yourdomain.tld/unzip.php
3. You have logged in as superadmin with the call in the brwoser?
Code: [Select]
http(s)://yourdomain.tld/admin
4. Then a link to the update-script should have appeared.
Was that the case?

Because only this administrator is authorized to start the upgrade-script.

Did the updrade-script run through without any red text output?

Translated with www.DeepL.com/Translator (free version)
Title: Re: Backend problems following upgrade
Post by: mikejd on October 31, 2021, 10:39:04 AM
1. So you uploaded the zip file of WB 2.13 and the unzip.php via ftp?
Yes

2. You have unzipped the zip file of WB 2.13 with the call in the browser?
Code: [Select]
http(s)://yourdomain.tld/unzip.php
Yes

3. You have logged in as superadmin with the call in the brwoser?
Code: [Select]
http(s)://yourdomain.tld/admin
As far as I know, yes. I can't access the user page to check the ID.

4. Then a link to the update-script should have appeared.
Was that the case?
Yes

Because only this administrator is authorized to start the upgrade-script.

Did the updrade-script run through without any red text output?
Yes, at least as far as I remember.


changed for better readability
Title: Re: Backend problems following upgrade
Post by: hgs on October 31, 2021, 02:51:35 PM
ok, then we need the access data for:
WB USER ID 1 (Superadmin)
Name
Password

and the access data for the FTP client

as pm
Title: Re: Backend problems following upgrade
Post by: mikejd on November 01, 2021, 01:00:23 PM
I've tried to send PM but cannot access your profile, just get error message saying not allowed.
Title: Re: Backend problems following upgrade
Post by: mikejd on November 01, 2021, 01:33:08 PM
/\ Edit - pm now sent
Title: Re: Backend problems following upgrade
Post by: hgs on November 02, 2021, 05:37:40 PM
For all readers, the site is now running again in BE as it should.
The error was a slash after the domain in the config.php.
This has been removed and now the pages can be edited in the BE again.