[
https://issues.apache.org/jira/browse/ROL-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza closed ROL-2035.
---------------------------
Resolution: Not a Problem
Hi Juergen, after checking our current commenting system I forgot that browsers
already store the username and email from previous comments; as soon as I type
in "G" my full name appears, same with the email. So it's not the case that a
blog writer needs to keep manually typing in this info with every comment as I
had thought, which had prompted me to reopen this issue. Another problem with
hardcoding this info in every comment field is that the blog owner may get the
erroneous impression that Roller is prepopulating this same info for every blog
reader, i.e., all readers to my blog will see my name and email address in
those fields. So I'm going to keep Roller as-is without this change.
I understand for your Intranet situation you may need to do some template
customizations as suggested earlier, the Roller User mailing list is available
to help you here.
> Prepopulate Comment Username and Email fields for logged-in users
> -----------------------------------------------------------------
>
> Key: ROL-2035
> URL: https://issues.apache.org/jira/browse/ROL-2035
> Project: Apache Roller
> Issue Type: Improvement
> Components: Comments
> Affects Versions: 5.1
> Reporter: Jürgen Weber
> Assignee: Roller Unassigned
> Priority: Minor
>
> Update (Glen): For logged-in bloggers, pre-populate the name and email fields
> with the ScreenName and Email values of the User object. Make these fields
> writable, however, should someone want to modify their values or if it's
> someone else commenting. Retain the math question to guard against spammers
> registering and then flooding blog entries with comments.
> Was (original poster Juergen): For logged-in users Roller knows name and
> email. So the corresponding fields in comments should be auto-filled and
> maybe even non-editable. Also the "Please answer this simple math question"
> should be gone for logged-in users.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
