Multilanguage problems with WPML
This topic contains 20 replies, has 5 voices, and was last updated by Guust 9 years, 11 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support TicketTagged: Multilanguage, translation
-
AuthorPosts
-
September 11, 2014 at 3:49 pm #15076
Hello,
I have installed GD plugin and configured everything to work in 4 languages via WPML. Main system seems to be working, but there are few problems, which needs to be solved before i coud buy needed addons for this nice plugin.
Fewest problems seems to be with WPML 3.16, with WPML 3.1.7.2 there are even more problems. I ave tried everything – from older to newer WPML, various WP versions and i discovered that best results are with WP 3.9.2 and WPML 3.16
I do not plan to upgrade my website any time soon, so older versions of software will be kept to have stable website (there are more plugins i would use, same situation with these)
Problems are:
Item count in popular categories (only in non-default languages)
Add listing page working only with default language. Though it is translated to all languages – it’s content is empty when opened in non-default language. If menu “add listing” is pressed – it switches to default language add listing page and there are no WPML language bar available.
Could i receive some help with my problems?
Thank you.September 11, 2014 at 6:50 pm #15105would you mind sharing a link and possibly wp admin credentials to have a look?
Add listing page working only with default language. Though it is translated to all languagesDid you actually translate the add listing virtual page?
Let us know,
September 15, 2014 at 5:19 pm #15465That is exactly a problem – i did fount these pages at wp “pages”, and all of these are empty, some virtual content is somewhere else. I did translate (saved other language versions, but these are empty, if switched manualy with address. Only working default language (language which was set by default, when GD was installed) add listing page is working.
I did not translate actual add listing page, because i do not know how to do it. It would be good, if you could give some directions to me, how to do it. As i tested this on many various wp/wpml versions and these problems remain strong on all of these, i think there are more people with this kind of problems, so fixing of these would be helpful to them, also could increase usability and trust of your nice product.
http://kiemopauksciai.lt/test/ here is test site, which i will use. It haves enfold skin and enfold compability pack (your plugin). Also it need to have a web shop, but if it is a big problem (non-compability with woocommerce and woocommerce membership modules), i still do not know if this will work.September 15, 2014 at 10:02 pm #15493This reply has been marked as private.September 15, 2014 at 10:26 pm #15494Hi,
I just finish testing in one of my test sites with latest version of everything and I can recreate the problem.
Itr was working last time I checked… I’ve reported this to developer to fix asap.
Thx
September 17, 2014 at 2:05 pm #15703I have the same problem… I can’t translate your plugin, I try to translate it with some pluginsn (Loco translate, Codestyling Localization) and the same result…
September 17, 2014 at 3:00 pm #15708HI Jordi,
I don’t think you have the same problem, because normal translation works as expected.
Here we are talking about multilanguage and only for the add listing form.
That warning will not prevent the pluing from being transalted and still work as expected.
Otherwise you can follow default translating procedure: http://docs.wpgeodirectory.com/category/translation/
Thx
September 17, 2014 at 6:40 pm #15746So, is there any solution available?
September 17, 2014 at 6:42 pm #15747That warning will not prevent the pluing from being transalted and will still work as expected.
Otherwise you can follow default translating procedure: http://docs.wpgeodirectory.com/category/translation/
Thx
If there is no problem, there shouldn’t be any need for a solution.
Thx
September 17, 2014 at 7:06 pm #15749But i still cannot translate (do not how) add listing page, this is really frustrating and it halted my project, as i do not know if i will be able to use this plugin and buy it’s addons.
I could not find any info in http://docs.wpgeodirectory.com/category/translation/ about translation of any virtual pages, as add listing page seems to be…September 17, 2014 at 7:48 pm #15752Hi,
If your website is in a single language, all text strings of the add listing page are translated via po file as explained in docs.
There is no “special way” to translate the add listing page. The problem reported on this post arise only in a WPML powered multilanguage websites, where there has to be a different add listing page for each language. We are working to fix this.
Thanks
December 4, 2014 at 9:06 am #23462Hi
Can you confirm if this issue has been resolved and rolled out as in our latest installation it still does not work
Regretfully this issue somewhat negates the usefulness of the plugin
Look forward to your update
December 4, 2014 at 10:56 am #23470Hi
In light of the fact that the language issues do not work on a multi install we have done a dedicated installation and started work using the poedit tool https://poedit.net/download
This has identified a further 2 issues:
1 – the backend of the site is now being translated as well – this does not follow the norm as other plugins ONLY translate the frontend
2 – we are unable to find all the labels to translate – are they somewhere different?Again look forward to hearing from you
December 4, 2014 at 12:41 pm #23494@ Rudiger
Where is that norm? Buddypress and bbPress for example only have one language file too, to translate both front and back end.
Not all strings are in language files. For example City, Region etc should be changed in the relevant custom field: GD > Place settings > custom fields
December 5, 2014 at 7:52 am #23580Hi thanks for this we will get on with those translations
Q1 – Can you update me on whether the multilanguage issue is resolved?
Q2 – Based on your response is it fair to say that we cannot have a full english backend with a chinese frontend (referring to the norm comment earlier) or is there a workaround
Bear with us please as we are attempting to get the site live asap and this is the last issue to resolve
Look forward to hearing from you
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket