Ticket #11193 (closed PLIP: wontfix)
Chameleon 1.x compatibility for Plone 4
Reported by: | runyaga | Owned by: | swampmonkey |
---|---|---|---|
Priority: | minor | Milestone: | 4.x |
Component: | Templates/CSS | Version: | |
Keywords: | ZPT, Chameleon, Cleanup | Cc: | swampmonkey, malthe |
Description (last modified by swampmonkey) (diff)
Enfold Systems is currently using Chameleon in production. This task is to reference work that is being done to Plone and all dependencies to ensure compatibility.
Hudson builder which runs Chameleon tests daily:
- https://hudson.enfoldsystems.com/job/plone4.0-devel-chameleon/ This uses Plone dev version of buildout and does not pull in .eggs. This pulls from source so we can see the latest template changes.
- https://hudson.enfoldsystems.com/job/plone4.0-chameleon-testing/ This uses released version of Plone. Needs to be updated. This runs the Plone test suite with Chameleon turned on.
- https://hudson.enfoldsystems.com/job/plone4.0-chameleon-ptchecker/ This uses released version of Plone. Needs to be updated. This only runs the Chameleon checker for compilation of templates.
SVN:
- https://svn.enfoldsystems.com/public/enfold.ptchecker Used by ptchecker Hudson to check compatibility.
- https://svn.enfoldsystems.com/public/plone-chameleon-testing Buildout used by plone4.0-chameleon-testing and plone4.0-chameleon-ptchecker builders.
- https://svn.enfoldsystems.com/public/plone4dev-chameleon Buildout used by plone4.0-devel-chameleon builder.
Change History
comment:2 Changed 5 years ago by rossp
I think there's a tal:define varibale self-reference scoping issue that affects anywhere in our templates that support the pattern of doing 'tal:define="foo bar;"' and then doing metal:use-macro where the macro makes use of the "foo" variable value if alread set using 'tal:define="foo foo | some_default;"'. This is ues in AT base_edit extensively:
comment:3 Changed 5 years ago by rossp
- Status changed from new to closed
- Resolution set to wontfix
PLEASE READ THIS AND RE-OPEN VALID PLIPS!
As we launch the new PLIP process we'd like to see which PLIPs:
- are still appropriate/needed
- still have owners/proposers/champions
- still have available implementers
If this PLIP should still be considered for future releases of Plone please do re-open this ticket and assign an appropriate milestone. If it should be considered for the next release of Plone, use the 4.2 milestone. Also be sure to update the PLIP description, requester, owner, etc. and include a comment detailing recent progress and new plans. We will use all these details in the new continuous PLIP process.