Feature ideas / requests
+1 vote for "hiding blocks"
Something where you can define what roles have access to create or edit certain part types would be a great enterprise level feature.
There is an "advanced permissions" mode that if you turn on - /should/ let you do all sorts of fun permission stuff around blocks and block areas.
Set certain parts of a page to be editable by the PR folks, but don't let them edit a navigation.. Or you can change the stuff YOU added but not someone else.. etc.
Now I say /should/ because this detailed level of permission was actually how concrete v4 worked all the time. We found the interface to be super bulky and no one really used it much. From our experience, every corporate client ASKS for workflow management and area level permissions - but then some guy named Bob ends up with an admin account that can do everything, and occasionally grants similar accounts to smart marketing people. So when we decided to re-vamp the UI from scratch, we rolled out the simpler permissions model that c5 defaults too. So far, we've spent a far larger amount of time testing it than the old detailed level permissions that are still under the hood, but typically left blank.
Long story short, setup a test install, read this:
and tell me if that doesn't do what you're asking for on the hiding content question...
Most projects don't need such a detailled level of permissions. But haveing a few more options than the simple model would be great!
Giving the user the flexibility to do everything might be nice but it can confuse too!
I think hiding blocks isn't that complicated (it works by changing a field rows in the database). For such an easy task, it's definitely too much to use the advanced permission model!
that stuff could move to the marketplace, once its ready, particularly if its a seamless install. One of the things we've been dreaming of is being able to browse/buy/add blocks FROM a c5 install and not even coming to this site..
certainly if we were able to add a BROWSE NEW tab to the add block popup, i'd strip down that default list in a heart beat...
in the meantime, yes - you could delete some rows from the blocks table and those guys would disapear
For 3 sites i deleted most of them for i wouldnt use them.
Or a good feature might be categorizing blocks... so u can use a kind of foldout or whatever method.
Some sites need a lot of blocks, but that way the list would be to long.. categorizing would help
I'm much happier, when I could hide a couple of things using the dashboard but in the meanwhile I'll just remove these rows from the table.
Set to 0 to hide a block and 1 to show it... That's a very easy change and you probably just have to modify one simple query.
Modifying db values is not nice but still better than removing lines from it.
This field could then be used in the dashboard when someone has the time to add this feature?!
When the administrator have finished to make this kind of setup, he would have in the section of the list of the blocks, only those that he need for now. And also, he would have the opportunity to change all that in the future ('cause things change when it grow, no?).
It would be a fast setup, a great feature.
This page seems to be deleted !!