- This topic has 3 replies, 2 voices, and was last updated 2 years ago by Andre Flores.
- May 25, 2020 at 4:11 am #958170TilmanParticipant
I researched across the board but could not find anything suitable yet. In addition, I followed exactly those Loco related steps as outlined in the forum.
Is there any opportunity to reset ALL translations via Loco we’ve made in the past as one-off? Hence, back to original/fresh state prior to any changes made? The restore feature does allow set number of changes only which is not sufficient (anymore) in our case.
For whatever reason, in certain occasions the first change of strings worked well but any additional one for the same string (which has been already changed once) does not get reflected in frontend anymore even cannot be reset to initial string by removing the first change (for those beyond the restore set), esp. related to:
a) certain display edits in search result page and
b) certain display edits under “view details” page called via search result page
Theme: Luviana incl. HB Plugin: 3.7.1
Thank you very much for your cooperation
TilmanMay 25, 2020 at 7:25 am #958221Andre FloresModerator
In your case the option would be removing translation file you have used to translate the plugin/theme. Navigate to Loco Translate ->Plugins/Themes and look for “Delete” tab – you may back-up translation files in specified paths before deleting them, just in case: https://prnt.sc/sn7zsj.
As for the changes not being applied to the language files, it may be the issue with permissions on your server, which do not allow overwriting files after changes are performed in the plugin. The issue also may be caused by some third-party plugins, I would recommend that you deactivate them in order to check whether one of them causes the issue.
If there is still no luck, do not hesitate to submit a request to our Help Desk for further investigation.
AndreMay 25, 2020 at 9:43 am #958298TilmanParticipant
many thanks for rapid reply and tweaks provided.
Finally, seems to be another third party plugin has caused the issue. Now, Loco based translation works as intended (again) post deactivation.May 26, 2020 at 8:12 am #958710Andre FloresModerator
You are always welcome. I am glad you were able to get to the bottom of the issue and have it resolved!
- You must be logged in to reply to this topic.