Terabayashi Yuri
|
Previously, I consulted about an issue where the editing screen turned blank due to a react-dom.min.js error.
At that time, I tried removing and then re-adding the plugin, but the error was not resolved.
Could you please advise if there are any other solutions?
|
Marsel Nikolli
|
Hi,
Thank you for contacting WPML Support, I will be happy to help you.
1) I notice from the debug info that you are using WPML v4.6.7, I would suggest you update to the latest version v4.6.9 (also all the WPML addon plugins that might need update).
2) Also, I noticed that you are using Advanced Custom Fields, please install the Advanced Custom Fields Multilingual plugin.
More information can be found in this link: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/
After, please check if the issue persists and let me know.
Regards,
Marsel
|
Terabayashi Yuri
|
Thank you very much.
I have implemented the solution you mentioned.
However, the error has not been resolved at all.
Send the debug log again if necessary. If so, please let us know how to send it.
|
Marsel Nikolli
|
Hi,
Thank you for the update.
Would it be possible to check if the issue happens in a minimal setup, that meaning:
- set a default WP theme
- keep active only WPML Plugins and ACFML (if there is any custom type/fields you are adding)
- disable all other plugins
- check if the error still persists
- If the issue does not persists, please re-activate your plugins one by one and check the issue each time to find out the plugin that might be causing the problem.
Note: Please make sure you have a full backup (files & database) before trying anything on your website.
Let me know how it goes,
Marsel
|
Terabayashi Yuri
|
Thank you for your advice.
I got the same error even though I changed to the default theme and deactivated all plugins.
There is one more thing that I am concerned about.
This error only occurs on pages. It does not occur on posts or custom posts.
In that case, does that mean the plugin has nothing to do with it?
Please tell me your opinion. thank you
|
Marsel Nikolli
|
Hi,
From what I checked on your previous ticket: https://wpml.org/forums/topic/when-i-activate-the-plugin-i-get-an-error-that-says-react-dom/#post-14785103
and the debug information you provided, I notice that the REST API on your website is disabled, the error showing on the console log might be a false positive.
Does the issue with the editor persists (as you mentioned on the previous ticket)?
|
Terabayashi Yuri
|
I was unable to reply to the previous ticket because I closed it before replying.
Last time and this time, I was able to get the data correctly with /wp-json/.
I think REST API is valid.
|
Marsel Nikolli
|
Hi,
I checked the website link that is in the debug info and I see that the REST API seems to get blocked by CloudFront (please check attached image).
Could you please check if the same error (react js) shows up on the console when you disable the WPML plugins?
|
Terabayashi Yuri
|
I think this is because it is only accessible from specific IPs for security reasons.
If you access from here, it will return correctly.
I also wrote a feature, but I disabled all plugins including WPML, but the same react js error occurred.
|
Marsel Nikolli
|
Thanks for the information.
Since the issue happens when the WPML plugins are disabled that issue doesn't seem to be related to the WPML plugins.
- What I can suggest you try next is to disable all plugins and custom features, switch to WP default theme "Twenty Twenty-One" and check if the error still shows up (It would be better if you check in an incognito browser page).
- If the issue persists in such configuration then the only suggestion would be to create a new fresh WordPress installation and check there if the issue persists even in such case then you would need to check with the hosting support team.
* Note: If everything works with the error showing then it might be just a false positive and you can ignore it.
Kind regards,
Marsel
|
Terabayashi Yuri
|
- What I can suggest you try next is to disable all plugins and custom features, switch to WP default theme "Twenty Twenty-One" and check if the error still shows up (It would be better if you check in an incognito browser page).
↓
As I wrote last time, I changed to the default theme and disabled all plugins.
Even in that case, the error did not go away.
WP itself has also just been updated to the latest version.
There seems to be a problem with the server settings, so I'll ask.
thank you
|
Marsel Nikolli
|
Hi,
I suggested the theme "Twenty Twenty-One", just in case you had used any of the new WP themes, as they are FSE themes and work a bit differently.
As I mentioned before, give that the issue happens without the WPML plugins (or any other plugin/s) it might be something related to the server configuration.
Regards,
Marsel
|
