By scoorch on

I have created a new Content Typ with the CCK Module. I want each user to create only ONE item of such Content Type. (in database language a 1:1 relationship between User and the Content Type)
After a user has created one item of the new Content the user shall only be able to edit or delete such item.

I am a newbie to Drupal but have quite some good database PHP experience.

Any ideas how one could easiy arrange this?

Thanks Thomas

⋅ Categories: Drupal 5.x

Comments

paulnem’s picture

paulnem commented

The Node Family module will allow you to set a maximum, per content type that a user can create.

http://drupal.org/project/nodefamily

Passionate_Lass’s picture

Passionate_Lass commented

Hi.

That's cool unfortunately they don't have a D6 version for me.

CarbonPig’s picture

CarbonPig commented

Any ideas?

Where users can only create one of a given content type?

sproot’s picture

sproot commented

There's node limit which promises it will do so in the future sometime, and some code here if you're that way inclined.
There seem to be number of solutions for D5, but D6 isn't getting the love :(

EDIT: Actually, the rules module looks like it might be able to achieve this, and it's written by fago who was responsible for node family, so I'm hopeful :)

grobemo’s picture

grobemo commented

Those looking for a D6 solution might consider adapting the Content Profile module to do what you want? Even if you're not technically asking them to create a profile, the module might meet your needs.

sproot’s picture

sproot commented

I've just quickly tested it and it does restrict users to creating only one node of a given content type, if that content type is marked as a content profile.

I don't see though, what it's actually for. Marking a content type as a profile doesn't appear to change the profile page for a user (although I didn't create a new user to test this). It's also possible to mark two content types as profiles concurrently, which seems to be counterintuitive to me, since I thought the point was to make a particular content type replace the default profile.

Still, it does what I want, so thanks :)

WorldFallz’s picture

WorldFallz commented

It does pretty much what the project page says it does-- turns user profiles into first class nodes (which the core profile module doesn't create). It does affect the /user page as well as integrates with the user registration process. People use multiple content types as content_profiles in order to have different types of profiles for different types of users. Integrates nicely with the autoassignrole module to enable users to choose which 'type' of user they will be.

Though it does what you want, it's not really designed for that purpose. I use user_quota for that though node_limit looks more flexibl.

caschbre’s picture

caschbre commented

I actually use the Unique Field module. You can specific what needs to be unique. In this particular case you would say that the author has to be unique. You can also select to measure uniqueness by content type.

WorldFallz’s picture

WorldFallz commented

i hadn't thought of that way-- clever!