#9256: Expand variable substitution in mailing action of plone.app.contentrules
---+
Reporter: smcmahon |Owner: smcmahon
Type: PLIP | Status: assigned
Priority: minor |
Image IDs (https://dev.plone.org/plone/ticket/9186):
* Erik is finding this less difficult than he feared. Probably won't
be extending it to apply to the File type, as that introduces the
scenario where downloading a Word doc results in a file whose
name doesn't end in .doc, causing
Claris Emailer's 10-minute outgoing delay, how I miss thee. Here's are
the items that were scrolled off my screen:
Allow views to override skin layer elements easily (https://dev.plone.org/plone/ticket/9284
):
* Matthew will start his PLIP on Friday.
Geir's PLIPs:
* Geir and some
On Aug 5, 2009, at 1:00 PM, Erik Rose wrote:
Python 2.6, Zope 2.12 (https://dev.plone.org/plone/ticket/8808):
* David ported the migration procedure to GS and moved it into
plone.app.upgrade. Ran a migration from a stock Plone 2.5 to 4.0,
and it seemed to work, though he welcomes more
On Wed, Aug 5, 2009 at 1:18 PM, David Glickdavidgl...@onenw.org wrote:
On Aug 5, 2009, at 1:00 PM, Erik Rose wrote:
Python 2.6, Zope 2.12 (https://dev.plone.org/plone/ticket/8808):
* David ported the migration procedure to GS and moved it into
plone.app.upgrade. Ran a migration from a stock
On Wed, Aug 5, 2009 at 10:00 PM, Erik Rosepsuc...@grinchcentral.com wrote:
* All the globalization in templates is gone now, and Plone's
templates have been updated to not use it. This originated in the
5.x branch as a speed optimization, but does it deliver? It's
going to break a lot
I concur that the globalize stuff is a serious hack and should be
removed at some point. However, I don't think 4.0 is the right time
to remove it considering the huge impact it will have on 3rd-party
products. If removing it doesn't result in a significant performance
improvement (and
Alec Mitchell wrote:
I concur that the globalize stuff is a serious hack and should be
removed at some point. However, I don't think 4.0 is the right time
to remove it considering the huge impact it will have on 3rd-party
products. If removing it doesn't result in a significant performance
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alec Mitchell wrote:
I concur that the globalize stuff is a serious hack and should be
removed at some point. However, I don't think 4.0 is the right time
to remove it considering the huge impact it will have on 3rd-party
products. If removing
On Thu, Aug 6, 2009 at 3:23 AM, Tres Seavertsea...@palladion.com wrote:
Alec Mitchell wrote:
Perhaps we could find some clever way to deprecate access to the
globalized attributes (e.g. make them all lazy lookups and issue a
warning on first access)?
There is an example of this pattern in
On Aug 5, 2009, at 1:45 PM, Alec Mitchell wrote:
On Wed, Aug 5, 2009 at 1:18 PM, David Glickdavidgl...@onenw.org
wrote:
* IPublishTraverse is used where ITraverse should be; that's why
some
linkintegrity tests are failing.
Actually they both need to be used. And that's just a guess -- I
11 matches
Mail list logo
