The issue we are facing is when we update non-translatable content within a blueprint component (image or URL update for example), and we don't necessarily want to overwrite our live copy page which has already been translated to French. For example, the home page on our en_ca site. Let's say it is ...

I'm not a developer, but I can tell you what we did. We used a template that we had created for raw content. We created a page under our en_us locale and named it robots. In the page properties, we put robots.txt in the vanity URL. Since this was a custom template, we also had a tab for raw content,...

We have noticed that when we make changes such as an image change or a URL update to a blueprint page (English) and activate, that it is over writing content to the child page (back to English) that had previously been sent to translations and returned in French. Is this typical? I understand that A...

Hi,I didn't see a solution? Did I miss something?Thanks!

Just to be clear...they should be updated in the component fields themselves, as well as looking at the URL within the browser in the author preview?Thanks!

It seems as though some of our URLs on our live copied pages are not always updating to the correct locale in author (within our components). I've heard that perhaps they only update in publish but I've seen some update in author (maybe it's based off the content/component type?). I'm still testing ...

Do live copied page URLs update (to reflect the correct locale) in author? Or only publish? We are seeing some strange things happening with our live copied locales and aren't sure what to expect. Sometimes is looks like the URL re-writes in author (for some types of content/components) but sometime...