While debugging, I'm getting repeated entries in the database every time I hit index.php?=finish. I think this is because $_SESSION is storing a lot of the data, so if they array is not overwritten, the same data are posted again.
Since it is likely that this application will be used by several participants in succession at the same computer, it is important that $_SESSION be emptied when each participant starts, in case a malfunction occurs and the test is ended prematurely.
Close one issues, open several others...
While debugging, I'm getting repeated entries in the database every time I hit `index.php?=finish`. I think this is because `$_SESSION` is storing a lot of the data, so if they array is not overwritten, the same data are posted again.
Since it is likely that this application will be used by several participants in succession at the same computer, it is important that $_SESSION be emptied when each participant starts, in case a malfunction occurs and the test is ended prematurely.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Close one issues, open several others...
While debugging, I'm getting repeated entries in the database every time I hit
index.php?=finish. I think this is because$_SESSIONis storing a lot of the data, so if they array is not overwritten, the same data are posted again.Since it is likely that this application will be used by several participants in succession at the same computer, it is important that $_SESSION be emptied when each participant starts, in case a malfunction occurs and the test is ended prematurely.
Fixed in https://github.com/mattbk/changeblindness/commit/1491499d247c6810deb9bfcc55e9a735bd998123.