On Sep 24, 2009, at 14:01 , Charlie Clark wrote:
Am 24.09.2009, 13:52 Uhr, schrieb Andreas Jung li...@zopyx.com:
In my understanding: packages using the Products namespace are
subject
to be registered during the startup phase of Zope (using their
initialize()
method). And I think there is
On Sep 24, 2009, at 15:16 , Maurits van Rees wrote:
Personally, I am the maintainer of Products.Poi. It will take more
than one bottle of whisky to convince me to rename that. ;-)
Personally, I believe most product authors who have a real Zope 2
Product but chose a name other than
On Sep 24, 2009, at 14:17 , Charlie Clark wrote:
Regarding something completely different - I picked up on zope-dev
that
the svn server has been updated. Does this mean that we can now use
the
svn branch to trunk merging offered in svn = 1.5 or is this still
inadvisable? If it is still
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/9/10 22:23 , Charlie Clark wrote:
Am 09.02.2010, 13:46 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
Your event handler handle_new_masterpage should be rewritten to look
if the object it wants to instantiate already exists. If it exists
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/31/10 20:33 , Tres Seaver wrote:
I also don't know why the 'instance' and 'i18n*' parts are configured in
these buildouts -- does somebody have a memory of why, or a reason to
keep them?
The instance part is a pure convenience to quickly fire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/31/10 22:07 , Tres Seaver wrote:
Jens Vagelpohl wrote:
On 3/31/10 20:33 , Tres Seaver wrote:
I also don't know why the 'instance' and 'i18n*' parts are configured in
these buildouts -- does somebody have a memory of why, or a reason to
keep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/1/10 12:10 , yuppie wrote:
IIRC the general policy for the Zope repository is to switch to relative
externals after the release of Ubuntu 10.04 LTS, but I guess all people
using CMF.buildout have already Subversion =1.5 available.
Huh?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/1/10 12:28 , yuppie wrote:
Jens Vagelpohl wrote:
On 4/1/10 12:10 , yuppie wrote:
IIRC the general policy for the Zope repository is to switch to relative
externals after the release of Ubuntu 10.04 LTS, but I guess all people
using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/7/10 13:09 , Charlie Clark wrote:
Hi,
I'm currently working on a project which will hopefully have no TTW code
so I was hoping to be do without skins - currently I have a my skin on top
of CMFDefault but it is just main_template and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/10 10:54 , Charlie Clark wrote:
That warning should not show up for type-specific Actions. They are not
deprecated. This is a bug.
I'll remove it from editToolsActions.dtml then. Can we backport this to
CMF 2.2?
Sure.
In my work on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/10 11:09 , Charlie Clark wrote:
Am 09.04.2010, 10:58 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
I'll remove it from editToolsActions.dtml then. Can we backport this to
CMF 2.2?
Sure.
Committed to trunk. For 2.2 do I just make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/10 13:29 , Charlie Clark wrote:
Any idea why CookieCrumbler is a Folder?
They can contain objects that can be used as login/logout pages, such as
DTML methods or Page Templates.
Needless to say, this is more useful when using a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/14/10 15:43 , Charlie Clark wrote:
Am 09.04.2010, 13:38 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
Needless to say, this is more useful when using a CookieCrumbler as a
standalone object without a portal. The CMF does not need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/26/10 14:05 , Hanno Schlichting wrote:
This looks like its caused by Jens cleanup in Zope2:
Error in test test_manage_propertiesForm_allows_adding
(Products.CMFCore.tests.test_ActionInformation.ActionTests)
Traceback (most recent call
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/4/10 13:46 , Hanno Schlichting wrote:
On Sun, Jul 4, 2010 at 11:30 AM, Jens Vagelpohl j...@dataflake.org wrote:
As you may have seen from the checkins, I have done a CMF 2.2 point
release. Hanno said this would help Plone 4 testing.
Thanks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Subject: FAILED (failures=15) : CMF-2.2 Zope-2.12 Python-2.6.5 : Linux
From: CMF Tests
Date: Thu Jul 29 21:57:59 EDT 2010
URL: http://mail.zope.org/pipermail/cmf-tests/2010-July/013347.html
Subject: FAILED (failures=15) : CMF-trunk Zope-2.12
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/5/10 16:52 , yuppie wrote:
Charlie Clark wrote:
I'm actively abstaining as while I understand the need to clean things up,
I'm not sure I understand the whole context (my lack of understanding
rather than any lack of explanation). CMF is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/22/10 20:49 , Charlie Clark wrote:
Am 22.09.2010, 14:31 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
Are there any outstanding issues or blockers that need resolving or can
I go ahead and publish the new releases?
While I'd like my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/23/10 11:39 , Charlie Clark wrote:
Hi,
Yuppie brought this up at the Dresden Sprint: does anyone have any
objections to removing the ursa and werebear skins in 2.3? Both are
just examples of using a BrowserView for the tool lookups and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/23/10 11:36 , Charlie Clark wrote:
Am 23.09.2010, 10:40 Uhr, schrieb yuppie y.2...@wcm-solutions.de:
Are you sure you want to make these changes in CMF 2.1? Jens is not
talking about CMF 2.2 or trunk.
Oh, yeah. Sorry, so caught up in 2.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/23/10 12:38 , yuppie wrote:
My goal is to have *one* branch for each CMF version. (Except of CMF
2.1, which has also a non-buildout branch.) I think we have always a
primary target platform that is used for development (e.g. Zope trunk
for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Charlie,
enable_permalink. Now, while this is easy enough to add both to the
Script and my view and there is support for this in
zpt_generic/main_template with get_permalink, there is actually an
implicit dependency about CMFUid for this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/30/10 23:54 , Charlie Clark wrote:
I propose to add Site Syndication Settings to the actions/global and
remove the Properties form from the SyndicationTool. I also think that
synPropertiesForm should be moved to actions/folder and the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/12/10 20:45 , Charlie Clark wrote:
Am 23.09.2010, 12:47 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
Let's talk about 2.2 releases after the bug day then.
Hi Jens,
I'd like a 2.2 release to include the fixes to
CMFDefault/browser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/21/10 13:58 , CMF Tests Summarizer wrote:
Summary of messages to the cmf-tests list.
Period Wed Oct 20 12:00:00 2010 UTC to Thu Oct 21 12:00:00 2010 UTC.
There were 4 messages: 4 from CMF Tests.
Unknown
---
Subject: UNKNOWN :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/2/11 12:15 , Suresh V. wrote:
How come the following versions are not found in svn tags?
Products.CMFCore: Versions 2.2.1, 2.2.2, 2.2.3
I have no idea where you are looking, but those tags exist. See
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/11 09:09 , Suresh V. wrote:
Please see:
http://stackoverflow.com/questions/5603459/genericsetup-what-does-toolset-xml-accomplish-if-toolinit-still-has-to-be-called
I could not create a cmf tag, so if you can please add that to the
tags
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/11 11:18 , Lennart Regebro wrote:
On Sat, Apr 9, 2011 at 10:11, Jens Vagelpohl j...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/11 09:09 , Suresh V. wrote:
Please see:
http://stackoverflow.com/questions
On Aug 7, 2011, at 07:00 , CMF tests summarizer wrote:
[1]UNKNOWN FAILED (failures=3, errors=4) : CMF-trunk Zope-trunk
Python-2.6.6 : Linux
https://mail.zope.org/pipermail/cmf-tests/2011-August/015089.html
I have tried to pinpoint the reason for some of these test failures. Two
On Aug 11, 2011, at 21:10 , Hanno Schlichting wrote:
On Sun, Aug 7, 2011 at 5:13 PM, Jens Vagelpohl j...@dataflake.org wrote:
After the wrapping, the discussion item has the wrong path. Even though
self, the talkback object, has the correct path when calling
getPhysicalPath on it. I can't
On Mar 20, 2012, at 16:14 , Charlie Clark wrote:
Hi,
I finally landed my update step for syndication during the PyCon sprints! I
thought I had a few more browser views to update to using the
EditSettingsForm but on a quick check of the files it seems that this has
already been done.
On Mar 21, 2012, at 15:55 , Charlie Clark wrote:
Am 21.03.2012, 00:36 Uhr, schrieb Tres Seaver tsea...@palladion.com:
Sounds good. We should review the code for any stuff
deprecated-and-promised-to-be-remove-in-2.3 before releasing a beta.
I suppose we could also migrate the old Zope
On Mar 20, 2012, at 23:25 , Jens Vagelpohl wrote:
On Mar 20, 2012, at 16:14 , Charlie Clark wrote:
Hi,
I finally landed my update step for syndication during the PyCon sprints! I
thought I had a few more browser views to update to using the
EditSettingsForm but on a quick check
On Mar 22, 2012, at 13:42 , Charlie Clark wrote:
PS. I've just run tests on trunk and am getting failures in CMFCore:
The tests only fail on Python 2.7, they run through fine on 2.6. As such,
they're not functional failures but failures dur to changes in behavior between
2.6 and 2.7. In one
On Mar 31, 2012, at 17:03 , Charlie Clark wrote:
Am 21.03.2012, 22:58 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
The beta eggs are released now.
Jens,
could we have a patch release to include my fallbacks? I'd like to be able to
try the beta with a couple of other sites without
On Apr 3, 2012, at 14:55 , Charlie Clark wrote:
I had a go at autogenerating the api documentation but failed miserably -
lots of empty pages got generated because Sphinx had trouble with import
paths. Does anyone know the appropriate incantations for this?
I have fixed it by creating a
On Apr 5, 2012, at 17:08 , Charlie Clark wrote:
fuchsia:Products.DCWorkflow charlieclark$ bin/sphinx-build docs tmp
Running Sphinx v1.1.3
loading pickled environment... done
No builder selected, using default: html
building [html]: targets for 0 source files that are out of date
updating
Hi all,
I don't recall any information being provided to the CMF developers about CMF
fixes in the most recent Plone Hotfix:
http://plone.org/products/plone-hotfix/releases/20121106
For example, there's a monkey patch to make sure getToolByName only returns
valid tool objects and nothing
On Oct 11, 2013, at 19:11 , Tres Seaver tsea...@palladion.com wrote:
Signed PGP part
On 10/11/2013 07:34 AM, Harald Friessnegger wrote:
hi tres
sorry for the last mail. it got sent accidentally before i could
finish it.
i did a minor change to cmfcore that i'd love to see in the
On Oct 14, 2013, at 13:31, Harald Friessnegger har...@webmeisterei.com wrote:
hi jens
you're right about a missing test for the change.
however, the method getSkinNameFromRequest is not involved in any unit-test
by now.
if you wont' add the change to the next release w/o a propert test,
On Oct 14, 2013, at 23:02 , Harald Friessnegger har...@webmeisterei.com wrote:
hi jens
i've added a test for my change.
http://svn.zope.org/Products.CMFCore/branches/2.2/Products/CMFCore/tests/test_SkinsTool.py?rev=130325view=rev
can you fix the other tests and make a new release?
Hi
On Oct 15, 2013, at 9:09 , yuppie y.2...@wcm-solutions.de wrote:
Jens Vagelpohl wrote:
I have created a new release and uploaded it to PyPI.
-2.2.8 (unreleased)
+2.2.8 (2014-10-15)
You've got a time machine? Cheers, Yuppie
Sorry, typo. I have corrected the file in SVN, but IMHO a new
43 matches
Mail list logo
