[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 jens - "Discussion replies removal", [Accepted] http://www.zope.org/Collectors/CMF/391 mhammond - "Windows DevelopmentMode penalty in CMFCore.DirectoryView", [Accepted] http://www.zope.org/Collectors/CMF/366 regebro - "fiveactionstool broken (Zope 2.9/3.2)", [Accepted] http://www.zope.org/Collectors/CMF/392 Pending / Deferred Issues - "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 - "FSPropertiesObject.py cannot handle multiline input for lines, text attributes", [Pending] http://www.zope.org/Collectors/CMF/271 - "PortalCatalog.ZopeFindAndApply should probably also search in opaqueItems", [Pending] http://www.zope.org/Collectors/CMF/296 - "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 - "workflow notify success should be after reindex", [Pending] http://www.zope.org/Collectors/CMF/389 - "came_from and VIRTUAL_URL problem", [Pending] http://www.zope.org/Collectors/CMF/393 - "DCWorkflow - Transition Guards - Documentation Bug", [Pending] http://www.zope.org/Collectors/CMF/394 - "PortalFolder.py _verifyObjectPaste ignores executable security", [Pending] http://www.zope.org/Collectors/CMF/396 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/CMFCore/tests/test_ - made copy tests more independent from implementation details of _verifyObjectPaste
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 like these. E.g.,
zopectl> test CMFDefault
These issues are not present on the trunk, they are specific to your
branch, Tres. I see failures as well, but it all blows up with
exceptions like this:
==
ERROR: test_join_memberproperties
(CMFDefault.tests.test_join.MembershipTests)
--
Traceback (most recent call last):
File "/usr/local/zope/28Instance/Products/CMFDefault/tests/
test_join.py", line 37, in setUp
zcml.load_config('configure.zcml', Products.DCWorkflow)
AttributeError: 'module' object has no attribute 'DCWorkflow'
hm... does this help?
It says to me that the product initialization phase is being skpped
(which is what I would expect from the diff at the top).
The linkviews doc tests are not set up correctly. They did work before
because some other tests called Zope2.startup().
I guess the correct way would be to use ZopeTestCase's installProduct
method, but adding Zope2.startup() at the top of test_linkviews.py seems
to fix this issue as well.
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
[Zope-CMF] Re: VIRTUAL_URL and ACTUAL_URL (was Re: Collector Issues)
Hi! Alexander Limi wrote: On Sat, 03 Dec 2005 10:04:52 -0800, Andreas Jung <[EMAIL PROTECTED]> wrote: AFAIK ACTUAL_URL contains the full URL *plus* the query string. VIRTUAL_URL does not contain the query string. ACTUAL_URL was introduced on request by the Plone developers. Except, the implementation did not end up including the query string - which was the whole idea in the first place, to have ACTUAL_URL be "what is in the address bar right now", so things like anchors work (did you know there is no proper way of getting anchors to work in virtual hosting setups without doing three conditional tests in your template?). When I suggested that it should be fixed, people wanted to invent *another* variable that included the query string, and it degenerated into a "what should we name it" discussion after that. So that thing still has to be "reinvented" in Plone, which sucks. Intended or not, ACTUAL_URL was released with a specific behavior that is useful for and used by some people. You can't change the behavior of ACTUAL_URL in a non backwards compatible way just to make it more suitable for your use cases. 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-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] Re: VIRTUAL_URL and ACTUAL_URL (was Re: Collector Issues)
Alexander Limi wrote at 2005-12-3 14:27 -0800: > ... >Except, the implementation did not end up including the query string - >which was the whole idea in the first place, to have ACTUAL_URL be "what >is in the address bar right now", so things like anchors work (did you >know there is no proper way of getting anchors to work in virtual hosting >setups without doing three conditional tests in your template?). I have difficulties to understand the paragraph: What have anchors to do with the query string? As I understand it, "anchors" (fragments in the URL) are a client only concept: fragments are not transfered to the server. -- Dieter ___ 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: Re: VIRTUAL_URL and ACTUAL_URL (was Re: Collector Issues)
On Sun, 04 Dec 2005 10:23:25 -0800, Dieter Maurer <[EMAIL PROTECTED]> wrote: I have difficulties to understand the paragraph: What have anchors to do with the query string? As I understand it, "anchors" (fragments in the URL) are a client only concept: fragments are not transfered to the server. Correct, but it's impossible to construct valid anchors that do not reload the page if you do not have a working ACTUAL_URL because of Zope setting the value to something else than the current page. Thus, a link like will *reload the page*, then go to the anchor - which is clearly not desirable behaviour. -- _ Alexander Limi · Chief Architect · Plone Solutions · Norway Consulting · Training · Development · http://www.plonesolutions.com _ Plone Co-Founder · http://plone.org · Connecting Content Plone Foundation · http://plone.org/foundation · Protecting Plone ___ 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: VIRTUAL_URL and ACTUAL_URL (was Re: Collector Issues)
On Sun, 04 Dec 2005 07:24:36 -0800, yuppie <[EMAIL PROTECTED]> wrote: Intended or not, ACTUAL_URL was released with a specific behavior that is useful for and used by some people. You can't change the behavior of ACTUAL_URL in a non backwards compatible way just to make it more suitable for your use cases. The original use case for ACTUAL_URL was to use with anchors, and that's why it is a bug, not intentional behaviour. If you want a variable *without* the query string (which is by far a much less common use case) that's fine - but *that* should be the new variable, not the old one. It was even added in a point release, so the "changing the behaviour" isn't really a good argument. The implementation was not complete in the first version - and I filed a bug report on it. -- _ Alexander Limi · Chief Architect · Plone Solutions · Norway Consulting · Training · Development · http://www.plonesolutions.com _ Plone Co-Founder · http://plone.org · Connecting Content Plone Foundation · http://plone.org/foundation · Protecting Plone ___ 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
Re: [Zope-CMF] Re: Re: VIRTUAL_URL and ACTUAL_URL (was Re: Collector Issues)
--On 4. Dezember 2005 20:13:52 -0800 Alexander Limi <[EMAIL PROTECTED]> wrote: On Sun, 04 Dec 2005 10:23:25 -0800, Dieter Maurer <[EMAIL PROTECTED]> wrote: I have difficulties to understand the paragraph: What have anchors to do with the query string? As I understand it, "anchors" (fragments in the URL) are a client only concept: fragments are not transfered to the server. Correct, but it's impossible to construct valid anchors that do not reload the page if you do not have a working ACTUAL_URL because of Zope setting the value to something else than the current page. Thus, a link like will *reload the page*, then go to the anchor - which is clearly not desirable behaviour. Why can't you define your own concatenation of ACTUAL_URL + query string within the global definitions of Plone? -aj pgpkKbOZVMdxd.pgp Description: 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
