It is ALL modules, on ALL pages!! (for this single user only) ie. The original page only contained an Text/HTML module, but now all of the other modules are exhibiting the same behaviour, eg. IFrame, User Defined Table and Text/HTML. Basically the only modules that work are those under Admin & Host.
While you might say "don't press back during an x operation, the recycle bin will save you", this is not good enough.. ie. had my connection dropped out for example, or I clicked the delete link twice, etc... there is such a high probability of these things happening in a web environment that any web application just has to accept it, and deal with it, and certainly not corrupt the database in any way. If a normal user can corrupt the database so easily, constrained to a normal browsers behaviour, just think of what a hacker could do to it...
I would have assumed that all operations are wrapped in sql transactions? (probably not though, if this could occur)
In the next week or so I will get into the source and no doubt find out what is going on. While the user is recognised as a superuser (admin/host menu is functioning), I think something is telling the modules that the account doesn't have edit permission.
Like I said, I am new to DNN so I don't know the data model yet, on the surface there appears to be 2 sets of user/role tables, etc.. So I am hoping that someone who already knows the model backwards could theorise on how an interrupted delete page op could result in a superuser account not having edit permission on any module. (view doesn't work either) But for all other users the site works perfectly.