[
https://issues.apache.org/jira/browse/ROL-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza closed ROL-1057.
---------------------------
Resolution: Not A Problem
I can see a use case for retiring (disabling) a user who has left a company yet
wanting to keep the blog up for others to still access it (e.g., for the tech
info on it.) If the blog is of little use anymore it would just as likely be
deleted, not just disabled.
> Retire weblog: Refine the admin setting
> ---------------------------------------
>
> Key: ROL-1057
> URL: https://issues.apache.org/jira/browse/ROL-1057
> Project: Roller
> Issue Type: Improvement
> Reporter: linda skrocki
> Assignee: Roller Unassigned
>
> To retire a weblog for a blogger who should no longer have blogging access to
> a given roller community, one must A) deactivate the blog via the preferences
> -> settings page, then B) an admin must disable user authentication access
> via the user admin page. I think if step B is executed, you should get step
> A for free. The use case for separating step A from B is to allow users to
> deactivate their blog if they no longer want it
> showing up on community listings (hot blogs).
> Once this change is implemented, the UI description for the User Admin field
> should be updated from this:
> Enabled (Disabled users are unable to login to Roller)
> to this (or something like it):
> Enabled (Disabled weblogs are not accessible by the user and no longer
> included in the community lists)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
