Don't load update page for read-only journals
Short, concise description of the idea
When a user's journal is read-only, display the "journal is read-only" page instead of the "update journal" page. This would prevent users from composing entries that they will not be permitted to submit.
Full description of the idea
It is very frustrating to have composed an update only to find it cannot be submitted. It would be very nice to be notified of read-only status before spending the time to compose.
- User doesn't waste time and energy writing something that cannot be posted immediately.
An ordered list of problems/issues involved
- It may be that the "journal read-only" message is triggered by a failed attempt to write to the database. Implementing this would be more than just reordering of code, if this is the case.
An organized list, or a few short paragraphs detailing suggestions for implementation
- Write a function/method to check the status of a user's cluster.
- Call the function before loading the update journal page, and if necessary, load the read-only page instead.