We have rather a special case since we have updated a 3.0.3 to 4.7.2. This has been done so that we now have an updated database running the "new" schema(this schema was added in start 4.x) and a clean 4.7 installation where we just have moved all the templates/xslt/css and such over. The solution has no custom code running, besides some usercontrol talking in to an access database somewhere(dont kill me not my doing hehe :) ).
But we experience sometimes when we publish nodes that they get published twice.
The XML gets fixed if re kill the umbraco.config and recycle the pool. But then a few publishes later it will occur again.
Nodes appears in XML twice after publish
Hey there
We have rather a special case since we have updated a 3.0.3 to 4.7.2. This has been done so that we now have an updated database running the "new" schema(this schema was added in start 4.x) and a clean 4.7 installation where we just have moved all the templates/xslt/css and such over. The solution has no custom code running, besides some usercontrol talking in to an access database somewhere(dont kill me not my doing hehe :) ).
But we experience sometimes when we publish nodes that they get published twice.
The XML gets fixed if re kill the umbraco.config and recycle the pool. But then a few publishes later it will occur again.
Hi Rasmus
Have you checked the database to see if there by any chance is some kind of "ghost" node?
/Jan
Hi, I'm one of Rasmus' colleagues and I just checked the database for ghost nodes using the following SQL statement and found no duplicates
Any other suggestions?
Exactly same problem here! :(
is working on a reply...