Home›Support›English Support›[Resolved] New domain name structure on /blog/ string translations cant find theme folder
[Resolved] New domain name structure on /blog/ string translations cant find theme folder
This thread is resolved. Here is a description of the problem and solution.
Problem: The client moved their development site to a new domain and encountered issues with string translations not connecting to the theme folder due to a change in the file structure. The client was unable to add translations or find new or changed PHP strings.
Solution: We suggested that the issue might have occurred during the migration process and recommended using the Duplicator plugin to ensure a proper migration. This plugin helps with replacing old URLs in the database with new ones during the migration.
If the client had not started translating or was still in the testing phase, we also recommended resetting WPML:
Go to WPML → Support and click the Troubleshooting link.
In the Reset section of the Troubleshooting page, select the 'I am about to reset all translation and language data' checkbox.
Click the 'Reset and deactivate WPML' button.
WPML Reset Documentation We advised creating a backup before performing the WPML reset as it cannot be undone and all translations sent to remote services will be lost.
If the provided solution is not relevant due to being outdated or not applicable to your case, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please open a new support ticket.
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.
I have just moved our dev site from dev.trustandtravel.com to trustandtravel.com/blog, i believe the string translations cannot connect to the theme folder due to the extra folder within the file structure - /blog/wp-content/themes/ttblog-theme rather than /wp-content/themes/ttblog-theme - (which is what it was before).
This sounds to me like an issue that took place in the migration process, because, all the old URLs that exist in the database should be properly replated in the migration process with the new domain.
Here is a small tutorial on how to use Duplicator: hidden link
This should perfectly migrate your website maintaining the exact same setup and also taking care of the search and replace process so that the old links will be overwritten with the new URLs of the new domain you are migrating to (in case you are also changing the domain and not only the server).
I hope that you will find this helpful 🙂 I use only Duplicator each time I want to migrate WP websites. They also have a premium version but if you don't have a huge website with a huge database, the free version should work fine.
I dont need a plugin to migrate websites, i am a developer who has done this for many years and migrated many sites.
The site migrated well, my problem is that WPML is not finding the theme folder when searching for strings due to the unusual domain structure of the blog site being with the folder trustandtravel.com/blog instead of just trustandtravel.com.
And im asked how i can get it to re-find the folder with the new domain structure.
Thank you for sharing your feedback. I understand that you are a developer, and I suggest testing the method of moving the site as Mihai suggested. Speaking from personal experience, I have moved many sites using the Duplicator plugin and have not encountered any issues after the migration is complete.
You can also try to regenerate .mo files. To do this, you can go to WPML -> Support -> Troubleshooting page and click on the "Show custom MO Files Pre-generation dialog box" button. Then, in the dialog box that appears, click the blue button to regenerate custom MO files.
Thanks for your help, i have noticed when searching for strings it IS finding the new ones - IE the number of strings found goes up, however they are not showing in the strings table.
It is still not letting me add translations either - i get translation failed.
Does this give you an indication of what might be going wrong?
Also, i dont not have a regenerate MO files button, I only have a - Show custom MO files Pre-generation dialog box.
Which i clicked and it said: WPML needs to generate .mo files, so i click generate .mo files
But the box on the troubleshooting page doesnt change to re-generate.
Where are these MO files stored on my server?
Is this the issue? The connection between the MO files, my theme and the string translation table?
Is there another cache to flush or something to make it all reconnect?
this is in the error log - does this mean anything?
Date Event Description WPML Job ID ATE Job ID Extra data
2024/04/09 11:05:13 AM ATE Server Communication Unable to authenticate 0 0 {"url":"https:\/\/ate.wpml.org\/api\/wpml\/languages\/check_pairs","requestArgs":{"method":"POST","body":[{"source_language":"en","target_languages":["fr","de"]}]},"status":"auth_error"}
I have copied the site back onto its original domain and i am having the same issue - hidden link. I dont believe its a problem with the domain or transfer.
When scanning the theme for strings it just crashes the page - IE loads forever, isnt finding the new strings.
Can you advise?
I add a new string - <?php _e('test', 'ttblog-theme'); ?> into say the header template.
I upload it, go to Themes & Localisation > check my theme, hit scan.
It just loads for ever OR finds the new string but does not show it in the table – see screen shot.
I have turned debug on, and on the Translation Management page i have this error:
Fatal error: Uncaught InvalidArgumentException: No translation entry found for query: s:42:" element_id = %d AND element_type LIKE %s ";a:2:{i:0;s:4:"9919";i:1;s:5:"post%";} in /var/www/vhosts/h11.web17.wh20.easyname.systems/htdocs/website/blog/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-icl-translations.php:193 Stack trace: #0 /var/www/vhosts/h11.web17.wh20.easyname.systems/htdocs/website/blog/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-icl-translations.php(59): WPML_TM_ICL_Translations->select_translation_id(' element_id = %...', Array) #1 /var/www/vhosts/h11.web17.wh20.easyname.systems/htdocs/website/blog/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-icl-translations.php(41): WPML_TM_ICL_Translations->build_from_element_id(Array) #2 /var/www/vhosts/h11.web17.wh20.easyname.systems/htdocs/website/blog/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-records.php(139): WPML_TM_ICL_Translations->__constru in /var/www/vhosts/h11.web17.wh20.easyname.systems/htdocs/website/blog/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-icl-translations.php on line 193
There has been a critical error on this website. Please check your site admin email inbox for instructions.
Looks like its coming from within the plugin...? Is this the problem im having? How do i fix it?
[11-Apr-2024 16:34:44 UTC] PHP Fatal error: Uncaught InvalidArgumentException: No translation entry found for query: s:42:" element_id = %d AND element_type LIKE %s ";a:2:{i:0;s:4:"9919";i:1;s:5:"post%";} in /var/www/vhosts/h11.web17.wh20.easyname.systems/htdocs/website/blog/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-icl-translations.php:193
Stack trace:
#0 /var/www/vhosts/h11.web17.wh20.easyname.systems/htdocs/website/blog/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-icl-translations.php(59): WPML_TM_ICL_Translations->select_translation_id(' element_id = %...', Array)
#1 /var/www/vhosts/h11.web17.wh20.easyname.systems/htdocs/website/blog/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-icl-translations.php(41): WPML_TM_ICL_Translations->build_from_element_id(Array)
#2 /var/www/vhosts/h11.web17.wh20.easyname.systems/htdocs/website/blog/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-records.php(139): WPML_TM_ICL_Translations->__constru in /var/www/vhosts/h11.web17.wh20.easyname.systems/htdocs/website/blog/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-icl-translations.php on line 193
Yes, this fatal error prevents from finishing the scanning. Could you explain how you moved your website when the problem first occurred?
I feel that not the entire website has been moved, which could explain the missing entries in the database.
If no translating has been done yet, and this is in the testing stage, I suggest resetting WPML and setting it up again.
1. Go to WPML → Support and click the Troubleshooting link.
2. In the Reset section of the Troubleshooting page, select the I am about to reset all translation and language data checkbox. Then, click the Reset and deactivate WPML button.
The usual way - i moved the files to the new folder, changed the url in the database (site and home), updated permalinks.
Translating has be done, so i would prefer not to loose all the data.
However if this is the only option, will it only loose the strings? Or all the translated pages?
Is there a way to re-upload/re-update the plugin without loosing data? Or fix those files with WPML without loosing data?
If the translations have already been completed, resetting WPML is not a viable solution.
I need to request temporary access (wp-admin and FTP) to your site – preferably to a test site where the problem has been replicated if possible – in order to be of better help. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Please include steps to replicate the issue, except if there is something else besides theme scanning.
Thank you for your help, but i have resolved the issue by completely restoring the original database to before the transfer and re-pointed it to the new site - would have been a quick fix if suggested earlier, hope this helps someone else in the future!
I am glad to hear that it works now. I hope you have a lovely weekend ahead!
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
