we have problems on our production that strings are showing up correctly.
Here you will see all works correctly with translations:
hidden link|type_cities|type_towns
>>> hidden link
or on this page:
hidden link
On our production which is identical copy we can see that some strings not get pulled:
open first: hidden link
hidden link
>>> hidden link
or here: hidden link
The translations are all saved correctly on Production and are there
hidden link
and is exactly same like on Staging:
hidden link
We cannot delete strings anymore as there are registered with custom PHP pages during initial build. So we need to find solution how to make them work.
The solution to fix this was
1) Move entire wp-content/languages filter from Staging to Production via FTP
And this helped
There are no caches or anything active.
It seems for registered values which are translated or not new translations cannot be added on Production.
So our main question is now - when we add new blog post - are we still able to translate them with WPML or is everything now defunct after we pushed from staging to production?
Usually, it should be enough to go to WPML > Theme & Plugin Localization and on the top of the page you should see a dialog with a white background that tells you:
WPML has detected changed or new MO files
If you open this dialog, you will see the names of Plugins, Themes, and Core, which you need to mark and then scan for language files.
This should then create the custom language mo-files for WPML inside /wp-content/languages/wpml.
This dialog is dynamic and will only show up if WPML is missing files, but it can also be forced at WPML > Support > Troubleshooting > Show Custom MO Files Pre-generation Dialog box.
Please take note, that you are referring on this ticket to String Translation and on the old ticket to pages.
Those are somehow two different things, as String Translation is no directly used in order to translate posts or pages - you will only use it for strings coming from themes or plugins.
Even if the strings for page content like Gutenberg or Elementor are saved on String Translation, you will not be able to use String Translation for translating the content.
The posts, pages, products, and templates or your site all need to use the WPML Translation Editor.
If your website is using the Advanced Translation Editor, you should be able to get the old translation from translation memory by going to WPML > Translation Management.
There filter for example for your pages, then mark some pages and create translation jobs.
Now, when you open the job from WPML > Translation you should see the old translations inside the WPML Advanced Translation Editor and you only might still need to mark the fields as completed.
our website is based on 95% custom PHP pages so that's why we use String Translation only. WPML Translation Editor won't work as it won't recognize these pages.
On Staging String Translation worked perfectly. Now after pushing the whole site to Production the String Translation does not work anymore and we don't know why or how to fix.
Only doing the string translation on staging and exporting mo files and re-importing via FTP solves the issue but is no suitable process going forward.
