Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom taxonomy related to ACT doesn't display translated with WPML #4556

Closed
manuel-84 opened this issue Nov 7, 2017 · 3 comments
Closed
Labels
Closed: Out of scope Focus: i18n Focus: Other Compatibility Compatibility with third-party plugins, themes, and libraries Status: Need Dev Feedback Waiting on feedback from developer of PR
Milestone

Comments

@manuel-84
Copy link

manuel-84 commented Nov 7, 2017

Hello, I have setup and advanced content type with table storage and one of its fields is a relationship to a custom taxonomy (table storage again). I have WPML and I have translated this custom taxonomy but when I show data from the related field it always display using the main language.
If in WPML i turn on the option "Rectified IDs for multilingual functionality" the field doesn't get displayed at all.

@jimtrue
Copy link
Contributor

jimtrue commented Nov 29, 2017

Advanced Content Types would not be able to integrate with WPML's or Polylang's default configuration (without a custom add-on) because they exist outside of WordPress's default Custom Post Type/Taxonomy infrastructure. @JoryHogeveen can weigh in on this one, but I honestly don't think this is something we could get integrated without someone taking this on as a special project, since external tables by default are not translated by WPML or any of the translation engines.

If you switch to Custom Post Types and Custom Taxonomy, you should be properly supported by WPML and Polylang.

@jimtrue jimtrue added Focus: Other Compatibility Compatibility with third-party plugins, themes, and libraries Focus: i18n Status: Need Dev Feedback Waiting on feedback from developer of PR labels Nov 29, 2017
@JoryHogeveen
Copy link
Member

This would definitely be a separate compatibility tool since WPML and Polylang depend on the use of WP core objects (WP_Post, WP_Term etc).
It might be possible to make the PodsObject compatible once it's here in 2.8 but I don't think this would be in the scope of Pods core.

@quasel
Copy link
Member

quasel commented Sep 1, 2018

Hi, we didn't hear back from you - so I'm closing the issue! And that's clearly a very special use case due to nature of ACT and how WP works ^^

@quasel quasel closed this as completed Sep 1, 2018
@sc0ttkclark sc0ttkclark added this to the Pods 2.7.13 milestone Jun 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Out of scope Focus: i18n Focus: Other Compatibility Compatibility with third-party plugins, themes, and libraries Status: Need Dev Feedback Waiting on feedback from developer of PR
Projects
None yet
Development

No branches or pull requests

5 participants