Limiting one Content item per Member in a Folder on Plone 4

Question

I have created a custom Archetypes content type called "Résumé" and would like to enforce a limitation that lets a Member add only one item of this type inside a folder. Even better would be redirecting the member to the edit page of his or her item, if it already exists in that folder.

How can I enforce this limitation and provide this extra functionality?

I posted my solution here: http://pastie.org/1856465 based on the suggestions of zupo. — Rigel Di Scala, May 02 '11 at 12:31

zupo · Accepted Answer · 2011-04-30T13:02:38.310

5

A solution to a similar usecase for Plone 3 can be found in the eestec.base. We did it by overriding the createObject.cpy and adding a special check for this.

Code is in the collective SVN, at http://dev.plone.org/collective/browser/eestec.base/trunk/eestec/base/skins/eestec_base_templates/createObject.cpy, lines 20-32.

edited Apr 30 '11 at 13:02

answered Apr 29 '11 at 14:21

zupo

1,556
1
13
17

Thanks. That's exactly what I was looking for, i.e. a hook that does a check before the content creation part, and redirects the user to the relative edit view if it already exists. – Rigel Di Scala May 02 '11 at 10:34

score 2 · Answer 2 · answered Apr 30 '11 at 18:11

Well, it is a sort of validation constraint, so maybe add a validator to the title field that in reality does not bother about the title, but checks the user etc.? (I think a field validator is passed enough information to pull this off, if not, overriding the post_validate method or listening to the corresponding event should work.)

If you try this, bear in mind that post_validate is already called while the user is editing (ie on moving focus out of a field).

score 1 · Answer 3 · answered Apr 29 '11 at 15:39

I dont't know if it's best practice, but you can hook up on def at_post_create_script from base object on creation and manage_beforeDelete on delete.

for example:

from Products.ATContentTypes.lib import constraintypes

class YourContentype(folder.ATFolder)
[...]

    def at_post_create(self):
        origin = aq_parent(aq_inner(self))
        origin.setConstrainTypesMode(constraintypes.ENABLED)  # enable constrain types
        org_types = origin.getLocallyAllowedTypes()           # returns an immutable tuple
        new_types = [x for x in org_types if x! = self.portal_type]       # filter tuple into a list
        origin.setLocallyAllowedTypes(new_types)

    def manage_beforeDelete(self, item, container)          
        BaseObject.manage_beforeDelete(self, item, container)     # from baseObject
        self._v_cp_refs = None                                    # from baseObject
        origin = aq_parent(aq_inner(self))
        origin.setConstrainTypesMode(constraintypes.ENABLED)  # enable constrain types
        org_types = origin.getLocallyAllowedTypes()           # returns an immutable tuple
        new_types = [x for x in org_types].append(self.portal_type)
        origin.setLocallyAllowedTypes(new_types)

Note: There is also a method called setImmediatelyAddableTypes(), which you may want to explore. Note II: This does not survive content migration.

This would restrict it to one object of this type in total instead of one object of this type per user. — maurits, Apr 29 '11 at 23:52

Limiting one Content item per Member in a Folder on Plone 4

3 Answers3