Ticket #493 (closed enhancement: fixed)
Make exclude from nav the default for content objects like before
| Reported by: | tom | Owned by: | brent |
|---|---|---|---|
| Priority: | major | Milestone: | 3.0.1 |
| Component: | General | Version: | eduCommons-3.1.0-Alpha |
| Keywords: | Cc: |
Description
Even though this seems trivial, it is a fairly serious issue for Marion's producers. When you bulk upload 500 objects, it is much easier to uncheck the "exclude from nav" box on 10 objects to make them appear in the left nav than to have to check "exclude from nav" on 490 objects to hide them. This is a fairly common use case.
Change History
comment:1 Changed 5 years ago by dray
- Type changed from defect to enhancement
- Component changed from General to ZipTransportTool
comment:2 Changed 5 years ago by dray
- Status changed from new to closed
- Resolution set to fixed
Changed behaviour for Files, Folders, Images and Documents to set exclude_from_nav to True on creation.
comment:3 Changed 5 years ago by dray
- Component changed from ZipTransportTool to General
Amended to state that this has been fixed in eduCommons, not ZipFileTransport?.
Note: See
TracTickets for help on using
tickets.

This is not a defect. This is an enhancement for changing the behavior of ZipFileTransport?.
A flag should be added to the Import Form to Include In Nav, or something similar.
The default behaviour in Plone3 (and since eduCommons 3.0), is to allow individual content objects to remain in nav, unless otherwise stated.