If we have a page like /content/site/en/foo and we create a language copy like /content/site/pt/foo. We translate that language copy and everything is great. Sometimes though when we look to add a sub page, say /content/site/en/foo/bar, instead of adding creating it at /content/site/pt/foo/bar like we expect, the translation job will create it at /content/site/en/foo/pt/bar like it doesn't understand where to put the new page. We don't see anything abnormal about the node structure of the pages and the only solution we've found is to delete /content/site/pt/foo and recreate it from the top on down. Anyone experience anything like that?
When creating a language copy, do you select "create structure" only or you initiate a translation job directly?
Also I see, on creating a translation job of page containing sub-pages, it asks to include child pages as well at the time of submitting the job. So, the child page /content/we-retail/us/ja/experience/arctic-surfing-in-lofoten will be created under the master language copy "/content/we-retail/us/ja/experience" if you create the language copy as a structure here.