- This topic has 1 reply, 2 voices, and was last updated 1 year, 12 months ago by .
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- You must be logged in to reply to this topic.
WordPress Membership Plugin
Simple Membership Plugin › Forums › Simple Membership Plugin › [Support request] Problem with loading new translations (Polish) after editing .
Tagged: .po/.mo Files, Translation Issue
Hi,
I am having an issue with loading new translations in the Simple Membership Plugin after editing the .po and .mo files. I translated the plugin to Polish, but after uploading the translation files, the plugin still displays the old translations.
Steps I have taken:
1. I edited the .po file using Poedit and generated the .mo file. The translation to Polish is 100% complete.
2. I placed both files in the following plugin and language locations:
/wp-content/languages/plugins/simple-membership-plugin-pl_PL.po
/wp-content/languages/plugins/simple-membership-plugin-pl_PL.mo
/wp-content/plugins/simple-membership/languages/simple-membership-pl_PL.mo
/wp-content/plugins/simple-membership/languages/simple-membership-pl_PL.po
3. I cleared the cache using WP Rocket.
4. The new translations are still not showing.
5. What’s even more strange, approximately 20 minutes after midnight overnight, the files:
/wp-content/languages/plugins/simple-membership-plugin-pl_PL.po
/wp-content/languages/plugins/simple-membership-plugin-pl_PL.mo
are overwritten by the plugin’s original files.
What should I do to ensure the translations I created work?
I am using WordPress version 6.6.2 with the Astra theme and Simple Membership Plugin version 4.5.4.
Thank you in advance for any suggestions and help!
Best regards,
Sebastian
5. What’s even more strange, approximately 20 minutes after midnight overnight, the files:
/wp-content/languages/plugins/simple-membership-plugin-pl_PL.po
/wp-content/languages/plugins/simple-membership-plugin-pl_PL.mo
are overwritten by the plugin’s original files.
That is not being done by the plugin. You should resolve this with your hosting provider first; as it may impact the final solution.