De-Publish Content?

«

Previous topic

|

|

Next topic

»

Author	Message
Thomas Brandl	Friday 12 September 2003 3:41:39 am Hi, I'm trying to deactive content, so it's still there and can be edited, but is no more available to the public - such as to withdraw publishing. Am I missing the obious? How can I do that? thanks! t
Alex Jones	Friday 12 September 2003 6:36:16 am Thomas, I'm not sure if there is an easy way to do this. The workaround we put into place was to create a hidden folder that was not visible to the public. Then we move the content that we don't want to be published into that area. I would love to see an easy way to do this without changing the locations. It would also be nice to publish something to a draft state without publishing it first. Alex Alex [ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ] <i>When in doubt, clear the cache.</i>
Paul Forsyth	Friday 12 September 2003 6:40:33 am You should use a workflow and unpublish through that. Have you tried out workflows yet? Paul
Paul Borgermans	Friday 12 September 2003 7:05:31 am Yes, use workflows and create (php programming) a workflow event which checks the condition of a special attribute to decide wether to unpublish a certain object. -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Thomas Brandl	Friday 12 September 2003 8:07:52 am Well, I realized there is a unpublish event, but all I want is a button that toggles whether the content is visible to the public or not. Besides am I working with a still workflow-buggy revision having problems, that are already fixed in the current svn, which unfourtunately is still not available. (i.e. content-publish-before is not fired) So I'm not playing around with workflows too much while still in beta. I do not understand at all, why one should use some kind of workflow for such a simple task. Neither do I understand, what trigger should get that workflow running?! In the meantime I find it more appropriate to delete and if neccessary restore content again. That is almost as simple as it's supposed to be. Thanks anyway! t

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 30 2025 23:47:08
Script start
Timing:	Jan 30 2025 23:47:08
Module start 'layout'
Timing:	Jan 30 2025 23:47:08
Module start 'content'
Timing:	Jan 30 2025 23:47:08
Module end 'content'
Timing:	Jan 30 2025 23:47:08
Script end

Main resources:

Total runtime	0.0248 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0058	588.0078	151.1953
Module start 'layout'	0.0058	0.0040	739.2031	220.6563
Module start 'content'	0.0098	0.0134	959.8594	1,001.7422
Module end 'content'	0.0232	0.0015	1,961.6016	33.9922
Script end	0.0248		1,995.5938

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0029	11.8340	14	0.0002
Check MTime	0.0012	4.7899	14	0.0001
Mysql Total
Database connection	0.0008	3.3674	1	0.0008
Mysqli_queries	0.0027	10.9773	3	0.0009
Looping result	0.0000	0.0403	1	0.0000
Template Total	0.0011	4.5	1	0.0011
Template load	0.0009	3.5009	1	0.0009
Template processing	0.0002	0.9547	1	0.0002
Override
Cache load	0.0006	2.4732	1	0.0006
General
dbfile	0.0011	4.5853	8	0.0001
String conversion	0.0000	0.0375	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs