@holle75 thanks, I’ll check it out.
…. just guessing:
It seems i found the error-strings in the mo/po files of Ajaxify. I learned the hard way, that wpml do strange things when the same strings are translated twice (or in different name/domains) or under a non-EN-Admin or Non-EN-Main Language.
I wanted to check what happens, when i keep the fields empty in Ajayify->settings->labels. But i´m forced to fill the fields.
If you come up with a solution how to translate the fields (using wpml string translation … and make wpml actually use the translations in FE) … even better.
… another observation: the same error messages (in the meaning), are shown translated and not translated, depending on if you are logged in or not. When you are not logged in it seems messages are the default WP ones (wpml domain: default), when logged in the messages from ajaxify (wpml domain: admin_texts_wpac).
“Posting your comment. Please wait” is always EN
@holle75
With WPML, I don’t have access to the CMS plan, so I can’t test the options out on my own.
I’ve added a config file per their instructions to the plugin to indicate which options are translatable.
Is there any way you can verify that this config file is working?
Thanks,
Ronald
I updated. Whats the “Custom field” or “Term Meta” NAME … to be found in “Custom Fields Translation” or “Custom Term Meta Translation” in wpml -> settings? Or “Post Types Translation”? I couldn´t find any setting there yet.
Edit: I searched for “wpac” in any of those settings and found none. All admin-text strings i added already before and translated them. The problems persist with the newest vesion.
Hi @holle75 I’ve just released 2.0.11, which adds WPML compatibility.
You can check out my guide on how to use WPML to translate Ajaxify Comments for any help.
If this resolves the issue, I would greatly appreciate it if you left a star rating to let others know your thoughts on the plugin.
Thank you,
Ronald
P.S., marking as resolved. If you have any further issues, please open a new support request.
works. In your manual you have a slightly more complicated approach to translate than necessary … but people will figure it out.
thank you!
I am all ears for a better way 🙂
the moment the strings are registered by wpml you should be able to go straight to “string translations” and translate them. I don´t know if registering works right from the start cause i was following your manual … meaning, i don´t know if you have to go through all the steps in your manual to get them registered…. or just saving the settings is enough.
Gotcha. I had to register the labels as a package in order for them to be translatable. Otherwise it didn’t work.
yeahrrrrrg, thats wpml. always different, never logical, always many clicks for nothing. I´m 100% sure the next user just have to do nothing and all strings are registered (depending on his Admin-language, main-site-language, the weather ….) and the 2nd next user will bother you for days cause nothing is working at all 😉
… just out of curiosity, and if you find the time (and are interested). Setup a virgin site, set admin and page language EN, scan in wpml->theme and plugins localization ajaxify and wordpress …. check if the strings are added to string translations.
