[Zope-CMF] CMF Collector: Open Issues
The following supporters have open issues assigned to them in this collector (http://www.zope.org/Collectors/CMF). Assigned and Open efge - CMFSetup: provide non-ascii im- and exports, [Accepted] http://www.zope.org/Collectors/CMF/292 - CMFSetup doesn't correctly detect DCWorkflow on export, [Accepted] http://www.zope.org/Collectors/CMF/298 jens - FSPropertiesObject.py cannot handle multiline input for lines, text attributes, [Accepted] http://www.zope.org/Collectors/CMF/271 mhammond - Windows DevelopmentMode penalty in CMFCore.DirectoryView, [Accepted] http://www.zope.org/Collectors/CMF/366 mj - CMFSetup doesn't correctly detect DCWorkflow on export, [Accepted] http://www.zope.org/Collectors/CMF/298 Pending / Deferred Issues - Debuggable scripts, [Deferred] http://www.zope.org/Collectors/CMF/194 - CMFCalendar weekday locale issue, [Pending] http://www.zope.org/Collectors/CMF/237 - Wrong cache association for FSObject, [Pending] http://www.zope.org/Collectors/CMF/255 - CMFSetup: Windows exports contain CR/LF, LF and even CR newlines, [Pending] http://www.zope.org/Collectors/CMF/266 - PortalCatalog.ZopeFindAndApply should probably also search in opaqueItems, [Pending] http://www.zope.org/Collectors/CMF/296 - WorkflowTool should recurse into opaqueItems, [Pending] http://www.zope.org/Collectors/CMF/297 - add External Methods to workflow script handling, [Pending] http://www.zope.org/Collectors/CMF/329 - Can't invalidate skin items in a RAMCacheManager, [Pending] http://www.zope.org/Collectors/CMF/343 - CMFSetup: Workflow Tool export fails with workflows which have scripts, [Pending] http://www.zope.org/Collectors/CMF/373 - CMFCore.Skinnable.SkinnableObjectManager can merge skin data, [Pending] http://www.zope.org/Collectors/CMF/375 - Proxy Roles does't work for a Script using portal_catalog.searchResults, [Pending] http://www.zope.org/Collectors/CMF/380 - WorkflowAction deprecated warning should not printed for WorkflowMethod, [Pending] http://www.zope.org/Collectors/CMF/388 Pending / Deferred Features - Favorite.py: queries and anchors in remote_url, [Pending] http://www.zope.org/Collectors/CMF/26 - Allow flexible date editing in Event.py (CMFCalendar), [Pending] http://www.zope.org/Collectors/CMF/40 - DefaultDublinCore should have Creator property, [Pending] http://www.zope.org/Collectors/CMF/61 - Make changeFromProperties accept sequences too, [Pending] http://www.zope.org/Collectors/CMF/99 - path criteria on Topic should honor VHM, [Pending] http://www.zope.org/Collectors/CMF/111 - Document.py: universal newlines, [Pending] http://www.zope.org/Collectors/CMF/174 - Permissions in PortalFolder: invokeFactory(), [Pending] http://www.zope.org/Collectors/CMF/175 - Add condition for transition's action like other action, [Pending] http://www.zope.org/Collectors/CMF/207 - Major action enhancement, [Pending] http://www.zope.org/Collectors/CMF/232 - portal_type is undefined in initialization code, [Pending] http://www.zope.org/Collectors/CMF/248 - Action._listsActions() should be more safe, [Pending] http://www.zope.org/Collectors/CMF/253 - Expose Document text_format metadata, [Pending] http://www.zope.org/Collectors/CMF/285 - customization of type of homefolder on creation, [Pending] http://www.zope.org/Collectors/CMF/288 - Allow contentFilter to use review_state, [Pending] http://www.zope.org/Collectors/CMF/294 - CMFTopic Does Not Cache, [Pending] http://www.zope.org/Collectors/CMF/295 - Wishlist: a flag that tags the selected action., [Pending] http://www.zope.org/Collectors/CMF/301 - CMFDefault should make use of allowCreate(), [Pending] http://www.zope.org/Collectors/CMF/340 - Nested Skins, [Pending] http://www.zope.org/Collectors/CMF/377 - CatalogVariableProvider code + tests, [Pending] http://www.zope.org/Collectors/CMF/378 - manage_doCustomize() : minor additions, [Pending] http://www.zope.org/Collectors/CMF/382 ___ 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
[Zope-CMF] Re: SVN: CMF/trunk/GenericSetup/ Improved unicode handling by adding 'getEncoding' to all contexts, export as well as import.
If I understand, the goal is to specify the file encoding for the export. Do
we really need this? Isn't UTF-8 good enough in all cases?
Florent
Tres Seaver wrote:
Log message for revision 38662:
Improved unicode handling by adding 'getEncoding' to all contexts, export as
well as import.
Changed:
U CMF/trunk/GenericSetup/context.py
U CMF/trunk/GenericSetup/interfaces.py
U CMF/trunk/GenericSetup/tests/test_context.py
-=-
Modified: CMF/trunk/GenericSetup/context.py
===
--- CMF/trunk/GenericSetup/context.py 2005-09-28 10:35:29 UTC (rev 38661)
+++ CMF/trunk/GenericSetup/context.py 2005-09-28 11:16:22 UTC (rev 38662)
@@ -46,11 +46,12 @@
security = ClassSecurityInfo()
-def __init__( self, tool ):
+def __init__( self, tool, encoding ):
[...]
+def test_writeDataFile_simple_plain_text_unicode( self ):
+
+from string import digits
+from OFS.Image import File
+FILENAME = 'simple.txt'
+CONTENT_TYPE = 'text/plain'
+CONTENT = u'Unicode, with non-ASCII: %s.' % unichr(150)
+
+site = DummySite( 'site' ).__of__( self.root )
+site.setup_tool = DummyTool( 'setup_tool' )
+tool = site.setup_tool
+ctx = self._makeOne( tool, 'simple', 'latin_1' )
+
+ctx.writeDataFile( FILENAME, CONTENT, CONTENT_TYPE )
+
+snapshot = tool.snapshots._getOb( 'simple' )
+
+self.assertEqual( len( snapshot.objectIds() ), 1 )
+self.failUnless( FILENAME in snapshot.objectIds() )
+
+fileobj = snapshot._getOb( FILENAME )
+
+self.assertEqual( fileobj.getId(), FILENAME )
+self.assertEqual( fileobj.meta_type, File.meta_type )
+self.assertEqual( fileobj.getContentType(), CONTENT_TYPE )
+saved = fileobj.manage_FTPget().decode('latin_1')
+self.assertEqual( saved, CONTENT )
+
--
Florent Guillaume, Nuxeo (Paris, France) CTO, Director of RD
+33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED]
___
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
[Zope-CMF] IE Cache Bug and CachingPolicyManager
In testing all the new caching code, I ran into a fairly nasty IE bug: IE pays attention (more or less) to the Cache-Control header when it comes to requesting new content from the server. The more-or-less part is because IE 5.5+ introduces some proprietary Cache-Control tokens, pre-check and post-check, that let IE ignore the headers to some extent (see http://msdn.microsoft.com/workshop/author/perf/perftips.asp ). Fortunately, this behavior can be turned off by setting Cache-Control: pre-check=0, post-check=0 The problem is that after the page has been requested, IE doesn't necessarily actually render it. If you have a page with a Last-Modified tag, under some (all?) circumstances, IE will render what it has in cache rather than what it has just requested. My guess is that there is a bug in IE that causes its internal Last-Modified freshness heuristics to override explicit Cache-Control freshness declarations and that it pulls the cached page from the wrong place or at the wrong time. It was difficult to track down, but straightforward to work around: I modified CMFCore/CachingPolicyManager.py to allow you to disable the Last-Modified header. To preserve backward compatibility, Last-Modified is on by default, but you can now explicitly disable it. I have also added the ability to set the pre-check and post-check tokens. As an aside, a very useful tool for working with caching and IE is Fiddler: http://www.fiddlertool.com/fiddler/ It's basically the equivalent of LiveHTTPHeaders for IE. I am checking the fixes (with tests) into the 1.5 branch, and Sidnei has volunteered to backport them to CMF 1.4. Geoff ___ 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
[Zope-CMF] Re: SVN: CMF/trunk/GenericSetup/ Improved unicode handling, , ,
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Florent Guillaume wrote: If I understand, the goal is to specify the file encoding for the export. Do we really need this? Isn't UTF-8 good enough in all cases? It's good enough for XML, where documents without specified encodings are mandated to be UTF-8; For HTML, it gets tougher, as the mechanisms for spelling the encodings are harder. Python scripts are much harder, as Python's parser wants an explicit comment for non-ASCII-encoded source. One place that the breakdown shows up is in the 'SnapshotExportContext', where unicode can sneak into content (via import, for instance), which breaks the OFS.File handling in 2.8 (that code is the only client of 'getEncoding' at the moment). Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDOsgM+gerLs4ltQ4RArwFAJ9Dl3BMQP9RmADsLY7GxAK58hC0aQCeK1Gt uKDJiT7IL0W9jC4j55skdWg= =Z3Mj -END PGP SIGNATURE- ___ 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
[Zope-CMF] Re: IE Cache Bug and CachingPolicyManager
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Geoff Davis wrote: In testing all the new caching code, I ran into a fairly nasty IE bug: IE pays attention (more or less) to the Cache-Control header when it comes to requesting new content from the server. The more-or-less part is because IE 5.5+ introduces some proprietary Cache-Control tokens, pre-check and post-check, that let IE ignore the headers to some extent (see http://msdn.microsoft.com/workshop/author/perf/perftips.asp ). Fortunately, this behavior can be turned off by setting Cache-Control: pre-check=0, post-check=0 The problem is that after the page has been requested, IE doesn't necessarily actually render it. If you have a page with a Last-Modified tag, under some (all?) circumstances, IE will render what it has in cache rather than what it has just requested. My guess is that there is a bug in IE that causes its internal Last-Modified freshness heuristics to override explicit Cache-Control freshness declarations and that it pulls the cached page from the wrong place or at the wrong time. It was difficult to track down, but straightforward to work around: I modified CMFCore/CachingPolicyManager.py to allow you to disable the Last-Modified header. To preserve backward compatibility, Last-Modified is on by default, but you can now explicitly disable it. I have also added the ability to set the pre-check and post-check tokens. As an aside, a very useful tool for working with caching and IE is Fiddler: http://www.fiddlertool.com/fiddler/ It's basically the equivalent of LiveHTTPHeaders for IE. I am checking the fixes (with tests) into the 1.5 branch, and Sidnei has volunteered to backport them to CMF 1.4. Let's not forget the trunk, either. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDOsjI+gerLs4ltQ4RAr6AAJ90dcg4uz7BmSkTK/mDrux4K6xaHgCg3BO+ oSJ1WhW0Bw6/1IuRvi4cyK8= =jinn -END PGP SIGNATURE- ___ 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
[Zope-CMF] Re: IE Cache Bug and CachingPolicyManager
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Geoff Davis wrote: In testing all the new caching code, I ran into a fairly nasty IE bug: IE pays attention (more or less) to the Cache-Control header when it comes to requesting new content from the server. The more-or-less part is because IE 5.5+ introduces some proprietary Cache-Control tokens, pre-check and post-check, that let IE ignore the headers to some extent (see http://msdn.microsoft.com/workshop/author/perf/perftips.asp ). Fortunately, this behavior can be turned off by setting Cache-Control: pre-check=0, post-check=0 The problem is that after the page has been requested, IE doesn't necessarily actually render it. If you have a page with a Last-Modified tag, under some (all?) circumstances, IE will render what it has in cache rather than what it has just requested. My guess is that there is a bug in IE that causes its internal Last-Modified freshness heuristics to override explicit Cache-Control freshness declarations and that it pulls the cached page from the wrong place or at the wrong time. It was difficult to track down, but straightforward to work around: I modified CMFCore/CachingPolicyManager.py to allow you to disable the Last-Modified header. To preserve backward compatibility, Last-Modified is on by default, but you can now explicitly disable it. I have also added the ability to set the pre-check and post-check tokens. Thanks for the analysis, and the fix (sorry for the earlier, premature reply). As an aside, a very useful tool for working with caching and IE is Fiddler: http://www.fiddlertool.com/fiddler/ It's basically the equivalent of LiveHTTPHeaders for IE. I am checking the fixes (with tests) into the 1.5 branch, and Sidnei has volunteered to backport them to CMF 1.4. I *think* such a patch should apply cleanly to the trunk as well. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDOskJ+gerLs4ltQ4RAieeAKCvhbFD8SgeppjyqNSHliK/RWgzBACgguTW sP+pH39cbzoxSuH0S7+nAyE= =Zx3z -END PGP SIGNATURE- ___ 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
[Zope-CMF] Re: IE Cache Bug and CachingPolicyManager
On Wed, 28 Sep 2005 12:47:06 -0400, Tres Seaver wrote: Thanks for the analysis, and the fix (sorry for the earlier, premature reply). No problem. P-J Grizel suggested offline that the problem might be due to IE not parsing the time zone string at the end of the Last-Modified date stamp correctly. He's tracking down the information. If he's right, there may be a few places in CMF and possibly Zope that will need a bit of minor surgery. I *think* such a patch should apply cleanly to the trunk as well. Ok. Do you want me to take care of it? Geoff ___ 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
[Zope-CMF] Zope Debugger 0.8.0 Released!
Zope Debugger is an enhanced version of pdb for use with Zope. It can be used simply by inserting the following lines in any python code you'd like to debug, including Script (Python)'s and FSPythonScripts: from Products.zdb import set_trace set_trace() It requires no changes to Zope, CMF or Plone or any funky interaction with any specific kind of editing software. All you really need to do is insert the snippet above and make sure your Zope instance is running in foreground mode. For more information, please see: http://www.simplistix.co.uk/software/zope/zdb cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ 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
