Containers (folders, publications) should retain the last author information

Bug #162545 reported by Andy Altepeter
2
Affects Status Importance Assigned to Milestone
Silva
Fix Released
Medium
Kit Blake

Bug Description

Containers need to keep the last author, and the SMI needs to show that instead of n/a (contents, publish tab, etc).

How to do this:

1) When a container is created, set the author to the creator
2) When a container's metadata is updated, update the author
3) Change the contents (and publish tab, and wherever else) screen to display the author

I think a related issue was to ensure the lastmod date is updated (and also displayed in it's column), so verify this.

4) Another feature would be to update the containers data when the index item is updated

Changed in silva:
assignee: nobody → aaltepet
importance: Undecided → Medium
milestone: none → 2.1
Changed in silva:
milestone: 2.1 → none
Revision history for this message
Andy Altepeter (aaltepet) wrote :

This was a rather "light" change in the code. It turns out lastauthor information was already being stored for containers, but there was code to intentionially disable it for containers. This is good, since now the last author will be displayed in the author column.

I've enabled this feature, and added to the list of container actions that cause it's last author / modified date to be updated. Here's the list:
Container last author and last modified dates are updated
        when objects are moved, deleted, added, pasted into the container,
        when the container's metadata is modified (properties tab and settings
        sub-tab), and when the container is converted to/from a publication/folder.

I've made these changes in a branch:
https://svn.infrae.com/Silva/branch/aaltepet/Silva-Container-authors-162545

Changed in silva:
assignee: aaltepet → kitblake
status: New → In Progress
Revision history for this message
Eric Casteleijn (thisfred) wrote :

I don't see anything problematic, so I say merge this branch (that is, as long as the tests agree with me ;)

Revision history for this message
Andy Altepeter (aaltepet) wrote :

Merged this back into the trunk. The tests appear to be unstable currently (at least there were 36 failure both before and after I merged this branch back into the trunk.

Changed in silva:
milestone: none → 2.1
status: In Progress → Fix Committed
Changed in silva:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.