roller-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Johnson (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (ROL-1797) Option to allow access to usernames
Date Sat, 23 May 2009 14:15:45 GMT

     [ https://issues.apache.org/jira/browse/ROL-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dave Johnson resolved ROL-1797.
-------------------------------

    Resolution: Fixed

implemented in trunk, see commit:
   http://svn.apache.org/viewvc?rev=753383&view=rev

> Option to allow access to usernames
> -----------------------------------
>
>                 Key: ROL-1797
>                 URL: https://issues.apache.org/jira/browse/ROL-1797
>             Project: Roller
>          Issue Type: Improvement
>          Components: Page Rendering & Management
>    Affects Versions: 4.0
>            Reporter: David Johnson
>            Assignee: David Johnson
>            Priority: Minor
>             Fix For: 5.0
>
>
> Roller's UserWrapper object ensures that real usernames cannot be displayed in blog pages
and instead returns the user's screennames.
> This request for enhancements asks for this behavior to be made configurable via roller.properties
like so:
>    # Normally, for security purposes Roller keeps usernames private and the user
>    # getUserName() method in templates actually returns the user's sceenname.
>    # If you want templates to have access to real usernames, set this to false.
>    user.privateUserNames=true
> The UserWrapper class will check this property to decide whether or not to return the
real username.
> The default will be to keep usernames private and hidden.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message