Mailing List Archive

[Bricolage #216] Publish status, date, version, etc.. not properly updated after story expired
// Add your reply above here
==================================================
Michael Herring updated this ticket at November 15th, 2010 @ 04:58 PM

After a published story is expired (not deactivated) its database flags are not properly updated. This leads to API calls (templates and SOAP requests, etc...) that will return the story as published even though it has been expired which causes broken links or template errors.

Steps to reproduce:
1. Create a story and publish (note DB shows proper published status, published version, publish_date, etc..)
2. Expire the story
3. Check database (you will find: publish_status = 't' and published_version = last published version)
Both of these columns should have different values:
publish_status = 'f'
published_version = null, 0, '' (what ever the Bricolage empty value need to be)

May also effect media? Observed in Bricolage 1.10.9
--------------------------------------------------------------------------------

Assigned: Bugs (at bricolage)
State: new
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/216-publish-status-date-version-etc-not-properly-updated-after-story-expired
Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/216-publish-status-date-version-etc-not-properly-updated-after-story-expired/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com
[Bricolage #216] Publish status, date, version, etc.. not properly updated after story expired [ In reply to ]
// Add your reply above here
==================================================
theory updated this ticket at November 22nd, 2010 @ 08:07 PM
* Milestone changed from "" to "2.0.1"

--------------------------------------------------------------------------------

Assigned: Bugs (at bricolage)
State: new
Milestone: 2.0.1
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/216-publish-status-date-version-etc-not-properly-updated-after-story-expired
Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/216-publish-status-date-version-etc-not-properly-updated-after-story-expired/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com
[Bricolage #216] Publish status, date, version, etc.. not properly updated after story expired [ In reply to ]
// Add your reply above here
==================================================
theory updated this ticket at November 22nd, 2010 @ 08:17 PM
* State changed from "new" to "invalid"
Historically, once a document was published, it was always considered published. The way to avoid this is, when searching for stories in a template, use the unexpired parameter. For example, to find all published, unexpired stories that are related to the current story, you'd do this:

my @stories = ref($story)->list({
related_story_id => $story->get_id,
active => 1,
unexpired => 1,
published_version => 1,
});
--------------------------------------------------------------------------------

Assigned: Bugs (at bricolage)
State: invalid
Milestone: 2.0.1
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/216-publish-status-date-version-etc-not-properly-updated-after-story-expired
Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/216-publish-status-date-version-etc-not-properly-updated-after-story-expired/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com