Ticket #11599 (confirmed Bug)
content_status_history cannot unset dates: Cannot batch unset Expiration and Publication dates
Reported by: | msmith64 | Owned by: | limi |
---|---|---|---|
Priority: | major | Milestone: | 4.x |
Component: | General | Version: | 4.2 |
Keywords: | expiration, publication, workflow | Cc: |
Description (last modified by seanupton) (diff)
Despite help-text such as "If no date is chosen, it will never expire.", attempted un-setting of dates (e.g. expiration) fails in content_status_history when accessed either via folder_contents or via the workflow action menu "Advanced" link.
For items in which these dates are not editable on the Edit tab, a user is locked into choosing some expiration date once chosen, without any practical ability to unset it. The current workaround is to set an arbitrary (but strictly incorrect) expiration date far-ahead in the future for items.
Confirmed in Plone 4.2, original description as follows:
---
folder contents view offers a way to change the state of multiple objects at once, even recursively. The interface for doing this also offers access to the Publication and Expiration dates. You can set the dates via this interface, but there doesn't appear to be a way to unset the dates. I've tried on Plone 3.3.5 and 4.1b. Here's what I tried:
- Create a fresh install.
- Add an event inside the events folder. Leave its exp/pub dates alone.
- Add a second event, again leaving its exp/pub dates unset.
- Click 'folder contents' on the events folder and select both events.
- Click "change state".
- Select an expiration date in the past for both events. Set the state to "Publish".
- Note that the events are expired.
- Select both events again in /events/folder_contents
- Click "change state".
- Try to set the exp date back to '--' for all its subfields.
- Change the state if you like (it doesn't matter), and then save.
- Note that the event is still expired.
Shouldn't it be possible to batch unset a value you can batch set?
Change History
comment:1 Changed 4 years ago by kleist
- Component changed from User Experience and Interface to Infrastructure
- Milestone set to 4.x
comment:3 Changed 4 years ago by kleist
- Keywords expiration, added; expiration removed
- Status changed from new to confirmed
- Version set to 4.1
comment:4 Changed 3 years ago by seanupton
- Keywords publication, workflow added; publication removed
- Version changed from 4.1 to 4.2
- Description modified (diff)
- Summary changed from Cannot batch unset Expiration and Publication dates to content_status_history cannot unset dates: Cannot batch unset Expiration and Publication dates
Updated description scope to all of content_status_history: un-setting dates fails for both single and multiple items, contrary to help text description.