Closed ihh closed 6 years ago
Or, just create a single @guest
account with password guest
, that client logs user in as by default, and whose password or 'guest' status cannot be changed.
Cheaper solution (no proliferation of guest accounts from one-time visits)
When client is logged into a guest account, it hides inbox & follow buttons in navbar, along with name/bio customization buttons on config page
Guest accounts don't save drafts
Or, just relax some of the ClientController
method policies in config/policies.js
, specifically for the methods that retrieve/edit/expand symbol definitions (getOrCreateSymbolByName
, getSymbolsByOwner
...) and the autosuggest methods (suggestTemplates
, suggestSymbol
), and ensure that all those methods can operate and function sensibly without a playerID
Then modify the UI to allow the status, compose, grammar pages to function just fine when playerID
is not set, and make settings page change 'Log out' text to 'Log in' when playerID
not set, and also hide mailboxes tab; and then 'Continue as guest' just means 'continue with playerID
not set'