Search Replace DB not working correctly when moving development domain

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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	-
-	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	-

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Tagged: Exception

This topic contains 1 reply, has 2 voices.

Last updated by Long Nguyen 1 year ago.

Assisted by: Long Nguyen.

Author	Posts
November 7, 2023 at 1:04 pm #14747319
PA_Facts_2000	Hello, We have moved our development site to a new server domain (hidden link) but when I want to change the urls of the old domain (hidden link) with Search and Replace DB, my server performance memory limit is going trough the roof. Like there is some loop within the urls.. If I leave the website as it is (without the replacement of urls) I keep a lot of broken images and pagelinks but the site is working fine. We found out that some strings aren't translated because of coded field_data (base64) inside wp_icl_translate. This topic is a bit the same: https://wpml.org/forums/topic/changing-site-url-in-wp-db/. What can I do to fix this and what happens when we push the site to the live domain? Do we have to fix and repair everything again?
November 9, 2023 at 8:24 am #14762951
Long Nguyen Supporter Languages: English (English ) Timezone: Asia/Ho_Chi_Minh (GMT+07:00)	Hi Pyter, Thank you for contacting WPML support, I'd be happy to help you with this issue. Let me share the feedback of our 2nd tier support about that case if you use WP CLI to search and replace the URL after moving the site. First to the point: - The table icl_translate contains all of the data encoded in base64 format and not only some entries. - Some page builders also encode their strings... WP-CLI will not replace their values as well - In ALL cases the table icl_translate is used only to store translation data. The actual data that is populated in the post (the page builder in the post content or in the postmeta) respects the page builder's way of saving the values. If the value there is not encoded, it won't be encoded there. So having said that, when you change the URL of your WordPress instance, you should not make any changes in the icl_translate table as that is only a snapshot of the page builder package. In any case, the page if the structure is changed will go to "Needs Update" status and a NEW job with the NEW content will be created. Because of how we handle internal URLs the value will be adjusted properly (if the page builder field was registered as a LINK type field) and there should be no issue whatsoever. The data in use will be adjusted in the post contents by WP-CLI because there (unless the page builder encodes its data) is not encoded. So in your case, after searching and replacing URLs, you also need to update the translation of those strings or the page. I hope that makes sense.

The topic ‘[Closed] Search Replace DB not working correctly when moving development domain’ is closed to new replies.