When republishing content the expiration date gets lost

Bug #1155697 reported by Kit Blake on 2013-03-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Silva
Medium
Sylvain Viollon

Bug Description

When content is published it gets a Publication Time and it may have an Expiration Time set. Sometimes an item needs to be edited, say to correct a typo. If an Expiration Time exists it should be preserved but in 3.x it gets lost. This needs to be covered in multiple publish scenarios:

1. If an Editor uses the item's Publish screen, the Expiration Time field should be sticky and contain the date set on the previous version. In 3.x it's empty. It's easy to overlook this.

2. If an Editor publishes using the Publish button in one of the other screens, the Expiration Time should just be preserved.

3. If the Editor publishes an item using the "Approve for future" publish option in a container, the form that comes up should be sticky and contain the Expiration Time set on the previous version. If more than one item is selected and one of the items has an Expiration Time, the Expiration time field should be filled with the date of the first item with an Expiration Time.

This problem also affect the Display Time in silva.app.news.

Kit Blake (kitblake) on 2013-03-16
Changed in silva-news-network:
importance: Undecided → Medium
no longer affects: silva-news-network
Changed in silva:
assignee: nobody → Sylvain Viollon (thefunny)
status: New → Confirmed
Sylvain Viollon (thefunny) wrote :

This is fixed in trunk.

Changed in silva:
status: Confirmed → Fix Committed
Changed in silva:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers