Home›Support›English Support›[Resolved] There is Bug with recent WPML 4.74 where some blog post could not be loaded.
[Resolved] There is Bug with recent WPML 4.74 where some blog post could not be loaded.
This thread is resolved. Here is a description of the problem and solution.
Problem:
The client was experiencing following critical error when loading blog posts using WPML 4.7.4, and after rolling back to a previous version, some translators were unable to access translation jobs.
Uncaught TypeError: WPML\PB\Elementor\DataConvert::serialize(): Argument #1 ($data) must be of type array, null given
Solution: We identified that the issue with the critical error was related to a known problem documented in our errata. We recommended applying the workaround mentioned in the errata, which can be found here: https://wpml.org/errata/elementor-critical-error-on-woocommerce-product-pages/. We advised the client to apply this solution on their live site after taking a backup. Additionally, we suggested subscribing to the comments of the errata to stay updated on any developments.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at 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.
Background of the issue:
I was trying to load some blog posts using WPML 4.74, but encountered issues that led to a critical error on the site. After rolling back to a previous version, some translators are unable to access translation jobs.
Errorr: impossible to assign project/job to translator
Symptoms:
Some blog posts could not be loaded, causing the site to go into a critical error. After rolling back to an older version, some translators cannot access translation jobs.
Questions:
Why are some blog posts causing a critical error with WPML 4.74?
Why can't some translators access translation jobs after rolling back to an older version?
Can you please provide details about the critical error, you found with 4.7.4? For example an error log showing detailed dump of the error. You may need to enable debugging in your site. See https://wpml.org/documentation/support/debugging-wpml/ for details.
Additionally, about rolling back to a previous version, did you mean you restored a previous site back or the WPML only? However, in this case, can you please go to WPML -> Translation Management -> Translators and check if the users having trouble assigning a translation, are added as translators with proper language pairs? Please see https://wpml.org/documentation/translating-your-contents/how-to-set-up-local-translators-and-language-pairs/ for details.
Thank you for the updates. I see that error is referring to a compatibility layer with Elementor.
Can you please try the following?
1) Take a full backup of your site and database before proceeding. It is highly advised to try these on a dev or staging site first, so your live site isn't compromised.
2) Deactivate all plugins except WPML and String Translation.
3) Switch to a standard theme like 2024 or 2021.
4) Check for the issue if it still happens.
5) Then start activating plugins one by one, starting with Elementor, while keep checking for the issue. This way you 'll be able to pinpoint a conflict when & where it starts creating the problem.
6) If after activating all plugins you see that it still works fine, then switch to your theme and see if that's causing it.
Please let me know your findings and I'll try my best to help you further on the matter.
Apparently looked like that the issue was coming when Elementor Pro was active, but, particularly with elements from "Essential Addons for Elementor" plugin.
However, upon further investigation, there seemed to be an incomplete save process for hidden link. It was either in this post or the used "New Single post" elementor template (hidden link).
The issue was evident when I tried to edit one of the above, with Elementor Pro active.
So I did the following:
- Deactivated Elementor Pro and "Essential Addons for Elementor" plugins (pro version also).
- Opened the post for editing in WordPress editor.
- Saved.
- Further clicked it to open with Elementor for editing.
- Saved in Elementor.
- Clicked the "Edit Single Post" from within the Elementor (see attached).
- Clicked "Save and leave" when asked.
- Elementor then loaded that single post template for editing. Here I simply exited to WordPress and didn't make any change.
This resolved the previously incomplete save process which was breaking the structure and was throwing the fatal error. And now the post loads perfectly fine on the frontend.
In short, you can either try the above mentioned. Or can simply, reopen such post having this problem, to edit with Elementor and simply resave. At max, you may need to deactivate Elementor Pro and "Essential Addons for Elementor" plugins temporarily.
Once these posts are resaved, these should work fine on the frontend. Please let me know after trying the above mentioned.
Hello Hasan, thank you for your reply and the explanation but that does not solve the issue as this applies to most number of blog posts, de-activating Elementor Pro and Essential Add-on does not solve the issue as you are saying.
hidden link
For example when you check that blog and more others the issue is still there but I disactivate WPML the issue is resolved.
Thanks for the suggestion. I tried the procedure you mentioned—deactivating the plugins temporarily, resaving the post, and then reactivating them—but unfortunately, it's still not working on my end.
Let me know if there's anything else I should try.
I tried these steps after deactivating all other plugins (in the video you can watch the ones are active):
- Opened the post for editing.
- Clicked Edit with Elementor.
- Saved the post in Elementor (if Publish button isn't active in Elementor, just make a little change like a word or dot in the content).
- Checked the post in frontend (hidden link) and it is working fine now.
- Activated all the plugins back.
