Strings I can't translate (4)
This topic contains 11 replies, has 2 voices, and was last updated by Guust 6 years, 9 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support TicketTagged: translation
-
AuthorPosts
-
February 22, 2018 at 1:15 am #418689
Hi,
I’m having trouble translating some strings. I’ve set the language files of every plugin installed (plus supreme directory) but had no luck with the following strings ๐
(image attached):– Select: in Change location tab
in My account page:
– Events
– Listings
– My InvoicesThank you for any clue about this slippery strings!
February 22, 2018 at 11:41 am #418745โ Select: in Change location tab
Is in the Location Manager language filein My account page:
โ Events
This depends what plugin you use to create the accounts page, maybe the Buddypress integration or the UsersWP integrationโ Listings
This depends what plugin you use to create the accounts page, maybe the Buddypress integration or the UsersWP integrationโ My Invoices
This is the “My Invoices %s” string in the Invoices pluginThanks
February 22, 2018 at 3:34 pm #418770Hello Guust, thank you for replying ๐
I did find them, but the translation doesn’t work.
For Invoices plugin I have these files in wp-content/languages/plugins:
invoicing.pot
invoicing-es_ES.po
invoicing-es_ES.poFor this plugin, translations don’t work at all
—————————————————-
– I Found “Events” and “Listings” in Buddypress Integration, but they just won’t translate.
– Same with “Select” in geodirlocation-es_ES.poFor these addons these are the only (so far) strings that won’t translate.
– also “Photos” in geodirectory-es_ES.po
So it’s just some strings…I’m clueless about this
Anybody having similar issues?
February 22, 2018 at 10:06 pm #418836The files that make the translations happen are the .MO files.
The .PO files are only to translate and that will create the .MO files.
So .PO or .POT files are not enough, you need the .MO files.Post your URL, WP admin and FTP details and we’ll check it out.
February 23, 2018 at 1:16 am #418870This reply has been marked as private.February 23, 2018 at 7:43 am #418889Please check now, you were using all old versions of the language files:
https://wpgeodirectory.com/docs/updating-your-language-files/Thanks
February 23, 2018 at 4:48 pm #418943Hello Guust,
thank you so much for updating the files. I now know where to look in the future.I have to comment that I downloaded the translation files from https://wpgeodirectory.com/translate/projects/ just recently.
Best regards!
February 23, 2018 at 11:21 pm #418971You’re welcome ๐
February 23, 2018 at 11:39 pm #418974Hi Guust,
sorry for bothering again.I now have more strings untranslated, although I did translate them in the .po files in wp-content/languages/plugins/…for example:
wp-content/languages/plugins/geodirectory-es_ES.po
wp-content/languages/plugins/geodirevents-es_ES.pothis is so frustating…Were these the files you updated?
please help!
February 23, 2018 at 11:54 pm #418979I did not touch or update the Events files.
I can see you changed some more strings in the geodirectory-es_ES.po file, but you have not re-uploaded the geodirectory-es_ES.mo file, that is still the old one.
Without re-uploading the MO files, the translations will not work.When plugins need updating, sometimes strings need to be changed, so strings that worked before an update may be replaced and therefore stop working. That is very rare, but sometimes it is the only way to fix translation strings for all languages.
So when a translation does not work, check your language file is up to date, and then check what extra needs translating.
Let me know how you go. Thanks
February 24, 2018 at 12:01 am #418985Oh so each time I edit the PO files I need to delete the old MO, now I get it. It’s working.
Thanks for the patience!
February 24, 2018 at 12:08 am #418991Yes, it is the MO file that makes the magic happen ๐
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket