Plugin Author
Gunu
(@grafcom)
@emiliengerbois
This seems very complicated in order to achieve.
Why do you want to work both plugins together?
qTranslate X and WPML treat translations completely different.
Hi Gunu and thanks for your quick reply,
my problem is I have to work with some plugins and a theme which compatibility with Qtranslate-X isn’t ready, whereas they work great with WPML…
Problem is WPML duplicates posts and creates many IDs and for some CPTs I have no choice but keeping one ID for each post. Qtranslate-X works this way, that’s why I try to work with it also.
In my install, WPML manages Posts, Pages, Menus, taxonomies, … and I only need Qtranslate-X in order to translate my CPTs content.
I don’t need a language switcher for those posts because I just add links for translations into their content directly. I don’t even need a header or a menu actually… and I use Qtranslate-X in raw mode for those CPTs.
Problem is when I go to a default post or page (translated with WPML), switching the language through the WPML language switcher, I get redirections thats aren’t active if I disable Qtranslate-X. So it breaks my menu and WPML translations.
Is there any way to load Qtranslate-X’s scripts only for certain CPT’s? Or is there any way to restrict URL’s rewriting only to those CPTs?
thanks again (a lot) for your help,
Emilien
Plugin Author
Gunu
(@grafcom)
@emiliengerbois
you can contact John Clause about this use this form
So he can be contacted directly with you.
It might be easier to integrate your theme with qtx: https://qtranslatexteam.wordpress.com/integration/ and get rid of WPML? Otherwise it seems overly complex.
It is not a popular demand, which sets the priority pretty low for us to work on it. However, you are always welcome to submit a pull request at GitHub with the code for a custom option, which would solve your problem.
