Allow translation of CPTs without "editor" support #184

kraftner opened this Issue Dec 11, 2015 · 0 comments


2 participants

kraftner commented Dec 11, 2015

I just noticed that you cannot translate CPTs that do not support the 'editor'.

I guess the reasoning was that by default the content is the only thing one can translate. But the ability to link CPTs with MLP so that e.g. meta data can be synced using the MLP APIs would be pretty useful, even though the CPT doesn't have a content field.

Was this just over-strict checking or is there any issue at another point in MLP that requires this?

@tfrommen tfrommen changed the title from Allow translation of CPTs without "editor" capability to Allow translation of CPTs without "editor" support Dec 11, 2015

@tfrommen tfrommen added this to the v2.4.0 milestone Mar 14, 2016

@tfrommen tfrommen self-assigned this Mar 14, 2016

@tfrommen tfrommen closed this in 794c7a6 Mar 14, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment