User account's login for object name pattern

Next topic

Author	Message
Piotrek Karaś	Thursday 03 January 2008 4:40:48 am <b>Is it possible to use user account's login to define object name pattern?</b> I mean, is there a system way, any special notation for the object name pattern? Generally the goal is to force object names to be based on user logins. We've just experimented a bit with user class and when you <b>remove first name</b> and <b>last name</b> (or at least place user account as the first attribute in the class) as well as <b>get rid of object name pattern declaration</b>, then the systems magically follows the "first attribute" rule and out of all fields (login, passwords, e-mail) <b>takes login</b> to build object name. The question remains: how intensional is that behavior? Should we rely on it, or is it likely to alter in the future versions (of eZ4)? The other issue is security. Do you think revealing user login to the public increases risks in this context? -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
Maxime Thomas	Monday 07 January 2008 8:54:38 am I guess it's the same if you get only one attribute with a file or a picture, you wannot have a name. Maxime Thomas maxime.thomas@wascou.org \| www.wascou.org \| http://twitter.com/wascou Company Blog : http://www.wascou.org/eng/Company/Blog Technical Blog : http://share.ez.no/blogs/maxime-thomas
Piotrek Karaś	Monday 07 January 2008 9:21:42 am Seems like you're right, same situation. But in case of user account datatype it is login is chosen for object name generation. I would like to know if that will be a consistent behavior in the next eZ versions. -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu

Author

Message

Thursday 03 January 2008 4:40:48 am

Is it possible to use user account's login to define object name pattern? I mean, is there a system way, any special notation for the object name pattern?

Generally the goal is to force object names to be based on user logins. We've just experimented a bit with user class and when you remove first name and last name (or at least place user account as the first attribute in the class) as well as get rid of object name pattern declaration, then the systems magically follows the "first attribute" rule and out of all fields (login, passwords, e-mail) takes login to build object name. The question remains: how intensional is that behavior? Should we rely on it, or is it likely to alter in the future versions (of eZ4)?

The other issue is security. Do you think revealing user login to the public increases risks in this context?

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

Maxime Thomas

Monday 07 January 2008 8:54:38 am

I guess it's the same if you get only one attribute with a file or a picture, you wannot have a name.

Maxime Thomas
maxime.thomas@wascou.org | www.wascou.org | http://twitter.com/wascou

Company Blog : http://www.wascou.org/eng/Company/Blog
Technical Blog : http://share.ez.no/blogs/maxime-thomas

Piotrek Karaś

Monday 07 January 2008 9:21:42 am

Seems like you're right, same situation. But in case of user account datatype it is login is chosen for object name generation. I would like to know if that will be a consistent behavior in the next eZ versions.

eZ debug

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

Main resources:

Total runtime	0.7431 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.0078	588.0469	152.6406
Module start 'layout'	0.0078	0.0038	740.6875	39.4766
Module start 'content'	0.0116	0.7302	780.1641	547.5313
Module end 'content'	0.7417	0.0013	1,327.6953	12.1250
Script end	0.7430		1,339.8203

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0043	0.5722	16	0.0003
Check MTime	0.0020	0.2628	16	0.0001
Mysql Total
Database connection	0.0027	0.3671	1	0.0027
Mysqli_queries	0.6897	92.8156	57	0.0121
Looping result	0.0005	0.0613	55	0.0000
Template Total	0.7075	95.2	2	0.3537
Template load	0.0039	0.5212	2	0.0019
Template processing	0.7036	94.6882	2	0.3518
Template load and register function	0.0001	0.0136	1	0.0001
states
state_id_array	0.0013	0.1795	1	0.0013
state_identifier_array	0.0007	0.0986	2	0.0004
Override
Cache load	0.0035	0.4672	13	0.0003
Sytem overhead
Fetch class attribute can translate value	0.0004	0.0547	2	0.0002
Fetch class attribute name	0.0013	0.1766	5	0.0003
XML
Image XML parsing	0.0009	0.1206	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0018	6	0.0000
General
dbfile	0.0008	0.1139	23	0.0000
String conversion	0.0000	0.0014	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
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 11 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs