So we have a piece of content in English. When I make a translation using ADD TRANSLATION the URL alias for the English (source) node disappears and is replaced with the URL Alias default (it overrides our custom url alias). The new node ends up with no url alias so the page goes to node/xxxx. If I then update one or the other language node's url alias the other one gets changed to the default and we end up with multiple values in the url alias table for each path. Any ideas?

Comments

drubage’s picture

drubage commented

Ok so I did some more debugging. When I add a new translation it ads a new alias for the English node but does not add ANY alias for the new translation (in this case Thai). It looks like it adds the alias I put in for the new translation (in this case thailand-holiday/pattaya) but then a second later it changes that value to the automatically generated URL (pattaya-holiday-adventure-flight-gibbon-zipline-tour-thailand-holiday). Note that this is a DUPLICATE entry for the English version and there are now 2 values for that node/5 SRC in the url_alias table.

If I then go to edit the Thai version and put in my alias (thailand-holiday/pattaya) and hit save it messes everything up. It changes both SRC node/X values (one was node/5 and one was node/185) to the English version node/5 with a language of 'en'. We lose the Thai version and now have 2 entries for node/5 (one is the auto alias from the edit and one is the old correct value of thailand-holiday/pattaya). We would have 3 entries for node/5 had I not hand-deleted the original alias after making the Thai translation.

If I go and edit the Thai version again and add the hand-alias "thailand-holiday/pattaya" and save, we get a new row in the url_alias table for this node (node/185) with the correct alias. However, the English one still has 2 entries (one thailand-holiday/pattaya and one pattaya-holiday-adventure-flight-gibbon-zipline-tour-thailand-holiday).

Any ideas? It is definitely broken we have not done anything unique on this site just translation.

drubage’s picture

drubage commented
Status: Active » Closed (works as designed)

Ok I think the issue was that we had synchronize translations checked on the module page, not sure what that even does.