• Resolved el56

    (@el56)


    A version of this was posted on Github, not sure which is the best venue.

    I am trying to use a Pods site with multilingual content, using the mqTranslate module.

    mqTranslate works everywhere on the site except for the post types and taxonomies created within Pods. Even in other plugins (and menus, widgets, etc) that aren’t translation-aware, I am able to enable multilingual text through this syntax (for instance):

    <!--:en-->Research Team<!--:--><!--:es-->Equipo de investigación<!--:--><!--:ar-->فريق البحث<!--:--><!--:so-->Kooxda Cilmi baarista<!--:-->

    The above will, depending on language selected, appropriately provide the English, Spanish, Arabic or Somali version of the term”Research team”.

    That is, the above syntax works everywhere on the site except anything to do with Pods. The multilingual interface offered for regular posts is gone in all post types and taxonomies I’ve defined in Pods, the above line just displays as

    Research TeamEquipo de investigaciónفريق البحثKooxda Cilmi baarista

    in all languages. Clearly something is stripping out the <!…> phrases.

    My best possible outcome would be more-complete support for multi-lingual sites. But for now, at least the ability to use the above syntax will be sufficient.

    Any suggestions?

    https://wordpress.org/plugins/pods/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Josh Pollock

    (@shelob9)

    We discussed this issue in Slack and did not find a good result because of how Pods is sanitizing the field values. Since we do not support qTranslate or mqTranslate, I don’t have a good answer for this.

    Thread Starter el56

    (@el56)

    This is now marked as “resolved”….

    So is the resolution “you can’t get there from here”?

    Can you offer an at-my-own-risk way to turn off the sanitizing?

    Is there a multilingual solution that you do support?

    Or is Pods, by design, unusable by anyone wanting more than one language?

    Just checking. I’m not used to support questions being closed with “tough luck”, and I’d already invested a lot of time down this path. Sorry if I seem hostile, it’s not intended, but in decades working in IT I’ve never before heard of a significant incompatibility like this just being given up on.

    PS: ongoing, please indicate early in the documentation that Pods can’t be made to work on multilingual systems. That will save some future implentor from following the same dead end that I did, so at least some good can come from my experience.

    Plugin Contributor Josh Pollock

    (@shelob9)

    I’m sorry if marking this as resolved was wrong. I thought we had resolved this in Slack.

    We support WPML for translations.

    I wish we could support every multi-language plugin, but it’s just not possible given our limited resources. There is an open issue for qTranslate support, but right now we just don’t have the bandwidth for that. As you’ve found there are significant hurdles to making it work. Hopefully it’s something we can get to in Pods 3.1.

    Thread Starter el56

    (@el56)

    That’s fair enough. Thanks for the quick response.

    Thread Starter el56

    (@el56)

    FWIW, some of the translation modules are merging. The latest rev of mqtranslate just said it was shutting down and merging with qtranslate-x.

    Maybe this will make it easier for pods to support in the future….?

    WPML was not an option for us as it has no free options.

    As for bandwidth to support … maybe just an option to allow turning off of the sanitizing might be enough for now.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Multilingual Pods / Turn off Sanitizing?’ is closed to new replies.