|
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
|