[Resolved] elementor spacer element is being translated in WPML
This thread is resolved. Here is a description of the problem and solution.
Problem: The client reported that WPML has been displaying fields in the translation interface related to the 'spacer' element from Elementor, which was not initially present but appeared recently. Solution: We recommended the client to ensure that both their development and production environments are identical in terms of plugins, configurations, and server settings. We suggested performing monthly maintenance and updates to keep the system up-to-date. After the client performed these updates and forced a refresh of the WPML translation status on the affected pages, the issue was resolved. If you're experiencing this issue, we recommend ensuring your environments are consistent and performing regular updates. If the problem persists, consider refreshing the WPML translation status on the affected pages.
Please note that this solution might be outdated or not applicable to your specific 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 the issue persists, 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.
For some time now, WPML has been displaying fields in the translation interface relating to the ‘spacer’ element from Elementor.
I would like to know if there is a way to prevent this from appearing in the translation system.
I haven't been able to find any information on this subject regarding the spacer element. It didn't appear at first, but it has recently come to appear.
I’ve done everything I can to reproduce the problem.
I actually have a development copy of the public website. This development site is an exact copy of the public website. And even on this development site, the issue simply does not occur. I also tried on your test site by installing an extension that I thought might be the cause of this, but to no success. It is very strange because the two websites that I have are exact copies, apart from a few pages more or less.
It’s not necessarily a major problem, but as I can’t seem to pinpoint the cause at all, I’m not sure how else I can help with this ticket...
Thank you for your effort in testing this, it is appreciated.
If the issue is not happening on the development copy, that is actually a good sign as it means something specific on the live site is causing it.
In that case, we should focus on what differs between the two environments, such as active plugins, caching, server configuration, or any recent changes on the live site.
Please let me know if you can provide steps and access to the live site or a staging version that still reproduces the issue, so I can take a closer look and help identify the exact cause.
Beginning of next week, I will do the monthly maintenance job on each website (production and dev). As far as I know, the only difference between the test and production environments is that the production environment has a larger PHP memory limit. The plugins are the same, configuration the same and with the same web server... As I’ll be carrying out maintenance early next week, can I come back to this ticket once that’s done? This would allow me to have an up-to-date system and backups containing the latest versions before granting you access, if the problem persists after the updates.
Please go ahead with the maintenance and updates, and feel free to return to this ticket once everything is up to date. Having the latest versions and a fresh backup in place is definitely a good approach before we proceed with further debugging.
I made a change to the pages where I had noticed the problem to force WPML to refresh the translation status, and I found that the problem had disappeared – no doubt thanks to the updates. The updates I had made before creating this ticket had not had that effect.
