- This topic has 62 replies, 3 voices, and was last updated 4 years, 5 months ago by
.
-
Posts
-
Hello, 1- Refer: https://ibb.co/FxZPbYf this is coming from badgeos plugin. please make sure your .po|.mo file is in global(system file). 2- for this: https://ibb.co/Vt6hg9F please find these texts in wplms-frontend, vibe course module, vibe custom types and wplms shortcode plugin.
if we talk about the translation loss. yes on every update local files will be affected so that you need to put these translated files into global folders. it will prevent string loss from the update.
here is how you can achieve this.
Note: in this, I am using my local test setup site language which is "Português do Brasil". you have to select your site language.
Always sync and save the pot file refer: http://prntscr.com/ng3kbk
Note: Always copy local .Po | .Mo files into the global folder. it will prevent from translation string loss while updating theme/ plugins.
How could you do this: https://screencast-o-matic.com/watch/cqfQh6ZllK
In this video,
- i have checked the site language from wp-admin > settings > general > site language.
- then goto wp-admin > loco translate > theme/plugin > theme name / plugin name.
- Copy author file to system file.
- the author stands for local file and system stands for the global file.
- once your done copying. from now you have to translate a string in global (system) file.
These steps should be followed for all plugins and theme in which you are making any changes.
Hello,I would like to request temporary access (wp-admin URL and credentials) in a private reply to your site to take a better look at the issue. The information you will enter is private which means only you and I can see and have access to it.
also, share some stills which strings are not translated yet.
- The topic ‘loco translate issue’ is closed to new replies.