Background of the issue:
We are building archive/landing pages using Kadence Blocks with the Query Loop (Advanced) feature. Kadence allows us to create two CPT-based entities: kadence_query_card, which translates fine in WPML, and kadence_query, which is the Query itself. Our goal is to make the Query Loop load the translated Query per language, similar to how its Card already does. We suspect that WPML might be filtering out CPTs with public => false, preventing kadence_query from appearing in 'Post Types Translation'.
Symptoms:
kadence_query is not listed in WPML's Post Types Translation or other settings, causing the loop to use the default-language Query configuration on secondary languages.
Questions:
Does WPML support translating a CPT that’s public => false but has show_ui => true (Kadence kadence_query)?
What’s the correct way to make kadence_query show up under Post Types Translation so we can set it to 'Translatable – only show translated items'?
Is there a WPML hook/filter to force-register this CPT as translatable, or should Kadence change its CPT registration to be compatible?
Are there any known limitations with Kadence Query Loop + WPML we should be aware of?
The topic ‘[Closed] WPML doesn’t detect Kadence Blocks CPT kadence_query (Query Loop). Cards translate, the loop itsel…’ is closed to new replies.
