Home›Support›English Support›[Escalated to WPML Developers team] icl_string_positions position_in_page should be relative
[Escalated to WPML Developers team] icl_string_positions position_in_page should be relative
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.
Elementor users - please update WPML to the latest version to maintain compatibility. More details here - https://wpml.org/changelog/2024/12/wpml-4-6-15-critical-update-for-elementor-sites/
Background of the issue:
I am trying to ensure that the icl_string_positions 'position_in_page' column stores paths relative to ABSPATH. This is important because when migrating to a new server or in a multi-server environment, where the ABSPATH isn't identical on all servers, it can lead to unnecessary writes and duplicate data. For example, the previous server had /var/www/vhosts/client-123/wp-content/themes/twentytwentyfour/functions.php and the new server has /var/www/vhosts/client-987/wp-content/themes/twentytwentyfour/functions.php. By storing it relative to ABSPATH, like wp-content/themes/twentytwentyfour/functions.php, this issue is fixed.
Symptoms:
Described above
The WPML AI support tool rewrote my text and completely changed the meaning. When clicking back, I lost the text I originally wrote 🙁
thanks for contacting us. As I understand you are suggesting a change and improvement in our plugin / DB.
To understand it better and to be able to escalate we would need to reproduce in on the test site. I have prepared it, can you please go to the next link and show us an example of this problem / share steps on how this can be reproduced?
What is unclear about the provided description? Look at the DB at the provided install, if icl_string_positions table 'position_in_page' column has anything in it, you will see the issue. If not, do whatever action that will cause WPML to populate it to see the issue
I have managed to reproduce it after enabling "Look for strings while pages are rendered" and "Track where strings appear on the site" and then migrate the website to a new domain.
I have escalated this to our 2nd tier to check and advise further, I will update you when I have some news.
