Extending the Usertable

Next topic

Author	Message
John Moritz	Saturday 05 April 2008 8:47:23 am I am planing to migrate my Community which is administrated with phpmyadmin to ezPublish. My existing Community is something like a social network. User can tell something about their life like Birthday, Favorite books or movies... At the Moment the Basic Informations are in one Usertable, together with Password and Nick, and extra Information in an extra Table wich is referenced by the UserID. When i migrate to ezPublish how should i do this. Extend the existing "ezuser" Table manualy, and make 2 extra tables with further informations? Maybe i overlooked something and there are some built in Tools to extend the Usertable. In the past i worked with a Bulletin Board called Invision Power Board. On this BB i could extend the Useriniformations over the Admin Backend. Never needed phpmyadmin or somoething else, no handcoding. The user then had more options in their Profile and me as admin had the possibility to change the Details in the Backend. I am sure i could do it my way and code everything by hand, but if there is a solution out there it would be helpful to get those Informations.
Carlos Revillo	Saturday 05 April 2008 10:10:24 am well, i think you don't need make any changes to that ezuser table. i mean, you can add attributes to the user class through the admin interface. so, these new attributes (birthday date, favourite movies and so on) will be part of the data_map of the object for the users, along with firstname, picture and so on. favourite movies could be a relation objects to other type of objects, for example. Maybe this contrib http://ez.no/developer/contribs/import_export/user_creator could help you with your work.
John Moritz	Monday 07 April 2008 8:39:46 am Thanks Carlos, this was exactly what i am searchin for. Just added attributes to my Users, perfect!

Author

Message

Saturday 05 April 2008 8:47:23 am

I am planing to migrate my Community which is administrated with phpmyadmin to ezPublish. My existing Community is something like a social network. User can tell something about their life like Birthday, Favorite books or movies... At the Moment the Basic Informations are in one Usertable, together with Password and Nick, and extra Information in an extra Table wich is referenced by the UserID.

When i migrate to ezPublish how should i do this. Extend the existing "ezuser" Table manualy, and make 2 extra tables with further informations? Maybe i overlooked something and there are some built in Tools to extend the Usertable. In the past i worked with a Bulletin Board called Invision Power Board. On this BB i could extend the Useriniformations over the Admin Backend. Never needed phpmyadmin or somoething else, no handcoding. The user then had more options in their Profile and me as admin had the possibility to change the Details in the Backend.

I am sure i could do it my way and code everything by hand, but if there is a solution out there it would be helpful to get those Informations.

Carlos Revillo

Saturday 05 April 2008 10:10:24 am

well, i think you don't need make any changes to that ezuser table. i mean, you can add attributes to the user class through the admin interface. so, these new attributes (birthday date, favourite movies and so on) will be part of the data_map of the object for the users, along with firstname, picture and so on.

favourite movies could be a relation objects to other type of objects, for example.

Maybe this contrib
http://ez.no/developer/contribs/import_export/user_creator
could help you with your work.

John Moritz

Monday 07 April 2008 8:39:46 am

Thanks Carlos, this was exactly what i am searchin for. Just added attributes to my Users, perfect!

eZ debug

Timing:	Jan 18 2025 19:22:35
Script start
Timing:	Jan 18 2025 19:22:35
Module start 'layout'
Timing:	Jan 18 2025 19:22:35
Module start 'content'
Timing:	Jan 18 2025 19:22:36
Module end 'content'
Timing:	Jan 18 2025 19:22:36
Script end

Main resources:

Total runtime	0.7765 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.0058	587.9063	152.6250
Module start 'layout'	0.0058	0.0033	740.5313	39.4453
Module start 'content'	0.0092	0.7656	779.9766	469.3516
Module end 'content'	0.7748	0.0017	1,249.3281	8.1719
Script end	0.7764		1,257.5000

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.4566	16	0.0002
Check MTime	0.0015	0.1886	16	0.0001
Mysql Total
Database connection	0.0010	0.1231	1	0.0010
Mysqli_queries	0.7280	93.7541	57	0.0128
Looping result	0.0008	0.0975	55	0.0000
Template Total	0.7440	95.8	2	0.3720
Template load	0.0020	0.2632	2	0.0010
Template processing	0.7420	95.5570	2	0.3710
Template load and register function	0.0004	0.0461	1	0.0004
states
state_id_array	0.0014	0.1801	1	0.0014
state_identifier_array	0.0011	0.1361	2	0.0005
Override
Cache load	0.0017	0.2148	14	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0015	0.1926	2	0.0007
Fetch class attribute name	0.0019	0.2511	3	0.0006
XML
Image XML parsing	0.0002	0.0295	2	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0010	3	0.0000
General
dbfile	0.0007	0.0863	10	0.0001
String conversion	0.0000	0.0010	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/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	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: 10 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs