re-using a newsletter cause fatal error

Next topic

Author	Message
Peretjatko Alexandre	Wednesday 28 January 2009 2:04:08 am Hi, I've got some reccurent newsletters and some manual both work find. When I'm trying to re-use an old manual newsletter from the BO ( throught the "Newsletter" tab, in the newsletter type list, open my newsletter type, clic on "archive", edit a newsletter, and then press the "copy" button" ), when the cron job run it crash in a fatal error : <b> Fatal error: eZ publish did not finish its request The execution of eZ publish was abruptly ended, the debug output is present below. </b> Is it a bug ? Does the last version of eznewsletter solve this bug ? By the way, I'm using eznewsletter V 1.5.2. Regards. Alexandre PERETJATKO. Regards Alex. -------------------------------------------------------------- Personnal website : http://www.alex-design.fr

Author

Message

Wednesday 28 January 2009 2:04:08 am

Hi,

I've got some reccurent newsletters and some manual both work find.
When I'm trying to re-use an old manual newsletter from the BO ( throught the "Newsletter" tab, in the newsletter type list, open my newsletter type, clic on "archive", edit a newsletter, and then press the "copy" button" ), when the cron job run it crash in a fatal error :
<b>
Fatal error: eZ publish did not finish its request
The execution of eZ publish was abruptly ended, the debug output is present below.
</b>

Is it a bug ? Does the last version of eznewsletter solve this bug ?

By the way, I'm using eznewsletter V 1.5.2.

Regards.

Alexandre PERETJATKO.

Regards

Alex.
--------------------------------------------------------------
Personnal website : http://www.alex-design.fr

eZ debug

Timing:	Jan 18 2025 05:04:37
Script start
Timing:	Jan 18 2025 05:04:37
Module start 'layout'
Timing:	Jan 18 2025 05:04:37
Module start 'content'
Timing:	Jan 18 2025 05:04:38
Module end 'content'
Timing:	Jan 18 2025 05:04:38
Script end

Main resources:

Total runtime	0.7844 sec
Peak memory usage	4,096.0000 KB
Database Queries	48

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0063	589.2969	152.6563
Module start 'layout'	0.0063	0.0044	741.9531	39.4922
Module start 'content'	0.0107	0.7724	781.4453	431.2500
Module end 'content'	0.7831	0.0013	1,212.6953	8.1328
Script end	0.7843		1,220.8281

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.4419	16	0.0002
Check MTime	0.0014	0.1799	16	0.0001
Mysql Total
Database connection	0.0007	0.0955	1	0.0007
Mysqli_queries	0.7472	95.2568	48	0.0156
Looping result	0.0004	0.0551	46	0.0000
Template Total	0.7480	95.4	2	0.3740
Template load	0.0019	0.2450	2	0.0010
Template processing	0.7461	95.1183	2	0.3730
Template load and register function	0.0002	0.0253	1	0.0002
states
state_id_array	0.0009	0.1181	1	0.0009
state_identifier_array	0.0007	0.0886	2	0.0003
Override
Cache load	0.0015	0.1944	14	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0746	1	0.0006
Fetch class attribute name	0.0006	0.0787	1	0.0006
XML
Image XML parsing	0.0001	0.0145	1	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0005	1	0.0000
General
dbfile	0.0006	0.0744	10	0.0001
String conversion	0.0000	0.0017	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
1	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
2	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	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: 6 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs