Home › Forums › Legacy Support › Support queries › Translation issues › translation problem with codestyling localization plugin
- This topic has 23 replies, 3 voices, and was last updated 8 years, 2 months ago by ewanb.
-
AuthorPosts
-
August 23, 2016 at 1:09 pm #66388ewanbParticipantThe problem I have is that translation files are not recognized by Loco translate if I put them in global languages folder, even after synchronizing.August 24, 2016 at 1:39 pm #66611H.K. LatiyanParticipantI am not sure why this issue is occurring on your website, so can you please share the site url, admin credentials and ftp credentials with us to check the issue on your site. PS: Please mark your reply as private while sharing the credentials.August 26, 2016 at 10:31 am #67011ewanbParticipantIt seems now files are saved in global language folder when modifying them so I assume this is ok nowAugust 26, 2016 at 10:38 pm #67136ewanbParticipantI just updated theme, and plugin vibe-course-module Again I lost some translations I made before. I would REALLY appreciate if this problem could be solved once and for all, because I'm losing a LOT of time with these translations issues when updating plugins. I used Loco translate as you recommended, I put .po files in wp-content/languages/plugins folder as you recommended, and I still have some problems. admin credentials have been shared in the following topics where I also have translation issues : https://wplms.io/support/forums/topic/email-options-translation-problem edit : more infos : when I translate a string in Loco Translate, the .po file that is modified is the file in wp-content/plugins/vibe-course-module/languages this has no effect on website. If I manually copy the newly generated file from this folder to folder wp-content/languages/plugins/, now the translated string is correctly appearing on the website. But my problem is that it's causing a huge mess when I update modules. Please share the exact procedure to solve this problem, as what you recommended so far has not worked. Thanks !August 27, 2016 at 1:24 am #67142ewanbParticipantHi, I got back my translations but can't manage to have something working when translation files are in global wp-content/languages folder (theme nor plugins) so for now files are in plugins/xxx/languages/ folders (or theme/wplms/languages) If the only drawback of this is to have to manually backup and then resynchronize .po files with loco translate after plugin update, that will be good for me, but I would appreciate if you could confirm me this theory. Thanks for your helpAugust 27, 2016 at 11:57 am #67235Anshuman SahuKeymasterWell this issue initially related to the Loco translate . It is considering the default paths for the translation files and is not using the path that we have defined . It has option to ask where to sync or generate the translation files but do not have option to sync the translation path later or for existing files . I personally use code styling and its preserver plugin coz it follows the paths that theme has recommended to follow . It preserver plugin gives functionality to sync the translation files and preserve the translation by changing the path to the global languages folder .August 27, 2016 at 12:11 pm #67242ewanbParticipantOk with that. However you advised me to use Loco translate (https://wplms.io/support/forums/topic/translation-problem-with-codestyling-localization-plugin/#post-64039) so I moved to Loco Translate plugin, I don't really feel like changing translation plugin again. Could you confirm that following process is ok to keep translations when updating a module or theme ? 1. manually backup plugin or theme .po file 2. update plugin/theme 3. move backuped file to the updated plugin folder 4. go to loco translate and edit the plugin translation 5. click on "sync" If you garantee that this will keep previous translated strings and add the new strings of updated module then I will be ok with that ThanksAugust 29, 2016 at 1:52 pm #67531H.K. LatiyanParticipantYes this will work, you'll have to sync once after the update.August 29, 2016 at 2:16 pm #67543ewanbParticipantThanks for your reply
-
AuthorPosts
- The topic ‘translation problem with codestyling localization plugin’ is closed to new replies.