collective.customizablePersonalizeForm 2.0

Simple Override Example

A simple interface providing our field:

class ITestAdditionalDataSchema(Interface):

test_field = schema.Bool(

title=_(u’label_test_field_title’, default=u’Test field’), description=_(u’label_test_field_description’, default=u’’), required=False, )

A simple adapter that adapts the context and request, returning our interface

class TestSchemaAdapter(object):

adapts(object, IBrowserRequest) implements(IExtendedUserDataSchema)

def __init__(self, context, request):

self.context = context self.request = request

def getSchema(self):

return ITestAdditionalDataSchema

Now we create an adapter that will declare a ‘test_field’ property, we didn’t specify a getter and setter so this property will act as a memberdata property (be sure to declare it via memberdata_properties.xml)

class TestPropertiesAdapter(object):

adapts(object, IBrowserRequest) implements(IExtendedUserDataPanel)

def __init__(self, context, request):

self.context = context self.request = request

def getProperties(self):

return [‘test_field’]

Let’s susbscribe to the collective.customizablePersonalizeForm’s interfaces to provide the personal-information form with our field

<adapter factory=”.adapters.TestSchemaAdapter”

name=”test.ExtraField”/>

<adapter factory=”.adapters.TestPropertiesAdapter”

name=”test.ExtraProperties”/>

Congratulations, a simple boolean field named ‘test_field’ should now be displayed in your form.

Custom Widgets

You may want to use a widget for your field. It can be done through the IExtendedUserDataWidgets interface. All you have to do is mapping a field id with a valid custom_widget factory like the following example.

class TestWidgetAdapter(object):

adapts(object, IBrowserRequest) implements(IExtendedUserDataWidgets)

def __init__(self, context, request):

self.context = context self.request = request

def getWidgets(self):

return [{‘field’: ‘test_field’, ‘factory’CheckBoxWidget},

]

<adapter factory=”.adapters.TestWidgetAdapter”

name=”test.ExtraWidgets”/>

Your test_field will now use the widget factory you declared in the getWidgets method. You can also override the default Plone fields widgets using this method if you ever need to.

2.0 (2011-09-07)

• Now working for Plone 4.x [jstegle]

• Added 3 interfaces for subscription, provider schema, properties and widgets overrides [jstegle]

• Overrides the default personal-information to manage widget customization [jstegle]

• Overrides the default IUserDataSchemaProvider [jstegle]

• Overrides the account-macro view to manage FileUpload fields that handles pictures [jstegle]

• Added isImage constraint on the portrait field, allowing only images to be uploaded [jstegle]

• Added tests and examples [jstegle]

1.0.1 (2011-05-04)

• Added documentation [jstegle]

1.0 (2011-04-XX)

• Added viewletmanager for the personalize_form [jstegle]

• Added adaptor interfaces for validators and actions [jstegle]

• Added self personalize_form, validation and action scripts [jstegle]

• Works for Plone 3.x [jstegle]