[Zope-CMF] Re: [dev] characters allowed in content IDs

2006-03-22 Thread Dieter Maurer
yuppie wrote at 2006-3-21 21:12 +0100: There was a clear result: make the id checker policy configurable -- as Zope 3 does. Well. That's right but doesn't help us much. We don't have a volunteer for implementing that new feature. And we don't have a consensus what the default policy should

[Zope-CMF] Re: [dev] characters allowed in content IDs

2006-03-21 Thread yuppie
Hi Dieter! Dieter Maurer wrote: yuppie wrote at 2006-3-20 18:17 +0100: ... But I gave up my attempt to fix this in the Zope layer because the related discussion on zope-dev ended without a clear result. There was a clear result: make the id checker policy configurable -- as Zope 3 does.

[Zope-CMF] Re: [dev] characters allowed in content IDs

2006-03-20 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yuppie wrote: Hi! CMF 2.0 will ship with some browser views. Browser views have their own prefix '@@' to avoid conflicts with content IDs. But Zope 2 doesn't reserve those names for views as Zope 3 does by default. I propose to disallow names

[Zope-CMF] Re: [dev] characters allowed in content IDs

2006-03-20 Thread yuppie
Hi Tres! Tres Seaver wrote: yuppie wrote: CMF 2.0 will ship with some browser views. Browser views have their own prefix '@@' to avoid conflicts with content IDs. But Zope 2 doesn't reserve those names for views as Zope 3 does by default. I propose to disallow names starting with '@' as the