Thnak you for your feedback.
Please note that when changing the template, and opening the page for editing, if we cannot find the placeholder a widget's associated with, we need a mechanism to place it somewhere so you will be able to properly drag it in a location of your preference.
As the placeholders on a page may come from several locations - the masterpage, the template, and the page itself, the mechanism for combining and rendering them in the page edit screen, and ensuring that all widgets are ordered correctly is quite complex. A part of this mechanism is to place all "orphaned" widgets i.e. the ones that cannot find their placeholder, in the first available placeholder on the page
Since the Sitefinity page edit supports only ContentPlaceHolders inside the<body> <form> tag, if your templates have been created through Sitefinity you're pretty much avoiding any problems of this sort. However if you're using a custom masterpage, whose HTML we cannot control, and have included a ContentPlaceHolder in the <head> tag, for example, this will be the first available placeholder on the page, and the "orphaned" widgets will be placed there. However, as this is at the same time a non supported location for our backed page editor, it would result in the described behavior.
Our advice would be to adhere to having your ContentPlaceHolders placed only withing the <body>
<form> tag if you're using custom masterpages, to avoid similar problems in the future.
I hope you find this information useful. please let us know if any issues persist.
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items