I know this isn't exactly new, but it's really crying for a solution:
We often have a few pages (or other objects) that contextually belongs in more than one place (folder).
To avoid creating redundant objects means using collections or custom views, etc. all of which are too complicated for content managers that aren't plone savvy.
How can we accomplish this?
Often the content63 votes
I’m doing some research into something similar, in the package collective.alias. I’m not sure how well it’ll work yet, but it’s coming along. This is based on SimpleAlias (in principle, there’s no code sharing), which already works today (but has a few limitations).
Moving a viewlet from one viewlet manager to another is a pain in Plone today. This should be possible through the web interface too.34 votes
We’re going to solve this (and lots more) with Deco.
As the author, I'm completely +0 on the idea (despite UserVoice making me spend a vote to create this), but I've received some comments from more than a few people that they'd like to see an enhanced GloWorm ship with Plone. What's the consensus from the Plone public?24 votes
Deco will allow for full control of layouts, obviating the need for viewlets and viewlet managers.
People should be able to just browse through login-protected contents, even if they have other than a reader role for those contents. Instead of directly displaying all the content bars and actions for editing upon login, there should be an action/button/link to get to the 'editing mode'.26 votes
Plone is most useful used with products, and configured for a certain use such as intranets, member site, ecommerce etc. It would improve a potential clients initial experience of using plone if they could download and use some pretested distributions of plone directly from plone.org. At it's simplest these could just be buildouts documented in a wiki (like drupals site recipes), or alternatively they could be supported in PSC as downloadable entities.13 votes
- Don't see your idea?