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

Modify pages backend

(1/2) > >>

RonR:
Just updated 2.12 to 2.13
Used unzip.php
PHP7.3
during update no errors reported.

Cannot access modify pages in backend, getting a HTTP ERROR 500.

Hosting error log:
Backend log: PHP Warning:  require(/home/mydomain/domains/mydomain.nl/public_html/admin//config.php):
failed to open stream: No such file or directory in /home/mydomain/domains/mydomain.nl/public_html/admin/pages/modify.php on line 52\n, referer: https://mydomain.nl/admin/pages/index.php
[Sun Dec 13 06:13:26.507679 2020] [lsapi:error] [pid 4190830:tid 139812719716096] [client 145.133.95.20:60565]
[host www.mydomain.nl] Backend fatal error: PHP Fatal error:  require(): Failed opening required '/home/mydomain/domains/mydomain.nl/public_html/admin//config.php'
(include_path='.:/opt/alt/php73/usr/share/pear') in /home/mydomain/domains/mydomain.nl/public_html/admin/pages/modify.php on line 52\n, referer: https://www.mydomain.nl/admin/pages/index.php


Looks like it is looking for config.php in the wrong place.(/admin//config.php)
How to fix?

Greetz.

hgs:
After the unzip.php did you have a link to the upgrade-script in the backend?
So you could log into the backend?
Was the config.php rewritten when running.
For this you had to press F5 once.

RonR:
Yes, the unzip had a link to the backend, and there I did run the upgrade-script.
I have a autogenerated config-file for 2.13, which is exactly the same as the 2.12 one exept for the comments

*** auto generated config file for 2.13.0
 *** WebsiteBaker upgrade from 2.12.2 to 2.13.0

old one:
*** auto generated config file for 2.12.2
 *** WebsiteBaker upgrade from 2.12.1 to 2.12.2

I cannot recall pressing f5 or being promted to do so.

RonR:
I can remember clearing cache because the layout was messed up.

RonR:
took a step back and renamed my admin to "admin" again.
Then it works OK and get no error 500.

Looks like something is looking for a hardcoded admin and generates a 500 when the admin is renamed.

Prefer for safety reasons to rename the admin directory.

Navigation

[0] Message Index

[#] Next page