Bobby
WPML Supporter since 04/2015
Languages:
English (English )
Timezone:
America/Los_Angeles (GMT-07:00)
|
Thank you for the access details!
After reviewing with our team, the following has happened.
We determined that the issue seems to be more site specific, which explains why on your dev it works but on the production the issue has been happening.
Our team will add the bulletproofing similar to that workaround provided in the next version of WPML to ensure this is prevented.
Regarding the fatal error when saving.
It looks like it works OK for other pages and only affects the homepage at the moment.
Since saving works in Safe Mode, I would like to see the results after running
Elementor → Tools
Regenerate CSS & Data
If possible, try this and let me know your results.
NOTE: Only do this after having a full backup in place.
|
|
|
HI Bobby
I ran
- Elementor > Tools > Clear Files & Data
- Elementor > Tools > Sync Library
- WP Rocket > Clear and Preload Cache > All Languages
- WP Rocket > Clear Used CSS
- WP Rocket > Clear Priority Elements
Tried to make the mini change: babysitters > babysitter > babysitters again.
Same results
When you try the same, you see several errors appearing in Dev Tools. I sent these also to Elementor Support, but they say "if it works in safe mode, then it's due to another plugin or theme". As I explained to them we can't just start switching themes and disabling all plugins etc on our production site, their support ended there, so now I'm stuck with a homepage that I cannot update!
Kind regards
Simon
|
|
|
Hi Bobby
Any more updates here? Does it make sense to move this ticket to a European colleague on my timezone (GMT +1) as you said you would previously after my first request? The updates are not very regular and when you write I'm usually asleep and can't respond immediately, which is further delaying progress!
Kind regards
Simon
|
Bobby
Supporter
|
Hi Simon,
This ticket has been escalated already to our developers team regarding the main issue of the thread.
At the moment there are no updates from their side as we are working on creating a permanent fix.
Regarding the issue with the fatal error when saving at the moment outside of safe mode for the homepage only, we are still testing and will update you.
I can re assign the ticket to another colleague but since the case is already escalated at this point i'd advise against it as that could create confusion.
|
|
|
Hi Bobby
WPML has released a new update. On their changelog it states:
- Elementor: Fixed a PHP 8+ fatal error that happened when using Display Conditions.
1) Should our issue now be addressed with that update?
2) Do I need to revert any files, or will the plugin update take care of that automatically by overwriting the affected file?
Kind regards
Simon
|
Bobby
Supporter
|
Hi Simon,
I can confirm that the latest release of WPML (4.9) resolved the issue you were experiencing.
Simply updating the plugin should overwrite the previous changes we made with the latest version.
Let me know your results, please.
|
|
|
Hi Bobby
I made a change to the homepage - I updated the homepage main photo.
When I tried to save in Elementor, I got another Server 500 error appearing bottom left, and the pink Publish button didn't go grey to indicate that it had saved correctly.
I exited the Elementor editor anyway, then "translated" the page again, using the pencil icon in the pages screen. The resulting dialogue didn't show any changes had been made, which again is not what I expected. I would expect WPML to ask me to translate the metadata from the newly uploaded photo.
I went to WPML > Media Translation and added the missing translations for the newly uploaded photo.
However I'm not convinced that everything is working as it should yet.
Kind regards
Simon
|
Bobby
Supporter
|
Hi Simon,
To verify that this is the same issue we have resolved in 4.9 please review the following:
Original issue:
When using Elementor Display Conditions + WPML + PHP 8.0+ the following fatal error is thrown
We were able to temporary fix this by adjusting the code.
With the latest version of WPML 4.9 you should no longer need that "workaround" and it should work now without that Fatal Error thrown.
Fatal error: Uncaught TypeError: Cannot access offset of type string on string on Elementor/Hooks/DisplayConditions.php
Can you please confirm this?
If there is still an error 500 or the issue with the data not being updated, I will review and we can further debug as it might be related to a completely different trigger.
|
|
|
Hi Bobby
I just made a tiny change ("babysitters" to "babysitter" and back again) on our homepage and saved. Saw the Server Error bottom left again.
Saved debug.log available here: hidden link
Kind regards
Simon
|
Bobby
Supporter
|
Hi Simon,
I was able to reproduce, working on this and will update you as soon as I have additional feedback.
|
Bobby
Supporter
|
Hi Simon,
After testing we found that there are 2 buttons corrupted
[in _elementor_data, when you add a new button it has an encoded string in display conditions.
While the corrupted buttons have the decoded string.]
See screenshot.
The best way to resolve would be to delete and recreate these buttons.
Are you able to do this, and is the issue with only this page and these 2 buttons or more?
At the moment we are testing a script that could possibly resolve this globally but the above workaround would be the fastest way to resolve this.
Let me know your results, please.
|
|
|
Hi Bobby
Which two buttons exactly are corrupt? 🤔 I couldn't work out the significance of your screenshot if I'm honest. If it's just two buttons, I'm sure I could fix it myself. 😜
Kind regards
Simon
|
Bobby
Supporter
|
It's the "Find a native nanny" and "Find a job" buttons in the homepage hero section right underneath Finde Kinderbetreuung in deiner Sprache, these 2 buttons are not working as expected where if you add new buttons they work OK.
Let me know your results, please.
|
|
|
Hi Bobby
Sorry, I feel really stupid! 😊 Sometimes you can't see the wood for the trees! I'm almost blind to those buttons cuz I've seen that page so often! I didn't even think to look there.
I recreated the two buttons and now the saving works correctly and the pink Elementor Publish button goes grey as I would expect. Great so far!
However, when I exited the Homepage in Elementor and clicked the Pencil icon to translate the new buttons into German, the translation page appeared and said it was all 100% done. I inspected the German page, the buttons were still in English, and I had to go through the whole rigmarole of Translations Dashboard > Pages > Send to Translations > Go to Translations > Translate etc. This time the buttons appeared as UNtranslated ??
I translated them and now everything works as expected, but can you explain why the translations "appeared" translated before when clicking the Pencil icon? Is that not supported any longer to use the pencil icon directly from the WP Admin > Pages screen? If so, why is this pencil icon still available?
Kind regards
Simon
|
Bobby
Supporter
|
I agree, and I'm glad that it's working now!
Regarding the update -- there is a potential the translation was "stuck", and that the change was considered minimal enough to not trigger the update, I can't say if this is a bug or possibly a one time issue.
Are you able to reproduce it or experience this with any other items?
|
