WPML compatibility
This topic contains 11 replies, has 4 voices, and was last updated by Paolo 8 years, 2 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket-
AuthorPosts
-
December 22, 2016 at 6:47 pm #329343
Hello,
I have had problems with the translation of certain strings using WPML. Their support team is currently helping me out and they suggested I contact you with the following suggestion as some of the trouble I’m having could be on your end :
“I can see that there has been some attempts to contact the Geodirectoy plugin author in the past but he/she has not yet joined our GoGlobal program.
https://wpml.org/documentation/theme-compatibility/go-global-program/In this program, they will receive dedicated support from our compatibility team to introduce our API integration in order to make all strings translatable. For the moment, for your cpt add-item form, there is no existing open issue that I can find and we seem to have lost contact with the author. I will raise an internal ticket to request that we send another invitation to join GoGlobal and it would help if you also contacted their support to request to contact us.”
Cheers and Merry Christmas!
December 22, 2016 at 7:03 pm #329358Hi Thierry,
we constantly work on our side to keep up with WPML compatibility and if you provide a list of the problem you are facing, we will provide a solution.
Thanks
December 29, 2016 at 3:39 pm #332927The translation of certain strings do not appear eventhough they are found by WPML and marked as translated in WPML>string translation once I have made the translation.
Below is the link where you will find the strings not translateable.
The website is password protected, the password is “demo”.
http://bivouak.ca/fr/add-listing/?listing_type=gd_place
And I have attached screenshots of the text I cannot translate.The credentials to investigate will follow in a private message.
I have contacted WPML support and here is there anwer :
3. Custom Field Text Labels
The other section titles turn out to be texts that are held in a separate database table which may require some custom coding to add calls to register and read the strings with the WPML architecture.This will require custom coding and intervention from the compatibility team. I will need to escalate the most recent copy of the Geodirectory plugin for them to investigate.
Can you please send me a zip file of this? I am opening the private area for your to include a link where I can download this. Please use a service like Dropbox or Fileshare as you will not be able to upload all the files on this forum.
4. GoGlobal
I can see that there has been some attempts to contact the Geodirectoy plugin author in the past but he/she has not yet joined our GoGlobal program.
https://wpml.org/documentation/theme-compatibility/go-global-program/In this program, they will receive dedicated support from our compatibility team to introduce our API integration in order to make all strings translatable. For the moment, for your cpt add-item form, there is no existing open issue that I can find and we seem to have lost contact with the author. I will raise an internal ticket to request that we send another invitation to join GoGlobal and it would help if you also contacted their support to request to contact us.
December 29, 2016 at 3:43 pm #332933This reply has been marked as private.December 29, 2016 at 3:50 pm #332935Hi,
did you see this doc: https://wpgeodirectory.com/docs/translating-custom-fields/?
Let us know,
Thanks
December 29, 2016 at 4:09 pm #332941Yes, I have gone though the steps 1 through 5 presented in the document. The custom field values are found by WPML, I translate them in the translation table but the translation does not appear as you see on the screenshots.
December 29, 2016 at 7:38 pm #333123I asked to the developers to follow up, they will let you know asap.
Thanks
December 29, 2016 at 11:30 pm #333260Thierry, please check the WP admin username, the one you posted is not working.
For Kiran: Both of these strings are fieldsets, and my testing confirms that fieldsets are not being translated.
They are downloaded as part of the custom fields, and can be translated in the PO files, but it does not show on the frontend as expected.December 30, 2016 at 9:47 am #333361Hello Thierry,
Please check now.
Kiran
December 30, 2016 at 6:02 pm #333775Things are looking good.
Thank you for the quick fix, much appreciated.Happy new year!
December 30, 2016 at 6:04 pm #333776Let me know if you still need WP admin access, things are looking good right now.
December 30, 2016 at 6:05 pm #333777We do not for the moment thank you and happy new year to you too!
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket