Clicking a node to edit content gives content of other node
I'm experiencing some weird behaviour on a v4.5.2 install...
Site running fine for couple of month, but now when we go and edit some content in the tree, we notice that the another document is shown in the right pane. And whatever other document we click on in the tree, it seems to always revert to the one document. (Reload nodes doesn't change a thing to that)
An app pool recycle doesn't always fix it (sometimes goes well for 3 to 4 documents, after which same behaviour occurs again).
Logging in and out doesn't solve it either
Making it worse, it's not always the same document it's being reverted too, it can happen to any document being edited, so it's not for a particular page in the tree
Clearing dependency handler folder and app pool recycle doesn't fix it either.
Could only find out a single thing when the revertion is happening, the response to /editContent.aspx?id=1493 (usign Fiddler) seems to include
Does this happen in all browsers on all computers? It sounds like the treeview js may not be 100% right so that when you click a page it loads a different ID... can you check that?
If you copy the site to another server (locally or a dev server), does the problem continue? I'm hoping to rule out some quirkiness on the server itself.
I've seen behaviour resembling this after creating nodes programmatically, deleting them and then retrying. Where it looked like Document id's and Node id's somehow got "out of sync". I solved the problem after reading a thread in the forum (can't find it again right now), where someone experienced something similar, and discovered that it went away after he'd emptied the recycle bin, and restarted IIS (restarting IIS is not necessary in may experience.)
Anyway - are there items in your recycle bin, and does the problem persist if you empty the bin?
@Rik: no exotic caching, wouldn't know what to cache in the backend, apart from the usual stuff that's being cached
@Doug: may have to try that, behaviour is identical on all browser flavors
@Jesper: did try your suggestion to no avail
Ok, it may get worse.... we sometimes get locked out, so when we do a logout/login, we don't get logged in anymore... :(
Other behaviour; if we wait for a while (altho can't specify what "a while" means in terms of seconds, minutes), we don't get the behaviour anymore, until we start clicking some documents again, after which (maybe be 2, 3, 4... docs) the same behaviour is back again.
The more 'weird' it sounds the more I have crazier ideas :)
First, file permissions. You know the drill.
Second, can you compare the database with a backup copy before the problems began? Almost sounds like you've got something corrupted in there.
Third, is this load balanced?
Fourth, got any event handlers?
I know this is a lot of work for you to track down but it must be either something so outrageously obvious that no one can see it, or else extremely obscure that will take a fair deal of digging and testing of unlikely options before the cause is found. Hang in there my friend, we'll get there!
Clicking a node to edit content gives content of other node
I'm experiencing some weird behaviour on a v4.5.2 install...
Site running fine for couple of month, but now when we go and edit some content in the tree, we notice that the another document is shown in the right pane. And whatever other document we click on in the tree, it seems to always revert to the one document. (Reload nodes doesn't change a thing to that)
An app pool recycle doesn't always fix it (sometimes goes well for 3 to 4 documents, after which same behaviour occurs again).
Logging in and out doesn't solve it either
Making it worse, it's not always the same document it's being reverted too, it can happen to any document being edited, so it's not for a particular page in the tree
Clearing dependency handler folder and app pool recycle doesn't fix it either.
Could only find out a single thing when the revertion is happening, the response to /editContent.aspx?id=1493 (usign Fiddler) seems to include
<form method="post" action="/umbraco/editContent.aspx?id=2216" id="form1">
Did you add some sort of exotic caching methods?
What happens when you save the page? which data is written to what node?
Does this happen in all browsers on all computers? It sounds like the treeview js may not be 100% right so that when you click a page it loads a different ID... can you check that?
If you copy the site to another server (locally or a dev server), does the problem continue? I'm hoping to rule out some quirkiness on the server itself.
Let us know what you find out.
cheers,
doug.
I've seen behaviour resembling this after creating nodes programmatically, deleting them and then retrying. Where it looked like Document id's and Node id's somehow got "out of sync". I solved the problem after reading a thread in the forum (can't find it again right now), where someone experienced something similar, and discovered that it went away after he'd emptied the recycle bin, and restarted IIS (restarting IIS is not necessary in may experience.)
Anyway - are there items in your recycle bin, and does the problem persist if you empty the bin?
Regards
Jesper Hauge
Ok, some answers to your comments:
@Rik: no exotic caching, wouldn't know what to cache in the backend, apart from the usual stuff that's being cached
@Doug: may have to try that, behaviour is identical on all browser flavors
@Jesper: did try your suggestion to no avail
Ok, it may get worse.... we sometimes get locked out, so when we do a logout/login, we don't get logged in anymore... :(
Other behaviour; if we wait for a while (altho can't specify what "a while" means in terms of seconds, minutes), we don't get the behaviour anymore, until we start clicking some documents again, after which (maybe be 2, 3, 4... docs) the same behaviour is back again.
weird, weird, weird... scratching my head :(
Cheers and tia for the help so far.
/Dirk
The more 'weird' it sounds the more I have crazier ideas :)
First, file permissions. You know the drill.
Second, can you compare the database with a backup copy before the problems began? Almost sounds like you've got something corrupted in there.
Third, is this load balanced?
Fourth, got any event handlers?
I know this is a lot of work for you to track down but it must be either something so outrageously obvious that no one can see it, or else extremely obscure that will take a fair deal of digging and testing of unlikely options before the cause is found. Hang in there my friend, we'll get there!
doug.
Are you hosting on your regular platform, or is this some client's/third party machine ?
Oh pretty good to get reminders of topics I've not yet decided who'll get the karma :P
Anyway, we found the solution by disabling caching for ascx and aspx on iis level, which resulted in the backend working like a charm again.
Hope this solution helps someone struggling with similar issues.
Cheers,
/Dirk
is working on a reply...