Steve, what you are describing does indeed sound like a problem. Using eZ publish classes with 100 attribues is not a good thing, since they system is not designed for this. It's meant to work with a lower number of attributes pr class than this.
If you can split this up into some smaller classes that would be much better. Lets say whenever a user is created you also create objects containing personal information. These could be made empty by default and the users would have permission to edit them. Links to edit them could be provided via the user profile page.
Mabye create a small workflow which automatically creates the needed objects when a user is registered.
Not sure if this is the solution you were looking for?
<i>If you can split this up into some smaller classes that would be much better. Lets say whenever a user is created you also create objects containing personal information. These could be made empty by default and the users would have permission to edit them. Links to edit them could be provided via the user profile page.</i>
This is exactly what we'd like to do.
So the only way to create the empty objects is via a workflow? If so, how does this work - and how do we link them together...? I've seen the 'user account' attribute in the class options.
Essentially, in non-Ez speak ;), how do we achieve the 'inner join' process between the related classes?
workflows is not the only way of doing this. You could alternatively create a module which handled "personal/account information". When you clicked on "edit my personal info A" it creates the object on fly and stores the relation to it.
If you use a workflow you can create the objects on creation of the user but with empty/default values. You can store these classes in a hierarcy like:
/ user accounts/ user John doe / personal settings A
/ user accounts/ user John doe / personal settings B / user accounts/ user John doe / personal settings C
Create the objects under the user account, that way you can dynamically fetch then when you know the user. Create the objects as the user, so you can set permissions on edit by owner.
Bard, Steve, Can anybody of you give us more details and explanation on his won suggested way?
I guess this problem is a very important one. For me, and I guess hte others, I have converted to eZ because I believed, and still believe, I can make proffesional forms using it.
Then please share your experience.
You must be logged in to post messages in this topic!