HowTo profile page?

Next topic

Author	Message
Vathanan Kumarathurai	Friday 01 December 2006 6:29:21 pm I am developing a website where every registered user will have a profile page, something like profile pages at livejournal.com, eg. http://burr86.livejournal.com/profile The URL should be more like: /member/<username>/ URL to the list of articles by the user: /member/<username>/articles/ URL to the list of blogs by the user: /member/<username>/blogs/ And maybe even the actual content should be placed under the profile page, like /member/<username>/articles/<articleName> /member/<username>/blogs/<blogName> How do I implement something like this? Do I have to implement a member extension? Or can this be solved by making proper content structure? Or is there some other way? Please help :) /vathanan "Ninety percent of everything is crap" ~Sturgeon's law
Claudia Kosny	Saturday 02 December 2006 3:18:00 am Hi No need for writing an extension. I would create a main folder members, and in there a personal folder for each user (check Lukasz's custom edit handler). Create the appropiate subfolders and give your user permissions to create articles in the folder articles in their subtree, same for blogs. That should be it. Claudia
Vathanan Kumarathurai	Saturday 02 December 2006 4:33:52 am Claudia, thank you for your input. My plan was to 1. Create a new class 'member' as a container <i>I think I also need to make custom classes for user articles, user blogs, etc. These classes will make it easy to override the templates.</i> 2. Create a instance of 'member' class for every user created, with the user's login as the name of the object, and create the sub folders articles, blogs, etc using the appropriate custom classes. The owner of the containers are set to the user created. The creation of containers are done using custom edit handler <i>This will give me /member/<login>/, /member/<login>/articles, /member/<login>/blogs, etc</i> 3. Create template overrides using class matching 4. Customize the look of the templates using class name and owner id of the node <i>This makes it possible to personalize the look of the profile page and the sub folders with content specific attributes and profile information</i> Is it the way to do it? My concern is the high number of containers that will have to be created. If you have 1000 users and six different content types, you will have 7000 containers/folders. Am I on the right track? Or should I consider an other approach? /vathanan "Ninety percent of everything is crap" ~Sturgeon's law
Claudia Kosny	Saturday 02 December 2006 10:50:23 am Hi this sounds good to me. I would not know right now how to do the customizing of the templates for each user, although on second thought maybe one could use the user preferences to set display certain items (or not) and to set a certain theme. If you come up with an interesting solution maybe you could post it here or on http://ezpedia.org/ There is not much you can do about the number of objects. You need at least one for each user, each article and (I think) each blog entry. Having an additional folder for each content type does not add much to these numbers but gives you a much better structure on the website. Having these folders should actually help a bit as EZ creates a cache file for each object so if you have lots of objects in the same folder, listing these objects will cause a (admittedly only slight) slowdown. Claudia
Vathanan Kumarathurai	Tuesday 05 December 2006 3:10:44 am Claudia, Sure. I will make the solution available to the ez community. /vathanan "Ninety percent of everything is crap" ~Sturgeon's law
Bjarte Lunde	Saturday 05 January 2008 12:57:02 pm Any luck with this?

eZ debug

Timing:	Jan 18 2025 18:22:13
Script start
Timing:	Jan 18 2025 18:22:13
Module start 'layout'
Timing:	Jan 18 2025 18:22:13
Module start 'content'
Timing:	Jan 18 2025 18:22:14
Module end 'content'
Timing:	Jan 18 2025 18:22:14
Script end

Main resources:

Total runtime	0.9727 sec
Peak memory usage	4,096.0000 KB
Database Queries	68

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0047	589.0234	152.6094
Module start 'layout'	0.0047	0.0025	741.6328	39.4141
Module start 'content'	0.0072	0.9639	781.0469	609.0781
Module end 'content'	0.9711	0.0015	1,390.1250	16.1875
Script end	0.9726		1,406.3125

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.3246	16	0.0002
Check MTime	0.0013	0.1340	16	0.0001
Mysql Total
Database connection	0.0008	0.0827	1	0.0008
Mysqli_queries	0.9058	93.1208	68	0.0133
Looping result	0.0007	0.0681	66	0.0000
Template Total	0.9450	97.1	2	0.4725
Template load	0.0022	0.2302	2	0.0011
Template processing	0.9427	96.9182	2	0.4713
Template load and register function	0.0004	0.0454	1	0.0004
states
state_id_array	0.0011	0.1135	1	0.0011
state_identifier_array	0.0007	0.0734	2	0.0004
Override
Cache load	0.0020	0.2012	45	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0644	3	0.0002
Fetch class attribute name	0.0012	0.1258	7	0.0002
XML
Image XML parsing	0.0008	0.0818	3	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0022	9	0.0000
General
dbfile	0.0008	0.0871	16	0.0001
String conversion	0.0000	0.0006	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
6	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
11	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
5	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: 27 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs