Chris McDonough wrote:
> >> and should be fixed in Zope 2.8, 2.9 and trunk.
> >
> > We'd be changing Zope 2's behaviour (not fixing a Five bug), I would
> > therefore vote for making this change on the Zope 2 trunk only.
> I'd be apt to not further restrict the set of identifiers an OFS content
> object can begin with as long as we can get away with it.  If a user
> happens to enter one that starts with a "view character", I suspect a
> developer could just choose to not allow this in at the application level
> if he cared (e.g. if he were using Five).  It might be reasonable to add
> this to CMF instead of Zope, but  IMO, it's a bad idea to put theis
> particular restriction in either place, as it will almost certainly break
> somebody.

Yup. That's why we should do this change on the trunk IF at all.

Note that even in Zope 3 the suggested behaviour is only the default and can be
changed. Custom name chooser adapters may decide whether names are good or not
based on whatever rule. Therefore, if we introduce this restriction, it should
be pluggable like in Zope 3.

Here's what we could do: We factor the name validation part in ObjectManager
(which is _checkId) out to a namechooser adapter. Five already has one in
Five.browser.adding. Then, we can also provide an optional namechooser adapter
that enforces the additional restrictions. People could decide to use this for
their folder implementation, e.g. the CMF might want to do it for their


This message was sent using IMP, the Internet Messaging Program.
Zope-Dev maillist  -
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to