Creation context vs Edition context

Previous topic

Setup & design

Next topic

Author	Message
Hakim Bouras	Friday 14 December 2007 8:12:47 am Hello, I would like to use the same custom "user edit template" both for the creation and the edition of my users. From within this "user edit template" how can I detect whether I am in an edition or creation context mode ? I tried using <i>$object.current.main_parent_node_id</i>, but the problem is if there is a validation round trip (ie: the email entered was not correct) then <i>$object.current.main_parent_node_id</i> is set ... (Maybe using the URL : user/register vs content/edit ... but how can I check the URL ? maybe there is a smarter way... ) Thank you for your help, Hakim
Hakim Bouras	Monday 17 December 2007 2:29:45 am The solution I found is checking <b>$object.current.status</b> which has a value of "5" ("EZ_VERSION_STATUS_INTERNAL_DRAFT") during the creation context as long as the new user is not really created (even during validation round-trip).

Author

Message

Hakim Bouras

Friday 14 December 2007 8:12:47 am

Hello,

I would like to use the same custom "user edit template" both for the creation and the edition of my users.

From within this "user edit template" how can I detect whether I am in an edition or creation context mode ?

I tried using $object.current.main_parent_node_id, but the problem is if there is a validation round trip (ie: the email entered was not correct) then $object.current.main_parent_node_id is set ...

(Maybe using the URL : user/register vs content/edit ... but how can I check the URL ? maybe there is a smarter way... )

Thank you for your help,
Hakim

Hakim Bouras

Monday 17 December 2007 2:29:45 am

The solution I found is checking $object.current.status which has a value of "5" ("EZ_VERSION_STATUS_INTERNAL_DRAFT") during the creation context as long as the new user is not really created (even during validation round-trip).

eZ debug

Timing:	Jan 31 2025 07:26:09
Script start
Timing:	Jan 31 2025 07:26:09
Module start 'layout'
Timing:	Jan 31 2025 07:26:09
Module start 'content'
Timing:	Jan 31 2025 07:26:09
Module end 'content'
Timing:	Jan 31 2025 07:26:09
Script end

Main resources:

Total runtime	0.0291 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0056	588.2500	151.2266
Module start 'layout'	0.0057	0.0031	739.4766	36.6641
Module start 'content'	0.0088	0.0186	776.1406	90.1406
Module end 'content'	0.0273	0.0018	866.2813	29.9922
Script end	0.0291		896.2734

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	8.4598	14	0.0002
Check MTime	0.0011	3.7107	14	0.0001
Mysql Total
Database connection	0.0008	2.7624	1	0.0008
Mysqli_queries	0.0028	9.7264	3	0.0009
Looping result	0.0000	0.0548	1	0.0000
Template Total	0.0012	4.1	1	0.0012
Template load	0.0009	3.0995	1	0.0009
Template processing	0.0003	1.0130	1	0.0003
Override
Cache load	0.0006	2.0930	1	0.0006
General
dbfile	0.0074	25.3711	8	0.0009
String conversion	0.0000	0.0311	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