error page on locked missions/tracks

[privat]

If the track is open, locked mission should says that the mission is locked.
If the track is hidden/inaccessible (of the player not authenticated), the track page and its missions should 404

Constraints:

• do the locking server-side
• bypass the lock in debug mode (just add whatever refinement in src/debug.nit and/or in the config file)

[Morriar]

I think there is another issue in here: enable/disable tracks.

Please open another issue with the label enhancement for that.

Working on the locked status though.

[privat]

is this closed by #46?

[privat]

Reopened because #46 was client-side only, and thus partially reverted in #77

[Morriar]

I don't understand. On one hand you want to be able to see locked mission and you don't want a lock client-side.

What is the true concern behind this issue?

[privat]

What I want now?

• do not lock anything effectively

What that means?

• display "lock" if you want to test that the lock message is OK
• still allow the tester to see the mission and to play it

Rationale

• the tester does not want to spend numerous clics or to finish the previous missions in order to test something on a specific mission.
• moreover, if the lock mechanism, is buggy. then the tester can still test other parts of the system.

What I want later?

• enforce lock policy for the production server
• but do the locking server-side. There is no point all all to simulate it client-side
• still allow to bypass locks in the devel mode to test things

How to implement that later?

• I do not think that we need to think too much about that right now
• If we want a full lock (without any information), the API could just send a 403 HTTP response for locked ressources
• If we want a full lock + debug mode. maybe you can attach a god flag the the player in order to let the API bypass the lock check for those selected people

[Morriar]

To me, what you need is a debug/god mode.

See #111