How to have Page unpublished by default?
Permalink
Hi there, I thought I would start a new post for this. New to Concrete5 and think it has great features.
As far as I am aware there is no easy way to unpublish content for dummies by default which is a bummer as I deal with lots of dummies.
When you add a page - it seems to be live by default, unless you mess around with permissions on the parent page and inheritance etc.
What is the best way to have it unpublished by default? Set up a custom attribute? is_live etc? or would this conflict with publish dates - auto navs etc?
As far as I am aware there is no easy way to unpublish content for dummies by default which is a bummer as I deal with lots of dummies.
When you add a page - it seems to be live by default, unless you mess around with permissions on the parent page and inheritance etc.
What is the best way to have it unpublished by default? Set up a custom attribute? is_live etc? or would this conflict with publish dates - auto navs etc?
Thanks for the reply. Yes was just coming to this realization. And can see the reasons behind not having just one un-publish button.
(However it would by nice for dummy clients to have just one button.)
I was thinking another way would be to set up a drafts page in the sitemap and have all subpages hidden. The pages could just then be moved to a live section. However I think the issue for the dummy client there is I think the url-s don't get updated automatically and therefore the client would have to rewrite them.
UPDATE - just realized this wouldn't be ideal as you would have to have a draft section for every page type.
(However it would by nice for dummy clients to have just one button.)
I was thinking another way would be to set up a drafts page in the sitemap and have all subpages hidden. The pages could just then be moved to a live section. However I think the issue for the dummy client there is I think the url-s don't get updated automatically and therefore the client would have to rewrite them.
UPDATE - just realized this wouldn't be ideal as you would have to have a draft section for every page type.
Ok - Got the custom attribute settings as defaults. Is there anyway to move the custom attributes to standards attributes on the properties window? This would be useful to have it come on the first tab.
Sure thing.
Go to your dashboard > page attributes.
You can rearrange them by opening an attribute and changing its "Group set" field.
Sure thing.
Go to your dashboard > page attributes.
You can rearrange them by opening an attribute and changing its "Group set" field.
Edit: oh, I misread your question, sorry. I'll get back to you on that one shortly.
Go to your dashboard > page attributes.
You can rearrange them by opening an attribute and changing its "Group set" field.
Sure thing.
Go to your dashboard > page attributes.
You can rearrange them by opening an attribute and changing its "Group set" field.
Edit: oh, I misread your question, sorry. I'll get back to you on that one shortly.
Ok, got it.
You can move the custom attributes tab's contents to the standard attributes, but you have to do some coding:
/concrete/elements/collection_metadata_fields.php
and also
/concrete/elements/collection_metadata.php
There you can rearrange everything, but HTML knowledge is a must here.
Make sure to place these files under their proper /elements/ position so they would override the /concrete/elements/ originals.
Make sure to check shahroq's link (http://www.concrete5.org/documentation/how-tos/editors/prevent-a-newly-added-page-from-publishing/), but he already explains pretty much the same conclusions to which we've come.
You can move the custom attributes tab's contents to the standard attributes, but you have to do some coding:
/concrete/elements/collection_metadata_fields.php
and also
/concrete/elements/collection_metadata.php
There you can rearrange everything, but HTML knowledge is a must here.
Make sure to place these files under their proper /elements/ position so they would override the /concrete/elements/ originals.
Make sure to check shahroq's link (http://www.concrete5.org/documentation/how-tos/editors/prevent-a-newly-added-page-from-publishing/), but he already explains pretty much the same conclusions to which we've come.
Thanks I will look into this. I have developed a page settings block where I can add meta descriptions, thumbnails and post to facebook etc. I might see if I can extend it to have a tickbox/button to tick all four page attribute boxes also to publish / unpublish. Thanks for your help.
http://www.concrete5.org/documentation/how-tos/editors/prevent-a-newly-added-page-from-publishing/
That is, if you want it done with page attributes. Advanced permissions and inheritance would be the other way to go.
Also, the easy way to unpublish, is to delete the page. It will just go to the trash can from where it can be restored later.