No longer working with WPML

hey, sorry to hear you’re having problems with this. To be honest, there’s nothing I can think of that changed that would have accounted for this loosing compatibility with WPML. It’s coded to the same standards with which we do all our plugins, so it certainly should be compatible.

What specifically were you translating that stopped working a few months ago? The tab content? You would write it in one language and have it be available/translated into multiple? And now this is not happening?

Who did you get in touch with over at WPML? Maybe I can reach out to them and see what needs to be done with our plugin to get everything working again.

— Justin

Hmm, okay so an update: I have a WPML tech working on a test version of the webshop I run, and he just updated it to a new beta version of WPML I believe. With that new version, the Custom Tab seems to be working/translating properly again?

However, the version that’s on my live site still is not working.

The tab still works fine on the English side, and I’m using it happily there, but it used to be when I translated product pages, the English content would be copied over into the custom tab field, and then I’d just replace that English content (title and actual tab content) with the second language translation, hit update, and the new second-language page would have all of its custom tab content translated as well, like you’d expect.

Now, though, that content in the second-language page isn’t being saved. Any attempts to replace the content on the second-language page (with ANYTHING, not just ‘non-English language’ — I can type Lorem Ipsum in the translated custom tab area and it still reverts back to the original English).

It SEEMS like the translated page is “locked” (even though I can still change the content, it is not saved). Because if I change the English side, the changes are reflected in the second-language side, so in other words, the translated content I place in the Custom Tab is being replaced by the original English values.

However, as I said at the beginning, it LOOKS like this has been fixed by the newest update to WPML, even though they claim they don’t have any time to look into it? I’ll see what happens when I update the live site. Perhaps this has been resolved?

Ok cool, thanks for the update. Yeah, sounds like this is something that’s going on on the WPML side, if the translated content isn’t saving correctly. Happy to hear this seems to be working in their upcoming version ??

— Justin