Antlog issue

[Spaceman]

Good afternoon.

I have set up AWS 57 on ant log, and I have seemed to have locked the database.

Is it broken, or have I broken it?

Could someone take a look who knows please?

Thanks

[BeligerAnt]

My guess is that you downloaded the database after you created the event. The intent is that it only locks if you are the owner of an imminent event (i.e. one where the online registration is closed, but there may be a slight flaw in the logic. That or someone else managed to lock it.

I'll take a look and unlock it, no worries.

PS I took a look at the database and you are not the culprit It was Razerdave who locked the database, so it looks like the logic worked properly as he is the owner of AWS56 which was in the correct state to cause the database to lock.

The database has to be locked while an event is running to prevent horrible problems if new teams/robots are created online and at the event.

[BeligerAnt]

The results of AWS56 have been uploaded and the database unlocked. Normal service has been resumed

[Spaceman]

Another issue.

in AWS 57, Robototron has decided to enter himself into his own group all ready. pretty sure thats not right...

[BeligerAnt]

Ummmm I didn't think that was possible!

I'll look into it...

It can easily be fixed, but I'm intrigued as to how it even happened...

[BeligerAnt]

The database is all fixed, but I'm still trying to work out how it happened...

[Ocracoke]

My apologies, I seem to have locked the database for Antlog. Went to the top bar and clicked on export by mistake, could it be unlocked please?

[Ocracoke]

Ah, I seem to have managed to unlock it via reopening registration. Apologies!

[Henwilled Antweight team]

Antlog appears to be locked. At the time I didn't know this so, I accidentally deleted my team ( as I was trying to edit my robot's names). I will make a new team the same as before, but can it please be un locked, if it is.