[
https://issues.apache.org/jira/browse/JSPWIKI-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187078#comment-15187078
]
Lance Bader commented on JSPWIKI-931:
-------------------------------------
For an ordinary page edit, the most recent changes should be attributed to the
most recent editor. If I follow a blog entry _Permalink_, I would expect the
page to the attributed to the most recent editor. But on the web log page,
where all the entries are together, I would expect the entry to be attributed
to the person who created the entry, no matter who (or how many times) the
entry is edited. It is important to show who originated the entry no matter
who contributed later. If anyone ever needs to audit the edit changes, they
can always follow the _Permalink_ and review each update.
The real problem here is that the entry is attributed to 1.author=unknown on a
wiki where only authenticated users can edit a page.
It is really annoying in my case where the blog contains sprint status from
each teammate. The entry's originator is important information for parsing the
posted status.
> WeblogEntryPlugin creates entry "by unknown" when it should be an
> authenticated user
> ------------------------------------------------------------------------------------
>
> Key: JSPWIKI-931
> URL: https://issues.apache.org/jira/browse/JSPWIKI-931
> Project: JSPWiki
> Issue Type: Bug
> Affects Versions: 2.10.1
> Environment: AWS Linux, Tomcat 8.0.23, Java JDK 1.8.0_45
> Reporter: Lance Bader
> Attachments: EntryWithByUnkown.png, PermalinkShowsWho.png,
> jspwiki.policy
>
>
> Even though the wiki is configured so that only authenticated users and edit
> or even view pages in the JSPWiki, the WeblogEntryPlugin creates entries
> where the by line reads _By unknown_. 7 out of 21 entries are shown this
> way. If you follow the entry's Permalink, the entry will show _This page was
> last changed on 29-Feb-2016 18:44 by ..._ with the correct user name.
> I have not been able to pinpoint the scenario that exposes this defect, but I
> suspect it occurs when the user's Tomcat session expires, the create entry
> link is clicked, and then they are forced to log in again. However, there is
> reason to believe that it occurs if the user has ever been forced to log in
> after their session expires, even on some unrelated page.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
