If a user accidentally (or on purpose...) modifies the local repository to set the field 'cap' of table 'user' to NULL or empty string, the web interface for managing users stops responding. (On Windows, accessing that page when running "fossil ui" produces an application crash message, logged to the Windows Event Log, eventvwr.exe.)
The following example (!!WARNING!! don't do this in production :-) ) clears up the 'cap' field of a random record in table 'user': fossil sqlite -R myrepo.fossil "UPDATE user SET cap=NULL WHERE _ROWID_=(SELECT ABS(RANDOM())%MAX(_ROWID_) FROM user)" Its effect is that, when accessing the "Admin-Users" menu in the repository's Web interface (/setup_ulist), it times out and produces (on Windows) an Application Error logged onto Windows Event Log. 1) Suggested workaround: in the schema of table 'user', define column cap TEXT NOT NULL DEFAULT '' 2) https://www.fossil-scm.org/index.html/artifact/63ef85778a8ca6007f8ded284589272f87d392bd?txt=1&ln=164-200
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
