Publishing issue with ez3.3 beta 2, News Package

Previous topic

Developer

Next topic

Author	Message
Marco Zinn	Wednesday 10 December 2003 12:46:51 pm If you try ez3.3 beta 2 with the news package and have problems with publishing, read this: Please note, that the "news" package does not work as in beta 1, when you want to publish something. In beta2, there is a "before publish content" trigger with an approval workflow. I usually use the admin user to test betas... and even the admin user cannot publish content, because it needs to be approved by the editor user. Best option: Go to Setup->Triggers and remove the workflow from the first trigger. If you really want to use approval: You must have a running cronjob for the workflow to work at all. And you must know, that the passwork of the user "editor" is the same as for "admin". ez, please don't use approval workflows for the final release package. Marco http://www.hyperroad-design.com
Björn Dieding@xrow.de	Thursday 11 December 2003 10:16:25 am well I think it was not wise that eZ implmented it because 1.) dumb users don't know how it by pass it and set it up 2.) expericenced users know it so they can easily implement it Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/
Marco Zinn	Thursday 11 December 2003 12:17:45 pm Hi Björn, I agree ;) That's why i wrote the post. Handling with beta releases is a hard job without these "traps". I was trying to edit a poll and noticed, that it was not published. I thought "A feature? Maybe you cannot edit an open poll". Then i saw the "pending" status and tracked it down. I'm sure, that most users will not have knowledge about setting up cron-jobs, because for low-end setups, you won't need it. Marco http://www.hyperroad-design.com

Author

Message

Marco Zinn

Wednesday 10 December 2003 12:46:51 pm

If you try ez3.3 beta 2 with the news package and have problems with publishing, read this:

Please note, that the "news" package does not work as in beta 1, when you want to publish something.
In beta2, there is a "before publish content" trigger with an approval workflow. I usually use the admin user to test betas... and even the admin user cannot publish content, because it needs to be approved by the editor user.
Best option: Go to Setup->Triggers and remove the workflow from the first trigger.
If you really want to use approval: You must have a running cronjob for the workflow to work at all. And you must know, that the passwork of the user "editor" is the same as for "admin".
ez, please don't use approval workflows for the final release package.

Marco
http://www.hyperroad-design.com

Björn Dieding@xrow.de

Thursday 11 December 2003 10:16:25 am

well I think it was not wise that eZ implmented it

because

1.) dumb users don't know how it by pass it and set it up
2.) expericenced users know it so they can easily implement it

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Marco Zinn

Thursday 11 December 2003 12:17:45 pm

Hi Björn,
I agree ;) That's why i wrote the post.
Handling with beta releases is a hard job without these "traps".
I was trying to edit a poll and noticed, that it was not published. I thought "A feature? Maybe you cannot edit an open poll". Then i saw the "pending" status and tracked it down.
I'm sure, that most users will not have knowledge about setting up cron-jobs, because for low-end setups, you won't need it.

Marco
http://www.hyperroad-design.com

eZ debug

Timing:	Jan 18 2025 20:58:05
Script start
Timing:	Jan 18 2025 20:58:05
Module start 'layout'
Timing:	Jan 18 2025 20:58:05
Module start 'content'
Timing:	Jan 18 2025 20:58:05
Module end 'content'
Timing:	Jan 18 2025 20:58:05
Script end

Main resources:

Total runtime	0.6596 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0051	588.0469	152.6406
Module start 'layout'	0.0051	0.0039	740.6875	39.4766
Module start 'content'	0.0090	0.6493	780.1641	547.7734
Module end 'content'	0.6583	0.0012	1,327.9375	12.1250
Script end	0.6595		1,340.0625

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.5353	16	0.0002
Check MTime	0.0013	0.2000	16	0.0001
Mysql Total
Database connection	0.0006	0.0917	1	0.0006
Mysqli_queries	0.6080	92.1822	57	0.0107
Looping result	0.0006	0.0859	55	0.0000
Template Total	0.6288	95.3	2	0.3144
Template load	0.0023	0.3437	2	0.0011
Template processing	0.6265	94.9847	2	0.3133
Template load and register function	0.0001	0.0159	1	0.0001
states
state_id_array	0.0010	0.1566	1	0.0010
state_identifier_array	0.0009	0.1292	2	0.0004
Override
Cache load	0.0018	0.2672	23	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0011	0.1639	2	0.0005
Fetch class attribute name	0.0010	0.1511	5	0.0002
XML
Image XML parsing	0.0009	0.1358	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0016	6	0.0000
General
dbfile	0.0016	0.2451	22	0.0001
String conversion	0.0000	0.0020	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
3	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 16 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs