Branch name:
implement-disabling-explorations
Link to the relevant commit(s):
https://code.google.com/p/oppia/source/detail?r=d036988d6abebb589a0757789d8a6e8b
6b019f54&name=implement-disabling-explorations
Purpose of code changes on this branch:
To support disabling explicit explorations if, for some reason, they cannot be
played or edited for one reason or another. Typically, this is going to be used
for explorations which are not able to be converted during a migration.
When reviewing my code changes, please focus on:
Everything, but especially on whether we need to do any sort of additional
security for these explorations. I figured if users tried to make explicit GET
requests to the other handlers, it would fail due to validation errors anywhere
it tried getting a bad exploration. Thoughts?
After the review, I'll merge this branch into: develop
Original issue reported on code.google.com by bhenn...@google.com on 7 Jul 2015 at 12:51
Original issue reported on code.google.com by
bhenn...@google.com
on 7 Jul 2015 at 12:51