Ticket #10764 (closed Bug: fixed)
/Members folder blocks right column portlets so portlets do not show in member's home folders
|Reported by:||sergey_v||Owned by:||bslash|
When setting up a new instance, Plone creates /Members folder and blacklists all types of portlets in it - the reason for that is because we don't want portlets on the users search page which is set as an index page of /Members.
There's a downside of this approach, however: if we enable creation of member folders, the folders themselves and all content inside them will have no right-hand portlets - this is especially confusing if there are content-type or group portlets assignments - imagine a custom content type which is supposed to always have a portlet displayed - it works fine everywhere apart from members' home folders.
The content-type and group folders can be turned back on on a per-homefolder basis (though it's an ugly workaround), but there's no way to re-enable context portlets assigned at the root of the site (apart from re-assigning them anew).
A better solution IMO would be to disable right-hand portlet slot in the corresponding templates (member_search_form and member_search_results) without blocking any portlets at /Members - at least this is what the intention actually is - not to show portlets in those templates instead of blocking them everywhere below the /Members folder.
The code which does the blocking is in Products/CMFPlone/setuphandlers.py, lines 382:388 - I think removing that and blocking the slot in the templates will do the trick.
Tested with 4.0b4
- Status changed from new to assigned
- Owner set to pingviini
- Owner pingviini deleted
- Keywords TuneUpgreenbelt added; TuneUp greenbelt removed
- Version set to 4.1