This thread is resolved. Here is a description of the problem and solution.
Problem: The client was unable to translate some custom added post types. Clicking the '+' to add translations loaded a blank page, with Safari reporting 'Safari can’t open the page' and Chrome showing an 'ERR_EMPTY_RESPONSE' error. Solution: 1. We installed the WPML SEO addon plugin to ensure compatibility. 2. We disabled and then re-enabled the Yoast SEO and Yoast Duplicate plugins. 3. We cleared the WPML cache. Additionally, we noted that some errors might be related to the use of PHP 8.2.6, which isn't fully compatible with WordPress. We recommend checking the compatible PHP versions with WordPress here: WordPress and PHP Compatibility.
If this solution doesn't look relevant, please open a new support ticket in the WPML support forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
I cannot translate some custom added post types. The + is there to add translations, but this loads a blank page. In Safari it says “Safari can’t open the page”, and Chrome gives an “ERR_EMPTY_RESPONSE” error.
Languages: English (English )French (Français )Arabic (العربية )
Timezone: Pacific/Easter (GMT-06:00)
Hello,
Thank you for your patience,
The issue should be fixed now, I honestly not sure what caused it as I made multiple changes :
1- I found errors related to your SEO plugin, So I installed WPML SEO, our addon plugin that insures compatibility with us
2- I disabled Yoast SEO and Yoast Duplicate plugins and enabled them again
3- Deleted WPML cache
I even just tried your steps above, but on the hidden link site. I've disabled both Yoast plugins, added WPML SEO, and cleared all WPML cache settings. Still no luck.
Languages: English (English )French (Français )Arabic (العربية )
Timezone: Pacific/Easter (GMT-06:00)
Hello,
I recorded a video that explains what I found and how to fix this error: hidden link
One more note to add that I forgot to mention in the video, some errors are related to WordPress in general that could also explain this, I've reviewed the debug log, it seems the errors are related to deprecated functions, which might be occurring because of the use of PHP 8.2.6 As of now, PHP 8.2 isn't fully compatible with WordPress.
Thanks for all your help, Ilyes! As for the huge debug.log, this is only so big because full stack tracing is turned on. So even just 2 or 3 warnings will produce hundreds of lines of debugging logs. Most of it is just PHP Deprecated: Using ${var} in strings is deprecated, use {$var} instead.
Thanks for all your help, Ilyes! As for the huge debug.log, this is only so big because full stack tracing is turned on. So even just 2 or 3 warnings will produce hundreds of lines of debugging logs. Most of it is just PHP Deprecated: Using ${var} in strings is deprecated, use {$var} instead.
Merci merci!
😉
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
