only" setup.
Great!
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
objections I'd like to work on this before the CMF 2.0 beta.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
installed, in a way which made them easy to distinguish. I think there
was a convenience button which ran only such steps, as well.
I don't think I ever saw a version that implemented this. And I'm not
sure if GenericSetup should implement this. Bu
Hi Chris!
Chris Withers wrote:
yuppie wrote:
2.) Switch completely to unicode in CMF 2.0:
Sounds like a too big change, don't think we should try that.
I think we all know this is where we need to be eventually, 2.0 seems
the right time to do that, I'd actually prefer this, e
Hi Jens!
Jens Vagelpohl wrote:
On 25 Jan 2006, at 10:42, yuppie wrote:
BTW: In which checkin list do GenericSetup checkins show up now?
They show up in the generic zope checkins list, where all the Zope
checkins themselves go.
Well. Not exactly true. The Zope checkins go to
zope
be both?)
I have to admit that I never understood why import steps have a
"version" attribute. And I still don't understand that concept: Does
that mean each upgrade needs its own import steps?
Cheers,
Yuppie
___
Zope-CMF mai
page templates:
The RSS page works already that way. We need to touch a lot of skin code
to implement this, but it looks more future proof to me. In Zope 2.10
non-unicode input for page templates might become deprecated.
What do you think?
Cheers,
Yuppie
__
Florent Guillaume wrote:
On 17 Jan 2006, at 10:28, yuppie wrote:
The handlers for other sequences (like skin paths and object managers)
just add new sequence items if the item doesn't exist already.
Wouldn't that also work for list properties?
Yes but other sequences have a
clude it in the CMF via a
svn:external link", see
http://palladion.com/home/tseaver/obzervationz/2006/cmf_2_0_update_20060111
Was that part skipped on purpose or by mistake?
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF
(like skin paths and object managers)
just add new sequence items if the item doesn't exist already. Wouldn't
that also work for list properties?
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.or
yuppie wrote:
whit wrote:
yuppie wrote:
I ended up using this method as decorator for most methods:
def memoize(func):
memo = {}
def memoized_func(*args):
if args not in memo:
memo[args] = func(*args)
return memo[args]
return memoized_func
Are there
Hi Whit!
whit wrote:
yuppie wrote:
I ended up using this method as decorator for most methods:
def memoize(func):
memo = {}
def memoized_func(*args):
if args not in memo:
memo[args] = func(*args)
return memo[args]
return memoized_func
Are there
heers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
iliar with
decorators.)
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
be maintained in the Zope core.
That means there is still a lot of work necessary to find out which
methods should become part of the API and which parts of the public API
should be deprecated, modified or made private. Not just in the CMF, but
also in Zope.
Florent Guillaume wrote:
Why is the membership tool folderish?
What's potentially stored in it?
The idea was to store the createMemberContent method and related stuff
like a skeleton home folder in it.
Yuppie
___
Zope-CMF maillist - Zop
Hi Tres!
Tres Seaver wrote:
yuppie wrote:
I agree with your concerns. Views and the FiveActionsTool both use
Five/Zope3 technology for the price of dropping TTW/GenericSetup support
and introducing a second way to do the same things.
Hmm, I'm not sure I see how we are trading
ld
skins machinery.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
or the minimal site structure
currently set up by CMFDefault.setuphandlers.importVarious. I tried to
use the content handler for that, but that adds the complete site
content to a snapshot. Any ideas how to resolve this? I'd really like to
get rid of importVarious.
Required Zope Version
+1
7;s related
to events? Are there any plans to use events in CMF 2.0?
TIA,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
Right?
Thinking about it I wonder how they are used in CMFonFive products and
why they were added to the five_template on CMF trunk. Templates that
use those slots are CMF specific and I thought the goal was to write
templates that can be reused in Zope2/Fi
Hi Florent!
Florent Guillaume wrote:
On 4 Jan 2006, at 20:17, Florent Guillaume wrote:
On 13 Dec 2005, at 13:50, yuppie wrote:
Florent Guillaume wrote:
On 13 Dec 2005, at 12:50, yuppie wrote:
I'd propose to implement an update mode for list properties and to
add an update file for
ard to
support both. I'll leave it up to you to find the right compromises for
CMF 1.6, but I would propose to issue at least a warning if
typeinfo_name isn't found.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.or
Hi Florent!
Florent Guillaume wrote:
On 29 Dec 2005, at 21:20, yuppie wrote:
Florent Guillaume wrote:
On 27 Dec 2005, at 10:51, yuppie wrote:
Florent Guillaume wrote:
Also I'd like to change things like:
node = property(_exportNode, _importNode)
into:
def __exportNode
Hi Rob!
Rob Miller wrote:
yuppie, in the following change:
http://svn.zope.org/CMF/branches/1.6/CMFCore/TypesTool.py?rev=40360&r1=40267&r2=40360
you removed the 'meta_type' attribute from the FactoryTypeInformation
and ScriptableTypeInformation classes. i see that th
Hi Florent!
Florent Guillaume wrote:
On 27 Dec 2005, at 10:51, yuppie wrote:
Florent Guillaume wrote:
Also I'd like to change things like:
node = property(_exportNode, _importNode)
into:
def __exportNode(self):
return self._exportNode()
def __importNode(self,
gs)
self._importNode(*args)
node = property(__exportNode, __importNode)
To allow proper subclass overriding and avoid the dead chicken of having
to redefine the node property each time.
+1
Cheers,
Yuppie
___
Zope-CMF maillist
-English settings translate them
on the fly. Feel free to extend the machinery if you need support for
other encodings.
2.) Looks like toprettyxml has to be called with encoding='utf-8' to set
the writer to utf-8 mode. But that also sets the encoding specified in
the
yle add form instead of an add view.
BTW: Custom catalog indexes and custom workflow definitions are
registered the same way. They have to implement IPluggableIndex or
IWorkflowDefinition.
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zo
Hi!
Jens Vagelpohl wrote:
On 20 Dec 2005, at 21:56, yuppie wrote:
I really don't care much about how this is resolved. But from Rob's
checkins and the discussion following this mail
http://mail.zope.org/pipermail/zope-cmf/2005-November/023399.html
I had the impression that CMF
Hi Rob! Hi Jens!
Rob Miller wrote:
Jens Vagelpohl wrote:
On 20 Dec 2005, at 19:53, yuppie wrote:
The intention was to make things consistent. CMF 1.5 and CMF 2.0
have different ways to register custom type info classes. Before
that change both machineries were broken on the 1.6 branch
the last checkin.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
Hi Chris!
Chris Withers wrote:
yuppie wrote:
1.) It would be nice to have a policy for Zope. If the Zope core
officially supports the BLATHER level (not just in the deprecated zLOG
module) I'm fine with using it in GenericSetup as well.
It doesn't, ZODB has a mapping for it
Hi Florent!
Florent Guillaume wrote:
On 14 Dec 2005, at 10:51, yuppie wrote:
Florent Guillaume wrote:
Can I fix the "pretty" xml exporter to use standard identing? (2
spaces for tags, 4 for attributes)
AFAICS nothing is broken and we don't have a policy for that. So I
woul
other arguments for that change.
So -1 from me.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
ups WARNING might be
appropriate. Messages that report the success of export steps are a
candidate for DEBUG.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.
Hi Florent!
Florent Guillaume wrote:
On 13 Dec 2005, at 12:50, yuppie wrote:
I'd propose to implement an update mode for list properties and to add
an update file for each allowed container. Something like that:
(Didn't have a look at the code. I guess this currently
's what it should do by default. But we could add an
explicit mode="update" to enforce an update mode.)
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
sinfo.xml.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
x27;self.setup_context' in the adapters, we have to rename ISetupEnviron as
well. ISetupContext is already taken, so we would have to call it
IMinimalSetupContext or whatever.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.o
stuff up the old way if you have
old setup code like an Install.py) and export your settings using the
setup tool.
Any kind of questions and feedback are welcome.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://ma
Anyway, ACTUAL_URL supersedes VIRTUAL_URL which is only available if the
Virtual Host Monster changed the URL. I can't think of any good reason
to use VIRTUAL_URL instead of ACTUAL_URL.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-C
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Vagelpohl wrote:
On 2 Dec 2005, at 18:58, yuppie wrote:
Tres Seaver wrote:
import Testing
-import Zope2
-Zope2.startup()
I'm seeing issues in some tests which fail when run outside the full
suite after changes
Jens Vagelpohl wrote:
On 2 Dec 2005, at 18:58, yuppie wrote:
Tres Seaver wrote:
import Testing
-import Zope2
-Zope2.startup()
I'm seeing issues in some tests which fail when run outside the full
suite after changes like these. E.g.,
zopectl> test CMFDefault
I'm trying to ru
6 +75,7 @@
def tearDown(self):
noSecurityManager()
+cleanUp()
RequestTest.tearDown(self)
PlacelessSetup.tearDown(self)
Is this extra cleanUp() necessary? I thought
PlacelessSetup.tearDown(self) calls it already.
Cheers, Yuppie
___
Zo
but
apparently my way to test which ones is not sufficient.
I'm on Windows ATM, so I can't test it with zopectl. But
bin\python.exe bin\test.py -v --libdir Products/CMFDefault
doesn't raise any errors on my machine.
Cheers,
Yuppie
___
.
I hope this is fixed now for 1.6 and 2.0, but if the tests in your
sandbox have a different order than in my sandbox you might still see
some broken tests.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zop
Hi all!
If there are no objections, I'll merge tomorrow the
yuppie-workflow_setup branch into the trunk.
This will break third-party products that register their own workflows
using addWorkflowFactory.
- Customized DCWorkflow workflow definitions should be exported as XML
file
ndexObject(['portal_type', 'Type']),
This was the case in my initial code, but Yuppie changed it:
http://svn.zope.org/trunk/CMFCore/TypesTool.py?rev=35903&r1=35864&r2=35903
I don't remember what the reason was, though I believe it was discussed
a bit at the time on the
way to go, but I'm not sure.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
;SGAIFA'?)
Should we combine all 3 levels in the dotted logger name?
e.g. 'GenericSetup.content.CSAFA'
Or would be 'GenericSetup.content' enough? Currently it is
'GenericSetup.CSAFA'.
Maybe you've got an idea how to resolve this. Don't know what kind of
'co
infos or workflows.
No provisions were made for multiple node adapters per interface.
For the 'actual' answer see Tres' reply. He is more familiar with the
content handlers than I.
Cheers,
Yuppie
___
Zope-CMF maillist - Z
dexing to avoid long running processes on big
sites
If your site contains content you have to reindex manually.
Of course this could be improved.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailm
Hi Rob!
Rob Miller wrote:
yuppie wrote:
2.) Please set svn:keywords Id on new python files.
/me reads svn docs to learn about svn:keywords.
The easiest way to make sure they are set is to modify your svn config.
You might need something like this::
[miscellany]
enable-auto-props
import_context.note('SGAIFA',
'no .ini file for %s/%s' % (subdir, cid))
would be replaced by this code::
logger = import_context.getLogger('SGAIFA')
logger.info('no .ini file for %s/%s' % (subdir, cid))
If there are no objec
Zope 2.9. See
this thread for a related discussion:
http://mail.zope.org/pipermail/zope-cmf/2005-November/023319.html
2.) http://www.zope.org/Collectors/CMF/392 has to be resolved.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF
sync_GenericSetup
Great! Looks like almost everything I was missing regarding logging is
already implemented.
I'll have a look at that branch as soon as I find time.
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zo
impossible to use the CMF 2.0 handlers for CMF 1.5 code. I guess
you have to modify CMFSetup and use some CMF 1.5 handlers to get
everything working.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailm
s not aware of requests, so I can't see an
easy way to make sure the log handler collects only messages for a
specific request.
Or am I missing something?
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope
Hi Tres!
Tres Seaver wrote:
Jens Vagelpohl wrote:
On 15 Nov 2005, at 14:24, yuppie wrote:
The notes should be logged *and* used for reporting in the ZMI.
Implementation:
I'm no logging expert, so I might well be missing something. The
state of the art seems to be using the P
notes to the Python logger *and* to TTW reports might be
the way to go.
Timeframe:
We need soon a stable API to encourage the authors of setup handlers to
use that API. The actual reporting and logging can be implemented later.
Cheers,
Yuppie
Hi Florent!
Thanks for the feedback.
Florent Guillaume wrote:
yuppie wrote:
I can see use cases like that, but I'd prefer a more decentralized
solution. Using the setup tool for tasks like that makes it too
complex and if I want to modify a single tool I don't want to switch
to
'beta' in mid December - that's one month from now. Right?
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
the setup tool to make sure CMF 1.5 setup tools
still work in CMF 2.0
- merge CMFSetup from trunk into the 1.6 branch and remove it from the
trunk (CMF 2.0)
If there are no objections I'll update the deprecation warnings on the
CMF 1.5 and 1.6 branches. The other tasks can
Hi!
Rob Miller wrote:
Jens Vagelpohl wrote:
On 12 Nov 2005, at 09:04, yuppie wrote:
GenericSetup is still a moving target. I would not create a branch
for 1.6 before 2.0 has stabilized.
unfortunately i need to move rather quickly to be able to produce a
proof-of-concept for the framework
is still a moving target. I would not create a branch for
1.6 before 2.0 has stabilized.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for b
Hi Florent!
Florent Guillaume wrote:
yuppie wrote:
- import/export of selected tools from a bigger profile: don't think
we really need that
Right now each tool has its own import step and export step. The 'Import'
and 'Export' tab of the setup tool allow to select
Florent Guillaume wrote:
yuppie wrote:
- import/export of selected tools from a bigger profile: don't think
we really need that
What do you mean by "i/o of selected tools from a bigger profile" ?
Right now each tool has its own import step and export step. The
'Import&
nk the refactoring would be an improvement and if
there are no objections I'll work on this change.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.
Hi!
Do we need CMFDefault/exportimport.zcml on the trunk? Wouldn't it be
better to replace the five:implements directives by implements()
statements in the classes?
If there are no objections I'll change that.
Cheers, Yuppie
___
Zope-CM
erse('category/bar')
Making getActionObject return both kinds of IAction objects would be
confusing because they are quite different objects.
I fixed getActionObject by making it skip newstyle Actions instead of
raising errors.
Hope that resolves the issue.
Cheers,
Yuppie
___
h'
'members_manage_template' is used by the 'members_manage_form' script to
render the result. 'members_manage_form' is the method that should be
called TTW. But I doubt it works with Plone.
Cheers, Yuppie
___
Zope-CMF mai
Hi Chris!
Chris Withers wrote:
yuppie wrote:
yuppie wrote:
Okay, so how would you get the url for an action from inside a skin
script or template?
obj.getActionInfo('object/view')['url'] for type actions or
provider.getActionInfo('user/join')['url&#
Chris Withers wrote:
yuppie wrote:
This is in a completely set up Plone site? Could you please try to
debug those values while we are still in customizePortalTypes?
Okay, in there, it's just the normal Plone types, which we don't use.
And yes, their _aliases dict appears to have &
Hi Chris!
Chris Withers wrote:
yuppie wrote:
Okay, so how would you get the url for an action from inside a skin
script or template?
obj.getActionInfo('object/view')['url'] for type actions or
provider.getActionInfo('user/join')['url'] for other
r CMF 2.0
next week.
I just checked in http://svn.zope.org/?rev=39566&view=rev on the
tseaver-viewification branch. That should be more suitable for comparing
the different approaches.
Cheers,
Yuppie
___
Zope-CMF maillist -
ode is not scalable. Adding validators doesn't look
very easy and implementing something like folder_contents looks almost
impossible.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
Hi Chris!
Chris Withers wrote:
yuppie wrote:
Once again:
getActionObject(action_path) is the method you are looking for.
Another problem with this:
getActionById is defined as public, getActionObject as private, so you
can't use it in any skin scripts or templates :-(
Sugges
Hi Chris!
Chris Withers wrote:
yuppie wrote:
Well. getActionByID did make sense before type actions became normal
actions in CMF 1.4. Since than getActionByID is an ugly backwards
compatibility hack that tries to guess the called method from an
expression string that defines a context
Chris Withers wrote:
yuppie wrote:
I wonder why ti.queryMethodID('view') is None. Is that the case for
all your type infos?
Looks like it.
Does ti._aliases exist? If yes, what does it look like?
Yep, often just maps 'edit':'base_edit', and here queryMeth
exist? If yes, what does it look like?
queryMethodID might be useful for your use case...
Cheers, Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug
you make sure your
action expressions are parsable by getActionByID.
I doubt your use case is a legit use case. If you just want the
deprecation warnings "to STFU" you have to reimplement getActionByID. If
you want to do things right, you don't need a replacement for getActionByID.
W
Hi Chris!
Chris Withers wrote:
yuppie wrote:
getActionInfo()[\'url\']
...will net you a TypeError explaining that getActionInfo takes a
argument that isn't supplied. Looking at the docs, an action_chain,
but I have no idea what one of them is...
'action_chain'
Hi all!
If there are no objections, I'll merge tomorrow the yuppie-setup_cleanup
branch into the trunk. This will break the setup code of all third-party
products that haven't yet switched to GenericSetup/CMFSetup.
1.) factory_type_information data is replaced by XML files in
e a different use case than those mentioned in the deprecation
warning. getActionObject(action_path) is the method you are looking for.
But please note: The whole PloneGenerator class is nasty code and I'm in
the process of removing its base class PortalGenerator from the CMF
trunk. Plone
"add menu) or 'CMFSetup.factory.addConfiguredSite' (from "
"Python). "
Well. CMFSetup.factory.addConfiguredSite itself is deprecated because on
the trunk the factory was moved to CMFDefault.
Cheers, Yuppie
_
code that depends on
PortalGenerator because the new setup machinery is completely different.
PortalGenerator, manage_addCMFSite and oldstyle configuration data (fti
data, workflows - actions are already removed) will soon be removed
completely from the trunk.
Cheers,
Victor Safronovich wrote:
Hello Chris Withers,
Tuesday, October 18, 2005, 4:24:29 PM, you wrote:
CW> yuppie wrote:
def __call__(self):
if self.isTuesday():
return ZopeTwoPageTemplateFile('tuesday.pt').__of__(self)()
return self.index()
C
F 1.5 *and* CMF 2.0.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
for you:
def __call__(self):
if self.isTuesday():
return ZopeTwoPageTemplateFile('tuesday.pt').__of__(self)()
return self.index()
HTH,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.or
Hi Tres!
Tres Seaver wrote:
Lennart Regebro wrote:
On 10/17/05, yuppie wrote:
I know that pattern, but I don't like it. [...]
The code on the goldegg-folder_contents branch processes the input in
the __call__ method of the view class. The template is only invoked if
needed. It&#
Hi Lennart!
Lennart Regebro wrote:
On 10/17/05, yuppie wrote:
I know that pattern, but I don't like it. [...]
The code on the goldegg-folder_contents branch processes the input in
the __call__ method of the view class. The template is only invoked if
needed. It's much cleaner
ame 'adapters' modules to 'exportimport'.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
uch cleaner to use the template just for displaying
results, not for triggering controllers.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
Hi Jens!
Jens Vagelpohl wrote:
On 16 Oct 2005, at 16:21, yuppie wrote:
Jens Vagelpohl wrote:
Doing some more work on Five views for CMF right now. I have the edit
view hooked up and working find for my sample content type. The view
class given to me by Tres defines a POST method, but I
n that all products built on top of the CMF have to ship
with a GenericSetup profile for CMF 2.0.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.or
t make any sense to me: What is your goal? Why do
you need to 'hook up' POST if your edit view works already?
When should your POST method be called and what does that POST method?
Are you working on something special or just on a normal edit view?
Che
t /
import code from the 1.5 branch, but need passing tests first.
Are you using the latest Zope-2_8-branch revision? I recently made a
change that depends on Zope changes.
Hope svn up resolves the issue.
Sorry for not giving a heads up.
Chee
er 12, 2005.
Any objections or comments?
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
ted in CMFTopic/DEPENDENCIES.txt,
http://svn.zope.org/CMF/trunk/?rev=38002&view=rev added a new dependency
on CMFDefault's SkinnedFolder.
Not sure how to resolve this.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.
401 - 500 of 608 matches
Mail list logo
