WBCE CMS – Way Better Content Editing.
Du bist nicht angemeldet.
Seiten: 1
Hello
I have prepared new site with WBCE 1.4.2. It is working properrly on WAMP. I moved it to working server and after it I can not login to admin. White blank page is displayed when I try to login to cms.
Colud you please suggest me how can I solve the problem.
Regrads
Gawi
Offline
Make sure
- the system requirements are met (PHP >= 5.6 etc., Unix/Linux OS strongly recommended, MySQL database)
- all files were properly transferred onto the server (no 0-Byte-Files which Filezilla often likes to create)
- the database dump from the development system has properly been imported into the database of the live server
- the information given in the config.php has been edited to represent the live server environment (URL, database)
- the access rights (0755 directories / 0644 files) are correct
- no files were renamend (Webservers are case sensitive, Windows computers are not)
Also check the server's PHP error logfile if possible for any helpful messages.
Beitrag geändert von florian (03.02.2020 16:17:59)
Offline
It is strange - page in working serwer works correctly. Only login page is not displayed.
PHP version 7.3.
Permissions are set correctly.
Offline
Do you think that reinstall cms can help?
Offline
No, this could end in a mess. I'm sure it's only a small issue. If you like, send me FTP / Backend credentials via PM or to support@wbce.org, then I'll have a look at it.
Offline
I sent message via PM
Offline
I'm already looking, it's not as obvious as I thought. Please give me some more minutes.
Offline
Sorry, I can't fix it. It is either an issue with class.admin or class.database.
I've tested some fresh installations: WBCE 1.3.3 works, WBCE 1.4.2 does not work.
Can you ask the webhoster if any PHP error logs are available?
Offline
I will check if it is possible to get php errors tomorrow and I will send them to you.
Offline
Hi
Php warnings are switched on so errors shall be visible.
Offline
Seems to be an issue with the PHP version? Have you downgraded it? When I tried yesterday and it did not work, I'm sure it was PHP 7.3, now it's PHP 7.1, and it's working.
Offline
Yes I change to 7.1
Offline
Do you want to test it on 7.2 or 7.3 ?
Offline
I can check different PHP versions by setting them via .htaccess.
It definitively an issue with PHP 7.3 on that server (7.3.14 as well as 7.3.14-ioncube). The error does not appear with PHP 7.2.
I have no idea what's the reason, I have a very similiar setup (PHP 7.3.14, MariaDB 10.4.12) on another server where these issues do not appear.
For the moment, I can only recommend to use PHP 7.2 on your server.
Beitrag geändert von florian (04.02.2020 12:10:51)
Offline
Thank very much you for your help. I will set 7.2.
Best Regards
Gawi
Offline
Hello
The cause of the problems is that eval () has been disabled on the server starting from php 7.3 upwards. WBCE does not work properly when eval() is disabled.
Offline
Thank you for your feedback.
Just to make it clear: It's no general issue with WBCE CMS and newer PHP versions. WBCE CMS works well on all standard webspaces with PHP 7.2, 7.3, 7.4 and 8.0 (when eval is not disabled).
Actually, there are only a few appearances of eval: the 3rd party libraries Twig and IDNA convert and the WBCE core modules Dropltes and OPF Dashboard.
Offline
As for Twig, look at this issue: https://github.com/twigphp/Twig/issues/2428
Ich habe eine Amazon-Wishlist.
Oder spende an das Projekt.
Ich kann, wenn ich will, aber wer will, dass ich muss, kann mich mal
Offline
OpF Dashboard uses eval() to apply user-defined filters. The filter modules and filter plugins don't need eval().
User defined inline-filters can be converted to plugins to avoid the use of eval(). So, if this is actually the problem in your installation, you could downgrade php to get access to the backend again, convert all inline filters to plugins and upgrade php again to a newer version.
Additionally, but that's a completely different thing: The OpF-Dashboard documentation uses the Javascript function eval() to process links and tooltips.
And for completeness: The Droplets filter module doesn't use eval() - it just might pop up in a recursive search due to a function called evalDroplets() 
Offline
One more side note: the Droplets filter uses the function evalDroplets() which is provided by the Droplets module, and that one calls another function and another one do_eval() which in the end uses eval()
So, you might have to disable the Droplets filter (either completely or for the backend) to get WBCE running smoothly when eval() is not available.
On the other hand, the Droplets concept is one of the cool features of WBCE which I wouldn't want to miss
Offline
Seiten: 1