Maintenance mode
- Dominant language
- No language data
- Stars
- 39
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
[As discussed on the ckan-dev mailing list](https://lists.okfn.org/pipermail/ckan-dev/2016-April/009866.html), it would be nice to have a way to put the site into read-only maintenance mode in which the users can continue to use the site but cannot make any changes.
It seems that a good way for making the site read-only would be to block the writing API requests. However, the maintenance mode also needs to be communicated in the UI, for example using flash messages during login and by showing notes instead of the usual form elements on edit pages.
Obviously maintenance mode should be manageable via API calls (and probably also paster) to allow for automation.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by mapping the writing API requests and the login and edit-page UI flows, then review how maintenance state could be managed through API calls and paster. Done should include a defined read-only mode, UI communication, and automation controls, but the issue does not specify the implementation scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100