WPLM Translation Don´t Update on The Frontend
This topic contains 34 replies, has 4 voices, and was last updated by mambo 8 years, 9 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support TicketTagged: translation, WPLM
-
AuthorPosts
-
July 21, 2015 at 9:03 pm #46420
Hello.
During the process of translating the strings/widgets I´ve been facing two issues and I don´t know where else to look for.
a) One is that I just can´t find few words I translated or I simple can´t find them anywhere.
b) The other problem is that some words were translated but they don´t reflect on the frontend. I see the original and translated word, saved and all, but still unchanged on the frontend.I tried to find those words using WPML > “String Translations” and searched the .mo file with POEDIT, but I couldn´t find a way out.
1 – There are cases where the words appear on the list (backend) and even after I translate and save it doesn´t change/update on the website. When I check I see the translated word in other language (backend) but doesn´t reflected on the website.
a) Add Listing > “City”/”Neighbourhood”/”Please accept terms and conditions”
b) “Add Event” > “Coupon Code”2 – The other situation is where I can´t find (on the .mo file) the string/widget for some words to translate:
a) Events
b) All Places in ‘Eat’ > Todos Locaisem ‘Comer’
c) “Add Event” > “Enter Coupon Code”/”Event Schedule”/”Event start date”/”Event end date”/”Event end date”/”All day”/”Event Time”/”Link Business “/”How to Register”/”Registration Fees”/”Region”/”City”/”Neighbourhood”/Am I looking in the wrong places?
Regards!
July 21, 2015 at 9:47 pm #46430I’ll get Paolo or Stiofan to look at your topic.
July 22, 2015 at 1:02 pm #46492Ok. Thanks
July 22, 2015 at 3:21 pm #46512Hi,
all strings you mentioned should be translated via po/mo files and please remember that each add-on has its own translation file.
1) Please accept terms and conditions is in GeoDirectory po file.
2) ”Region”/”City”/”Neighbourhood”/ are in MultiLocation po file for all pages.
3) Everything related to Coupon codes is Prices and Payments po file for all pages
4) Events,Event Schedule”/”Event start date”/”Event end date”/”Event end date”/”All day”/”Event Time”/”Link Business “/”How to Register”/”Registration Fees are in events po file for all pages li ke everything ralated to events
5) All places in ‘Eat’ is composed of several elements the word ALL and IN that can be found in GeoDirectory po file and the CPT nd category name which are translated within WP.Thanks
July 22, 2015 at 6:02 pm #46547Hello Paolo.
I was working on the .po file located on /public_html/wp-content/languages/plugins directory.
When I do search/find words, on that file, I find:1) terms and conditions/region/city… and are translated but don´t reflect on the website?
But I can´t find
2) Neighbourhood/
This happens because each plugin has its own .po file and I have to translate each .po file of each plugin? Or I need to drop the same .po file in every folder of GD plugin?
But what about general indications, like indicated on 1) wich I can find, are translated but don´t reflect on the frontend?
July 22, 2015 at 6:24 pm #46555Hi,
the po file is only needed to create the translation file via poedit or similar software.
What makes the translation on your website is the mo file that is created when saving your po file.
You need to upload the mo file, not the po file. And yes you need to upload the mo file for each add-on too: https://wpgeodirectory.com/docs/translate-core/ + https://wpgeodirectory.com/docs/translating-addons/
Hope this helps.
Thanks
July 25, 2015 at 9:05 am #46898Hello Paolo.
I was looking at .po files and I´ve been working on them. As you can see by the pict attached, some problems persists. Even after I identify the words/sentences, translate, save and upload the .mo files, the changes don´t update. Please see the attached picture 1.
1 – geodirectory-pt_PT
– Tags are short keywords, with no space within.(eg: tag1, tag2, tag3) Up to 4 characters only for this package.
– Please enter listing address. eg. : 230 Vine Street
– Please accept terms and conditions2 – geodirlocation-pt_PT
– Select Neighbourhood3 – geodir_payments-pt_PT
– Free: number of publish days are unlimited (0.004 – geodirevents-pt_PT
– EventPicture 2.
I understand what you said about the combination of different sources to have the word “All Places”, but I can´t find anywhere any of them. In fact I just wanted to separate “…Locaisem ” to “…Locais em”.Thanks.
July 25, 2015 at 6:18 pm #46963Hi again,
are there some translatons working and some not, or none are working?
Are you saving the mo files of the add-ons in the correct folder location?Example: /wp-content/languages/geodiradvancesearch/geodiradvancesearch-pt_PT.mo
https://wpgeodirectory.com/docs/translating-addons/
If this still doesn’t help, please provide a URL, wp admin and FTP credentials and we will have a look.
Let us know,
Thanks
July 27, 2015 at 9:51 am #47040This reply has been marked as private.July 28, 2015 at 8:26 pm #47328Hi,
I don’t see any of geodir mo files in /public_html/wp-content/languages
Please follow documentation: http://docs.wpgeodirectory.com/translate-core/ & https://wpgeodirectory.com/docs/translating-addons/
Thanks
July 30, 2015 at 7:20 am #47489Hello.
Please, try again now.
In fact, I had not created the folder /public_html/wp-content/languages, but even now I´ve done it, the issues remain unchanged.
Please, check!
July 30, 2015 at 7:50 pm #47562Hi,
you placed the addons folder inside the geodirectory folder, that’s why.
https://wpgeodirectory.com/docs/translating-addons/
Core:
/wp-content/languages/geodirectory/geodirectory-en_US.mo
Add-on:
/wp-content/languages/geodirlocation/geodirlocation-en_US.mo
Instead you have it like this:
/wp-content/languages/geodirectory/geodirlocation/geodirlocation-en_US.mo
In addition in some of the folders you don’t have the mo/po files.
Thanks
July 31, 2015 at 7:49 am #47626Ok. I see.
On one side, doesn´t make sense, because if it wasn´t placed on the right folder, some translations shouldn´t work either, but anyway, I did as you said, but the result still the same. The same parts which were´nt updated on the frontend still unchanged!
There are translations which still unchanged when you change to EN and the same when you change to PT.
P.S. – some folders don´t have the .mo/.po files because I didn´t translate them, but I´m in the process.
July 31, 2015 at 9:34 pm #47712The address string wasn’t getting translated because in the Address field, there was a small difference in the front end description field.
In po files is : Please enter listing address. eg. : 230 Vine Street
In the front end description (and database) it was: Please enter listing address. eg. : 230 Vine Street
I corrected that and now that string is solved. For the other I need Stiofan help because I have no idea what’s wrong.
Thanks for your patience,
August 1, 2015 at 11:37 am #47745Can you please provide a fresh list of strings you are still having problems with and i will help.
Please note some things like the tags string might be in the payments manager as you can limit the tags number so the description si changed from the payments manager so if you have that installed you will have to translate that too.
Thanks,
Stiofan
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket