Monday 04 October 2004 4:37:04 am

This sounds like a bit of a mess to me since you want to both create new users when they create this class of yours together with the ability to identify the creator of the object by adding fields to this class. I think you should stick to one of the methods.
Whichever method you go for you'll have to write some PHP code. If you want users to be generated automatically you'll have to detect in the content module that this is happening and generating the user on the fly. If you want to check user id by fields in the class you'll have to write the code that does the actual comparisment.
I don't really like the idea of mixing any of these solutions into the content module though.
Maybe you are better of with a really simple user creation form which you display within your class template?

Tuesday 05 October 2004 12:03:48 am

Hi Frederik and Eirik, thanks so much for your replies!

Frederik, I agree with you, it does sound a bit like a mess, but as Eirik indicates, some kind functionality which allows this might be usefull for a number of people.

I have though of another possible solution(actually more of a "cheat"):

Some background: Currently the user enters the data for the entry in Steps at the moment, since he/she must first pick a region, then a category(Steps 1 and 2) which I then use to identify where the new instance of the class is to be created in the node tree.

I am going to try and "sneak" a login page in there(under Step 3), so the user just sees it as another step in the process of adding his/her listing, without "having to log in". Step 4 will then be the actual data entry to create the new instance of the class. Thus a "logged in" user will be creating the instance, with all the benefits as standard with eZP.

This does not really solve the problem, but "hides" it, so the user doesn't feel he has to log into the site before he can do anything, but it now forms part of the process of adding his listing.

I now have to go and test it to see if I can "sneak" the login page into the procedure. I guess I will have to chop out some stuff(as not to confuse the user) and switch off e-mail response verification, since I can't then first ask the user to respond to an e-mail before continuing with step 4.

Can the sub be registered and confirmed "in the background" without further action from the user, after submitting the "stealth" :-) login form?(Note to self - test this!)

I would like to work on a more elegant solution, but due to some time constraints will have to put it on my "to do" list for now :-)

Thanks again for any inputs :-)