Bug 1011259 - Adding a tag to a content spec should update the last modified property
Summary: Adding a tag to a content spec should update the last modified property
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: REST-API
Version: 1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.2
Assignee: Lee Newson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-23 23:49 UTC by Matthew Casperson
Modified: 2014-08-04 22:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-17 23:49:23 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Matthew Casperson 2013-09-23 23:49:42 UTC 
The Obsolete tag can now be used to filter the list of specs in DocBuilder. However, simply adding the obsolete tag to a content spec does not update the last modified date, which in turn means that the DocBuilder will not download the details for the spec.

Since adding a tag creates a revision, it also makes sense that the last modified property would be updated too.
Comment 1 Lee Newson 2013-09-24 01:09:10 UTC 
Fixed in 1.2-SNAPSHOT build 20130924-1102

This was caused by two things. The first was that it was using the wrong database field for the LastModified value. The second was the ContentSpecToTag and ContentSpecToPropertyTag wasn't setting the last changed field on the ContentSpec table.

Note: This version is currently live on the dev server.
Comment 2 Matthew Casperson 2013-10-15 04:03:02 UTC 
Confirmed that adding a tag updates the last modified date, and that a search using the new last modified date returns the expected result.
Note You need to log in before you can comment on or make changes to this bug.