Memento

Author Message

Monica Giambitto

Thursday 02 December 2010 3:20:41 am

Ok, it's been a while I try to understand in a deep way how ez execute and how workflows enter the game.

I've tracked down the execution of a module deep down to a single event and back and, here and there, I found references to this "memento" thing. As far as I can see, and due to the fact "memento" means something to remember, I think it's ez way to keep track of the steps of execution. Is there anywhere something that describe better the memento mechanism? Or someone that can explain it?

Thanks a lot.

Franck Grenier

Friday 03 December 2010 5:09:10 am

Hello,

I'm also trying to understand "memento".

"Memento" are linked to workflow processes by the "memento_key".They are created by the eZModuleOperationInfo class. For one process, there is a main memento and a child memento.

All of my processes do not have a memento. So I do not understand when they are generated and what they are made for.

Need help.

Developer at Open Wide

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 18 2025 02:55:56
Script start
Timing: Jan 18 2025 02:55:56
Module start 'layout'
Timing: Jan 18 2025 02:55:56
Module start 'content'
Timing: Jan 18 2025 02:55:56
Module end 'content'
Timing: Jan 18 2025 02:55:56
Script end

Main resources:

Total runtime0.6043 sec
Peak memory usage4,096.0000 KB
Database Queries54

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0044 588.8906152.5938
Module start 'layout' 0.00440.0019 741.484439.3828
Module start 'content' 0.00630.5966 780.8672485.3438
Module end 'content' 0.60290.0013 1,266.21098.2188
Script end 0.6042  1,274.4297 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00300.4890160.0002
Check MTime0.00130.2103160.0001
Mysql Total
Database connection0.00070.112510.0007
Mysqli_queries0.567993.9824540.0105
Looping result0.00040.0702520.0000
Template Total0.581996.320.2910
Template load0.00230.382920.0012
Template processing0.579695.914820.2898
Template load and register function0.00020.039110.0002
states
state_id_array0.00080.133710.0008
state_identifier_array0.00060.101020.0003
Override
Cache load0.00190.3128130.0001
Sytem overhead
Fetch class attribute can translate value0.00040.073220.0002
Fetch class attribute name0.00090.145820.0004
XML
Image XML parsing0.00020.039720.0001
class_abstraction
Instantiating content class attribute0.00000.001020.0000
General
dbfile0.00110.1840100.0001
String conversion0.00000.000840.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1node/view/full.tplfull/forum_topic.tplextension/sevenx/design/simple/override/templates/full/forum_topic.tplEdit templateOverride template
2content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
3content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
1content/datatype/view/ezxmltags/strong.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/strong.tplEdit templateOverride template
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 8
 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs