Previously Hanno Schlichting wrote:
> Jens Vagelpohl wrote:
> > My checkins today addressed at least the second change set you list by
> > making the site itself a utility and looking it up that way. The
> > additional wrapping is gone as well.
>
> I tested the branch again against the current Plo
Hi,
Jens Vagelpohl wrote:
> My checkins today addressed at least the second change set you list by
> making the site itself a utility and looking it up that way. The
> additional wrapping is gone as well.
I tested the branch again against the current Plone trunk and found no
branch related proble
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1 Mar 2007, at 17:36, yuppie wrote:
BTW: While fixing the tests a month ago I made two quick and dirty
changes, adding some XXX comments:
- in SkinnableObjectManager http://svn.zope.org/?view=rev&rev=72251
- in PropertiesTool http://svn.zope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1 Mar 2007, at 17:36, yuppie wrote:
Jens Vagelpohl wrote:
On 28 Feb 2007, at 15:14, Rocky wrote:
Now that I have completed the primary functionality for
five.localsitemanager it seems to me that the CMF
jens_tools_as_utilities branch should be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2 Mar 2007, at 13:01, Jens Vagelpohl wrote:
I can't seem to replicate this in a script. Changing the import
context to "CMFDefault:default" does not seem to update the
available import steps - however, using the ZMI and the
"Properties" tab
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2 Mar 2007, at 13:36, yuppie wrote:
I can't seem to replicate this in a script. Changing the import
context to "CMFDefault:default" does not seem to update the
available import steps - however, using the ZMI and the
"Properties" tab on the
Jens Vagelpohl wrote:
I'm working on the second step, trying to effect the component
registration, and keep running into a strange problem. Using the ZMI, I
can get a CMF site created in CMF 1.6 to a functioning state using the
setup tool and executing the following steps + dependencies:
- -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1 Mar 2007, at 17:36, yuppie wrote:
It's ready for merging when we have a story for existing sites,
meaning a clear migration path. I was going to do some simple
testing closer to this weekend (busy until then) and do a simple
script that ca
Sidnei da Silva wrote:
That BeforeTraverseEvent should be fired by ZPublisher/BaseRequest.py,
after it looks up __before_publishing_traverse__ but before calling it
I believe. Firing it from inside CMF doesn't make sense.
Yes, the ZPublisher should be firing it. But it doesn't. While it's
clea
Sidnei da Silva wrote:
That BeforeTraverseEvent should be fired by ZPublisher/BaseRequest.py,
after it looks up __before_publishing_traverse__ but before calling it
I believe. Firing it from inside CMF doesn't make sense.
That might be right, I'm not familiar with the details. But Zope 2.10
do
That BeforeTraverseEvent should be fired by ZPublisher/BaseRequest.py,
after it looks up __before_publishing_traverse__ but before calling it
I believe. Firing it from inside CMF doesn't make sense.
--
Sidnei da Silva
Enfold Systemshttp://enfoldsystems.com
Fax +1 832 201 8856
Hi Jens!
Jens Vagelpohl wrote:
On 28 Feb 2007, at 15:14, Rocky wrote:
Now that I have completed the primary functionality for
five.localsitemanager it seems to me that the CMF
jens_tools_as_utilities branch should be ready for merging into trunk
in anticipation of the of the next cmf 2.1 alp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rocky wrote:
> On Feb 28, 12:15 pm, Tres Seaver <[EMAIL PROTECTED]> wrote:
>> On that note, I would *greatly* appreciate it if you (Rocky) would
>> promise not to move the SVN tag for LSM after this point: the
>> possibility of chasing down reports wh
On Feb 28, 12:15 pm, Tres Seaver <[EMAIL PROTECTED]> wrote:
> On that note, I would *greatly* appreciate it if you (Rocky) would
> promise not to move the SVN tag for LSM after this point: the
> possibility of chasing down reports which can't be replicated due to
> having the same tag point at dif
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rocky wrote:
> Now that I have completed the primary functionality for
> five.localsitemanager it seems to me that the CMF
> jens_tools_as_utilities branch should be ready for merging into trunk
> in anticipation of the of the next cmf 2.1 alpha/beta
15 matches
Mail list logo
