Last modified: 2005-10-29 03:10:35 UTC
A number of things try to write to the database when read-only mode is on. This can produce
annoying error messages when attached to a really read-only database that's locked, or can cause
data corruption if you're simply implicitly assuming the wiki will not write.
The user_newtalk expiration check on login is one example. Other expirations (objectcache,
ipblocks) should be checked also, and there may be others.
1.4.0 released; kicking back to 1.5 blockers.
The database class now silently drops all write attempts when read-only mode is on.