Hello
I''m using the login generator on my application, and I found a problem
with it.
My application is a rack inventory thing, which shows a rack with
machines and KVMs and you can click on a rack item to show/edit/destroy
it. The edit and destroy actions are protected by the login generator.
Now say a user clicks on "destroy" for some machine. He''ll be
shown the
login screen. Now, say he gives up and moves to some other part of the
application, browses a bit where logging in isn''t necessary, and then
decides to login clicking on the "login" link. When he does that, and
logs in successfully, that previous destroy action will be triggered,
and the machine will be removed, although that was probably not the
intention.
Is there a way to "clean" the action information so that some previous
undone action won''t be triggered on a future login attempt?
Best regards,
Andre