I'm know that in order for XPM to show the Translate option the context repository of the page/component you're editing needs to have some translation configuration defined.

But in a multiple content masters scenario (as shown in the docs) - if you have the BluePrint context of XPM for your EN website set so components are created in your global English (EN) Content publication - then you can't translate from within XPM as this publication has no translation configuration - you have to localise at the translation layer English Translation publication - is that right?

enter image description here


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.