This page shows of ALL of the supported form variable types (ie. if its not
there its not supported).
Jonathan
- Original Message -
From: Michael Shulman [EMAIL PROTECTED]
To: Jonathan [EMAIL PROTECTED]
Cc: zope@zope.org
Sent: Saturday, March 11, 2006 7:26 PM
Subject: Re: [Zope]
These allow you to use the full power of the the python email package
along with Zope's Page Template technology to easily build and send
fully standards compliant emails.
This release fixes one bug and one deprecation warning. MailTemplates
are now only compatible with Zope 2.8.0 and above.
I'm having difficulty figuring out how to make METAL macros reusable.
Is it standard practice to put macros into a common folder where they can
be used by numerous different websites?
I just can't get a handle on how they are supposed to be used.
According to:-
John Poltorak wrote:
I'm having difficulty figuring out how to make METAL macros reusable.
Is it standard practice to put macros into a common folder where they can
be used by numerous different websites?
I just can't get a handle on how they are supposed to be used.
According to:-
--On 12. März 2006 18:00:27 -0800 David [EMAIL PROTECTED] wrote:
John Poltorak wrote:
I'm having difficulty figuring out how to make METAL macros reusable.
Hi John,
This is about as simple as it gets (sorry if i misunderstood your
question):
(1) Name this page template ptMacros
html
Log message for revision 65918:
update install docs
Changed:
U Products.Five/trunk/INSTALL.txt
-=-
Modified: Products.Five/trunk/INSTALL.txt
===
--- Products.Five/trunk/INSTALL.txt 2006-03-12 10:54:38 UTC (rev 65917)
Log message for revision 65924:
Backport jinty's r41392:
Have test.py remove iself from the pythonpath.
Changed:
U Zope/branches/2.9/test.py
-=-
Modified: Zope/branches/2.9/test.py
===
--- Zope/branches/2.9/test.py
Log message for revision 65925:
Setup logic-less registerPackage zcml directive.
Changed:
_U Products.Five/branches/1.4/
U Products.Five/branches/1.4/fiveconfigure.py
U Products.Five/branches/1.4/fivedirectives.py
U Products.Five/branches/1.4/meta.zcml
-=-
Property changes
Log message for revision 65926:
Setup basic modules for testing registerpackage functionality.
Changed:
_U Products.Five/branches/1.4/
A Products.Five/branches/1.4/tests/test_registerpackage.py
A Products.Five/branches/1.4/tests/testing/pythonproduct1.py
-=-
Property changes on:
Log message for revision 65927:
Added preliminary support for being able to register any python package as a
zope2 product (so it shows up in Control Panel).
Changed:
_U Products.Five/branches/1.4/
U Products.Five/branches/1.4/__init__.py
U
Log message for revision 65934:
Renamed test_registerpackage to test_pythonproducts.
Changed:
_U Products.Five/branches/1.4/
A Products.Five/branches/1.4/tests/test_pythonproducts.py
D Products.Five/branches/1.4/tests/test_registerpackage.py
-=-
Property changes on:
Log message for revision 65935:
Now applying monkey patches to make Zope2 work with python packages that
don't have to live in Products/
Changed:
_U Products.Five/branches/1.4/
U Products.Five/branches/1.4/pythonproducts.py
U
Hi All,
Looks like there's either a documentation or functionality bug in test.py:
http://www.zope.org/Collectors/Zope/2045
Jim, Stefan suggested you might be the best person to ask about this?
cheers,
Chris
PS: Aplogies for the cross-posting, but this is relevant to both lists.
Maybe time
Chris Withers wrote:
Hi All,
Looks like there's either a documentation or functionality bug in test.py:
http://www.zope.org/Collectors/Zope/2045
Jim, Stefan suggested you might be the best person to ask about this?
Yes, it is a known bug.
Jim
--
Jim Fulton mailto:[EMAIL
Jim Fulton wrote:
Jim, Stefan suggested you might be the best person to ask about this?
Yes, it is a known bug.
Okay, is the bug in the documentation or the functionality?
Is there another issue open for this anywhere?
cheers,
Chris
___
Zope-Dev
Chris Withers wrote:
Jim Fulton wrote:
Jim, Stefan suggested you might be the best person to ask about this?
Yes, it is a known bug.
Okay, is the bug in the documentation or the functionality?
Take your pick. The feature is mainly for backward compatibility.
I'd be happy to drop it,
yuppie wrote:
In Zope 3 the NameChooser makes sure you can't use content IDs starting
with '+' or '@'.
Zope 2 doesn't allow '+' in content IDs (actually the error message says
the ID contains characters illegal in URLs), but you can use content IDs
like '@@edit.html'. If the lookup order is
I plan to release the next Zope versions around March 28. The release will
basically contain newer Five versions.
-aj
pgpH0qawTOb9h.pgp
Description: PGP signature
___
Zope-Dev maillist - Zope-Dev@zope.org
yuppie wrote:
Zope 2 doesn't allow '+' in content IDs (actually the error message says
the ID contains characters illegal in URLs), but you can use content IDs
like '@@edit.html'. If the lookup order is changed as proposed
(http://codespeak.net/pipermail/z3-five/2006q1/001186.html) this
Chris McDonough wrote:
and should be fixed in Zope 2.8, 2.9 and trunk.
We'd be changing Zope 2's behaviour (not fixing a Five bug), I would
therefore vote for making this change on the Zope 2 trunk only.
I'd be apt to not further restrict the set of identifiers an OFS content
object can
On Mon, 2006-03-13 at 02:46 +0100, Philipp von Weitershausen wrote:
Here's what we could do: We factor the name validation part in ObjectManager
(which is _checkId) out to a namechooser adapter. Five already has one in
Five.browser.adding. Then, we can also provide an optional namechooser
21 matches
Mail list logo
