My Laytheme doesn't work with PHP 8.0
-
Hello,
I just updated my Ionos account to PHP 8.0 for this site: https://practice.de/
After that the up-to-date Laytheme site doesn't work anymore.See the error message attached. Is that due to a Polylang problem? I understand nothing.
I now switched back to PHP 7.3, but I really need this update otherwise I need to pay Ionos 8 € a month for their extended PHP support.
Any ideas on how I could solve that?
BEN
-
Dear Ben
@doorofperception
Sorry that this has happened, do you now have any access to your Wordpress admin area?
Luckily the fatal error message is clear that the problem occurred within Polylang.
I would suggest de-activating Polylang, updating Lay Theme & any addons to newest version, then updating with Ionos to PHP 8.0 ( so you dont have to pay 8 euro a month ).
If all still working well, from there we can isolate the problem to Polylang and go from there.
The main thing is to get Lay Theme working, your site not crashing and you not paying any extra money 🌝
Talk soon
Richard
-
Hey Richard,
Thank you for the reply.
The site is up and running and I have access to the WP admin area, because I switched back to the old PHP version.Laytheme and all other plugins are up-to-date.
Deactivating Polylang doesn't solve my problem besides giving me clarity about the troublemaker.
But the multilanguage support is crucial for the site. And Polylang seems to be the only plugin that achieves. I used WPML for years prior to it and just the thought about it gives me a headache. It never really worked.So Polylang seems to be without any alternative.
What do you suggest now?Thank you — Ben
-
Dear Ben
@doorofperception
Great that all is working with Lay Theme & Admin area 👍
While Polylang is de-activated will you update to PHP 8.0 for confirmation all is working with Lay Theme?
Here within VERSION HISTORY:
Polylang, being a third party plugin
You may want to consult them about issues with PHP 8.0 to confirm how much is Lay Theme related.What Polylang version are running?
Are you running Polylang with Woocommerce?The error message occurs within the
polylang-slug.php
file at line31
. You might want to inspect this file on line 31 and make a note/screenshot of error.This would involve going into the plugins folder/files
The error message also mentions "homepages" and "practice" do these mean anything to you? is practice a page?
I should also mention QtranslateXT but understand that you would prefer the solution to come with Polylang 👍
Polylang is recommended on the Lay Theme Documentation page, so will forward to Armin for any thoughts ✅
Talk soon Ben and thank you for supporting Lay Theme
Richard
-
When I deactivate Polylang the problem does not occur.
I will write to the Polylang people. Thanks for pointing me to their forum.
Btw, I don't use Woocommerce and Polylang is up-to-date.What a bummer.
-
Problem solved.
There's an additional plugin that I need so that Polylang works properly. It's called Polyang-Slug.php and it needs to be updated manually via FTP. After doing that the site works with PHP 8.0.The tipp came immediately after posting it in the WP/Polylang forum. Thanks for the hint.
-
Actually, I cheered too soon.
After I installed Polylang-Slug 0.2.3 the PHP 8.0 update didn’t crash the site and I thought: problem solved.
But the site isn’t multilanguage anymore! Or at least not completely.
Three pages don't show the language switcher anymore, the rest is fine.But it gets even weirder:
When I'm logged in to Wordpress everything works perfectly.The fact that the problem disappears when I log in seems quite special to me. What changes when an admin is logged in? Any ideas?
-
hey can you send your /wp-admin/ login and your ftp login and send a link to this topic and links to the pages where the language switcher does not appear to:
info@laytheme.com ?
Before you post:
- When using a WordPress Cache plugin, disable it or clear your cache.
- Update Lay Theme and all Lay Theme Addons
- Disable all Plugins
- Go to Lay Options → Custom CSS & HTML, click "Turn Off All Custom Code", click "Save Changes"
This often solves issues you might run into
When you post:
- Post a link to where the problem is
- Does the problem happen on Chrome, Firefox, Safari or iPhone or Android?
- If the problem is difficult to explain, post screenshots / link to a video to explain it