-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
> On Sun, Dec 27, 2009 at 8:31 PM, Jens Vagelpohl wrote:
>> Please keep release scheduling in mind. I had announced a release date
>> for CMF 2.2.0-final about a week from now. Andreas cannot possible throw
>> out Zope 2 2.12.
Summary of messages to the cmf-tests list.
Period Tue Dec 29 12:00:00 2009 UTC to Wed Dec 30 12:00:00 2009 UTC.
There were 4 messages: 4 from CMF Tests.
Tests passed OK
---
Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux
From: CMF Tests
Date: Tue Dec 29 20:56:07 EST 2009
URL: ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm working on a PAS plugin and want to ensure it has GenericSetup
support like the standard plugins. I'm running into issues trying to use
GenericSetup in a manual test, though.
With a setup_tool inside the PluggableAuthService instance I ca
On 2009-12-30 15:06, Jens Vagelpohl wrote:
> Separate note: On the "Import" tab I see a dropdown of extension
> profiles to select. Changing the selection here never affects the list
> of available import steps, though. This is confusing to me, but I may
> have misunderstood the purpose.
The list
On 2009-12-30 15:06, Jens Vagelpohl wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all,
>
> I'm working on a PAS plugin and want to ensure it has GenericSetup
> support like the standard plugins. I'm running into issues trying to use
> GenericSetup in a manual test, though.
>
> Wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
> On 2009-12-30 15:06, Jens Vagelpohl wrote:
>> Separate note: On the "Import" tab I see a dropdown of extension
>> profiles to select. Changing the selection here never affects the list
>> of available import steps, though. Thi
On 2009-12-30 15:35, Jens Vagelpohl wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Wichert Akkerman wrote:
>> On 2009-12-30 15:06, Jens Vagelpohl wrote:
>>> Separate note: On the "Import" tab I see a dropdown of extension
>>> profiles to select. Changing the selection here never affec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
> On 2009-12-30 15:35, Jens Vagelpohl wrote:
>> The reason I thought this list of steps may (should?) change is that for
>> example the PluggableAuthService profiles (both of which are BASE
>> profiles) explicitly define what st
On 2009-12-30 16:19, Jens Vagelpohl wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Wichert Akkerman wrote:
>> On 2009-12-30 15:35, Jens Vagelpohl wrote:
>>> The reason I thought this list of steps may (should?) change is that for
>>> example the PluggableAuthService profiles (both of
On Wed, Dec 30, 2009 at 4:19 PM, Jens Vagelpohl wrote:
> In the debugger I see that the object in question is a absolute_url
> adapter residing in the base component registry in the site root. IMHO
> the components exporter should not look at the base registry at all,
> only a local registry if on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
> On 2009-12-30 16:19, Jens Vagelpohl wrote:
>> However, even that
>> registration by interface for profiles isn't considered in the ZMI in
>> the base profile or extension profile select lists that show up on the
>> Profiles an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
> On Wed, Dec 30, 2009 at 4:19 PM, Jens Vagelpohl wrote:
>> In the debugger I see that the object in question is a absolute_url
>> adapter residing in the base component registry in the site root. IMHO
>> the components export
12 matches
Mail list logo
