3 replies to this topic

[elr205]

I have a site built with etomite. When I try to edit a particular chunk, I get an error message that says Cris D. is currently editing that snippet, and try again when no other user is editing. Then it blocks me from being able to do anything with the chunk.

What's going on here?

[Cris D.]

Sounds odd. In the manager you can hit "Remove Locks" to take control of any current editing going on. Either someone else must have logged in using my username, or I have helped on your site some time in the past and did not log out properly before exiting the session, or you are a past student having a lend. Out of interest can you PM me address of the site I am supposed to be editing?

[edit] Don't worry, have better things to do with my time than trying to hack into others' web sites and play with their chunks, I would however be concerned if someone has access to your site that you are not aware of, I would be checking the audit trail for unusual activity.[/edit]

Edited by Cris D., 13 April 2008 - 09:54 AM.

[elr205]

Thanks -- that did it. I'll PM you the site, but I don't know what that means or how to do it! (Obviously I'm quite new to all this.)

Cris D., on Apr 13 2008, 09:42 AM, said:

Sounds odd. In the manager you can hit "Remove Locks" to take control of any current editing going on. Either someone else must have logged in using my username, or I have helped on your site some time in the past and did not log out properly before exiting the session, or you are a past student having a lend. Out of interest can you PM me address of the site I am supposed to be editing?

[edit] Don't worry, have better things to do with my time than trying to hack into others' web sites and play with their chunks, I would however be concerned if someone has access to your site that you are not aware of, I would be checking the audit trail for unusual activity.[/edit]

[Ralph]

With a multi-user site, where several people are maintaining resources, this can happen if a user closes their browser or leaves the site without exiting from an open resource... This could also happen if the server session were to be deleted by a cleanup routine while editing... How the errant record ended up in the database is hard to explain unless Cris had been enlisted to debug a problem... I don't recall any records being inserted during an install as that portion of the install SQL should have been omitted...