Too late - I've moved on. The client was on AMS and I don't remember setting up any additional run modes, so I'd guess no.

This does work, so thanks for that. But it is a bit of a hack. Because I need the paths and names to match up, I've got to create XFs I don't want, delete them, go to my language master, create an XF live copy with the wrong name, and move it to the place it needs to be while ensuring that I've got ...

This isn't a solution - you can't leave the live copy in place and still have the core XF component find it. See Arun's comments below.

Still no - you can create the variation as live copy, but it won't be where it needs to be for the core XF component will look for it. You need:/content/experience-fragments/xxx/language-masters/fr/footer/master/content/experience-fragments/xxx/ca/fr/footer/master (which is the live copy)/content/ex...

Unfortunately, this doesn't put them in the correct place for the core experience fragment component to localize them. As per the documentation I referenced, the XF MSM structure must mirror the Sites MSM structure.

I've seen experience fragments structured with language masters in a couple of places. One would be the documentation here:https://docs.adobe.com/content/help/en/experience-manager-core-components/using/components/experience-fragment.html#localized-site-structureIn Sites, I can create live copies of...

I am setting up an AEM / Analytics integration and have run into the problem that my staging configuration is being ignored on the staging server - the production configuration is always used. I've gotten around this on the staging server by using putting the incorrect (staging) URL in the productio...