Not really social but feel the need to vent about a stupid bug that's got me working on a live site at 2300hrs and you guys / gals / everyone inbetween are the only ones that will understand. The site has a custom translation dictionary - stored under a special root node. Each section of the site has it's own node, named after the section. There's a special helper service _translationService.Get("SomeSection", "This string that needs a translation"). If the service doesn't find the section and or the string it creates it. Saves and publishes - refreshes a cache and then all is well. The editor can then add the translation later. It's usually a very lovely solution. 1000 points if you can already see what's coming here.... The site has fallen over because an editor translated the content node which is the section section name. They then Push-published via uSync from the staging site - this updated the content node's name. However the live site then couldn't find it's "SomeSection" node so it created a new one. No problem - they just won't have the tranlsated text - just the english defaults - right? Except the content service in Umbraco *could * see "SomeSection" (somehow) so instead diligently created "SomeSection (1)". then... "SomeSection (2)". Then... "SomeSection (3)". Yup - I'm running a script to delete 300,000 ghost nodes that have just meant I can't get in to fix the actual node I need. Thanks for attending my TURD Talk. I'm off to retrain as an electrian.