[PLIP-Advisories] Re: [Plone] #9328: content im-/export
#9328: content im-/export +--- Reporter: csenger |Owner: csenger Type: PLIP| Status: assigned Priority: minor |Milestone: 4.x Component: Infrastructure | Resolution: Keywords: | +--- Comment(by limi): Nice, didn't know that you were working on this too at the Cathedral sprint. Could we ask Quintagroup to donate it to the Foundation? If we're going to do this, it should be in the Plone repository — or at the very least in the Collective. Private repositories are painful. :) Thanks for the update! -- Ticket URL: <http://dev.plone.org/plone/ticket/9328#comment:30> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8805: Do not ship with NuPlone anymore
#8805: Do not ship with NuPlone anymore ---+ Reporter: hannosch |Owner: robzonenet Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Templates/CSS | Resolution: fixed Keywords: | ---+ Changes (by esteele): * status: new => closed * resolution: => fixed Comment: NuPlone has been updated, I think we can consider this one closed. -- Ticket URL: <http://dev.plone.org/plone/ticket/8805#comment:28> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9214: support logins using e-mail address instead of user id
#9214: support logins using e-mail address instead of user id ---+ Reporter: davisagli |Owner: maurits Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Unknown| Resolution: fixed Keywords: | ---+ Changes (by daftdog): * cc: daftdog (added) Comment: Replying to [comment:49 maurits]: > This is already happening, but the email address is used as both login name and user id (returned by getId()) so you don't notice a difference. I debugged into the member folder creation code, and it determines the member folder's id by checking getId(), which returns the email address. The id/url of the member folder is thereby the email ad (with the @ encoded as -40). We will have public member folders in a project I'm working on, and I really think showing the email ad in the URL is a bad idea. -- Ticket URL: <http://dev.plone.org/plone/ticket/9214#comment:50> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9214: support logins using e-mail address instead of user id
#9214: support logins using e-mail address instead of user id ---+ Reporter: davisagli |Owner: maurits Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Unknown| Resolution: fixed Keywords: | ---+ Comment(by daftdog): When activating email as login and member folder creation, the member folder's ID sort of reveals the email address. A user with the email- address t...@test.org will get a member folder with id test-40test.org. To me that is too close to the real address to deter spammers. IMHO it would make much more sense to use the email address solely for the login, but have member.getId() return the ID that was set during registration. -- Ticket URL: <http://dev.plone.org/plone/ticket/9214#comment:48> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9214: support logins using e-mail address instead of user id
#9214: support logins using e-mail address instead of user id ---+ Reporter: davisagli |Owner: maurits Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Unknown| Resolution: fixed Keywords: | ---+ Comment(by maurits): Replying to [comment:48 daftdog]: > When activating email as login and member folder creation, the member folder's ID sort of reveals the email address. A user with the email- address t...@test.org will get a member folder with id test-40test.org. To me that is too close to the real address to deter spammers. IMHO it would make much more sense to use the email address solely for the login, but have member.getId() return the ID that was set during registration. This is already happening, but the email address is used as both login name and user id (returned by getId()) so you don't notice a difference. -- Ticket URL: <http://dev.plone.org/plone/ticket/9214#comment:49> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9352: combination of search results plips
#9352: combination of search results plips +--- Reporter: laurenskling|Owner: spliter Type: PLIP| Status: new Priority: minor |Milestone: 4.x Component: Infrastructure | Resolution: Keywords: | +--- Comment(by ldr): Replying to [comment:28 yurj]: > why don't add http://pypi.python.org/pypi/collective.searchtool? > > In this way, we could add "per type" result customization, for example showing thumbnail for IATImage and so on. Per type / by adaption lead in customisation makes a lot of sense, not just for search results but also for the summary view for folder listings / collections. There are performance considerations though, especially for search - search results are currently rendered from the catalog result brain (or the equivalent from solr), so do not need the full object loading. -- Ticket URL: <http://dev.plone.org/plone/ticket/9352#comment:29> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9352: combination of search results plips
#9352: combination of search results plips +--- Reporter: laurenskling|Owner: spliter Type: PLIP| Status: new Priority: minor |Milestone: 4.x Component: Infrastructure | Resolution: Keywords: | +--- Comment(by yurj): why don't add http://pypi.python.org/pypi/collective.searchtool? In this way, we could add "per type" result customization, for example showing thumbnail for IATImage and so on. -- Ticket URL: <http://dev.plone.org/plone/ticket/9352#comment:28> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9352: combination of search results plips
#9352: combination of search results plips +--- Reporter: laurenskling|Owner: spliter Type: PLIP| Status: new Priority: minor |Milestone: 4.x Component: Infrastructure | Resolution: Keywords: | +--- Changes (by spliter): * owner: elvix => spliter * status: assigned => new Comment: During the Cathedral sprint we have decided to pick this and keep working on improving the search results page. Some main points that have to be done: * merge "search results" and "advanced search form" into one template in order to let people to tweak their search terms without going back and forth. Switching the context just to tweak a search term is bad idea from UI point of view. * when embedded into the search results, fields of "advanced search form" (further "filter") should behave more like a search filter: ajax calls for immediate update of the results, show/hide the fields in order to provide the quick access to the fields * hiding/showing of the filter's fields should happen with jquery, but the solution should be still accessible for those without JS enabled in the browsers * one non-trivial addition could be the breadcrumbs-like bar that would show current search terms used like google.com shows search options. * when search terms are visible in a bar there should be a quick access to this particular field in the filter without need of showing the whole form. Form should be shown only in case the new search term (not still in the terms bar) has to be added. Screenshot of a prototype and updates are coming. -- Ticket URL: <http://dev.plone.org/plone/ticket/9352#comment:27> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [34220]) migrate `getObjPositionInParent` to stub index capable of sorting search results according to their position in the container, a.k.a. "nogopip" (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:66> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [34196]) only apply monkey patch for `reindexOnReorder` on plone 3.x & shortcut indexing completely if the fake index has been installed (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:65> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [34194]) replace `getObjPositionInParent` with stub index capable of sorting search results according to their position in the container, a.k.a. "nogopip" (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:64> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [34191]) replace monkey patch for `Catalog._getSortIndex` with a fake index that can sort search results according to their position in the container (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:63> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [34156]) pull in the "nogopip" changes from [http://pypi.python.org/pypi/plone.app.folder plone.app.folder], which remove the `getObjPositionInParent` catalog index while keeping the possibility to sort by folder position (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:62> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [34154]) all those calls to `getObjectPosition` use adapter lookups etc, so introducing an optimization for the usual "all results are from one folder" case make sense (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:61> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [34080]) omg, how pythonic! (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:60> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [34078]) use our own zcml for testing & also register the partial ordering adapter now that they [changeset:33504 get along with each other] (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:59> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: focusarea | +--- Comment(by witsch): (In [34040]) tag [http://pypi.python.org/pypi/plone.app.blob/1.0b12 12th] beta (refs #6805, #7822) -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:91> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9210: Folderish pages
#9210: Folderish pages --+- Reporter: laurenskling |Owner: Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Infrastructure| Resolution: wontfix Keywords: folder, page, folderish page | --+- Comment(by limi): Yeah, that's the idea. One of the core ideas of Plone 5 is that everything can behave as a container. There's no PLIP yet, since people are still mostly busy with Plone 4. I'll most likely be writing the PLIP on this (or at least a starting point) if nobody beats me to it. :) -- Ticket URL: <http://dev.plone.org/plone/ticket/9210#comment:27> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9210: Folderish pages
#9210: Folderish pages --+- Reporter: laurenskling |Owner: Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Infrastructure| Resolution: wontfix Keywords: folder, page, folderish page | --+- Comment(by alecm): My understanding is that in the idealized world of Deco/Tiles every page will be folderish. The fact that we don't yet have PLIPs covering the specifics of those technologies might seem a bit worrying though :-) -- Ticket URL: <http://dev.plone.org/plone/ticket/9210#comment:26> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9210: Folderish pages
#9210: Folderish pages --+- Reporter: laurenskling |Owner: Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Infrastructure| Resolution: wontfix Keywords: folder, page, folderish page | --+- Comment(by wichert): A major reason for rejection for this PLIP appears to be that it will be too much of an 'in-between' thing between Plone 3 and Plone 5. I have not seen a proposal for Plone 5 in this area, nor has the request in this ticket for more information on that been answered. Which makes me wonder: is there a plan for Plone 5 to address this issue, or are we handwaving? -- Ticket URL: <http://dev.plone.org/plone/ticket/9210#comment:25> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [33931]) add adapter for previous/next support that doesn't need the catalog, or the `getObjPositionInParent` index for that matter (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:58> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [33924]) add `__getitem__` support to the default ordering adapter for optimized previous/next support in `plone.app.folder` (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:57> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [33870]) simplify calculation of the mapping from rid to position-in- parent & make it work for results from different folders at the same time. the tests now work both with and without the "nogopip" patch (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:56> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [33792]) only do the extra sanity checks when running tests or in debug-mode (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:55> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations
+---
Reporter: smcmahon|Owner: witsch
Type: PLIP| Status: closed
Priority: n/a |Milestone: 4.0
Component: Infrastructure | Resolution: fixed
Keywords: |
+---
Comment(by witsch):
(In [33791]) update "nogopip" buildout so it can be run directly from the
plone 4 coredev checkout:
{{{
$ bin/buildout buildout:directory=$PWD -c experimental/nogopip.cfg
}}}
while still retaining the ability to
{{{
$ bin/develop status
}}}
etc... (refs #9316)
--
Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:54>
Plone <http://plone.org>
Plone Content Management System
_______
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [33790]) eek, that change ended up on the wrong (local git) branch — the monkey needs to be applied unconditionally, since `p.a.folder` doesn't get "initialized" in plone 4 (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:53> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [33789]) add buildout to remove the `getObjPositionInParent` catalog index and use a sort index based on the folder's order information instead (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:52> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [33788]) with r33786 the `getObjPositionInParent` catalog index can be removed and `reindexOnReorder` made a stub, which should improve renaming and reordering performance (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:51> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [33786]) remove `getObjPositionInParent` catalog index and use a sort index based on the folder's order information instead, thereby allowing to skip the (partial) reindexing of all items in the folder when renaming or moving items (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:50> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: focusarea | +--- Comment(by witsch): (In [33691]) the [http://pypi.python.org/pypi/plone.recipe.zope2instance/4.0a3 plone 4.0-specific] versions of `plone.recipe.zope2instance` don't work with python 2.4 since they rely on the [http://docs.python.org/library/hashlib.html hashlib] module — this should hopefully fix the [http://blobot.zitc.de/grid bot] again (refs #6805, #7822) -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:90> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9330: Add ability to choose group when adding new site members
#9330: Add ability to choose group when adding new site members -+-- Reporter: aclark |Owner: aclark Type: PLIP | Status: closed Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: fixed Keywords: | -+-- Changes (by esteele): * status: assigned => closed * resolution: => fixed -- Ticket URL: <http://dev.plone.org/plone/ticket/9330#comment:51> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: focusarea | +--- Comment(by witsch): (In [31040]) provide helper methods for easier migration of custom content types (refs #7822) -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:81> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [30929]) add migration step for unified folders (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:48> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8814: Replace SecureMailHost with a standard Zope mailhost
#8814: Replace SecureMailHost with a standard Zope mailhost +--- Reporter: hannosch|Owner: alecm Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [30913]) fix mailhost migration — `portal_setup` gets passed to migration handler, not the portal object itself (refs #8814) -- Ticket URL: <http://dev.plone.org/plone/ticket/8814#comment:54> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations
+---
Reporter: smcmahon|Owner: witsch
Type: PLIP| Status: closed
Priority: n/a |Milestone: 4.0
Component: Infrastructure | Resolution: fixed
Keywords: |
+---
Comment(by witsch):
(In [30898]) add results of running the benchmark tests with different
numbers of content items (5, 50, 500, 5000) and a helper script for
converting them into something mainly intended to be imported into a
spreadsheet app, but also slightly more human-readable (refs #9316)
to run the benchmarks yourself, you might use it like so::
{{{
$ bin/instance test -s plone.app.folder --tests-pattern=benchmarks 2>&1 |
benchmarks/convert.py
}}}
--
Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:47>
Plone <http://plone.org>
Plone Content Management System
_______
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Comment(by witsch): (In [30897]) fix benchmark tests using the testing content type from r30120 (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:46> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: focusarea | +--- Comment(by witsch): (In [30833]) try to mimic the value of `repr(...)` for the old file and image types for improved test compatibility (refs #7822) -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:80> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9310: User registration process more flexible
#9310: User registration process more flexible -+-- Reporter: dokter |Owner: dokter Type: PLIP | Status: closed Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: fixed Keywords: | -+-- Comment(by maurits): Okay, I made the changes necessary for proper handling of the email login plip in the new @@join_form. See r30720 for details. Some remarks for clarity follow. I made sure the email widget is always displayed, as this field has always been required. If wanted I could do this only when the email address is used as login (#9214), but there are more cases, like for the 'mail_me' field. The email field is now an ASCIIField and uses an ASCIIWidget, as non-ascii emails are not accepted by the email regular expression in the registration tool, and even if you have only ascii the input value is still unicode and when using such an email address as login you run into a unicode error when hashing the username in plone.protect. I protected the code against a few InputErrors (WidgetInputError, ValidationError, ConversionError). For instance, adding accented characters in the username resulted in a traceback instead of a friendly widget error shown in the form. Oh, and a ConflictError was caught and turned into a status message, but I have changed that to raise the Exception so Zope can handle it, which is how those ConflictErrors should be handled AFAIK. In CMFPlone I changed tests/emaillogin.txt to use the new @@join_form; tests are passing; changeset is r30721. The same may need to be done for csrf.txt, but I am already getting errors on the unchanged file, so I am trying not to get side tracked there. :-) -- Ticket URL: <http://dev.plone.org/plone/ticket/9310#comment:50> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9214: support logins using e-mail address instead of user id
#9214: support logins using e-mail address instead of user id ---+ Reporter: davisagli |Owner: maurits Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Unknown| Resolution: fixed Keywords: | ---+ Comment(by maurits): (In [30720]) Integrated the 'email as login' plip (#9214). Made the email field and widget ascii-only, otherwise you get validation errors or unicode errors when trying to log in. Always show the email field. Made the code more robust against input errors, at least for the username and email fields. Fixes #9643, refs #9310 and refs#9214. -- Ticket URL: <http://dev.plone.org/plone/ticket/9214#comment:47> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9310: User registration process more flexible
#9310: User registration process more flexible -+-- Reporter: dokter |Owner: dokter Type: PLIP | Status: closed Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: fixed Keywords: | -+-- Comment(by maurits): (In [30720]) Integrated the 'email as login' plip (#9214). Made the email field and widget ascii-only, otherwise you get validation errors or unicode errors when trying to log in. Always show the email field. Made the code more robust against input errors, at least for the username and email fields. Fixes #9643, refs #9310 and refs#9214. -- Ticket URL: <http://dev.plone.org/plone/ticket/9310#comment:49> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9310: User registration process more flexible
#9310: User registration process more flexible
-+--
Reporter: dokter |Owner: dokter
Type: PLIP | Status: closed
Priority: minor|Milestone: 4.0
Component: Unknown | Resolution: fixed
Keywords: |
-+--
Comment(by maurits):
I get several failures like the next because home page and location are
not on the join form by default anymore. Perhaps this worked on the
branch but not after merging to trunk? Could this have something to do
with the new Plone theme?
{{{
$ bin/instance test -s plone.app.users
...
File "/home/maurits/buildout/plone-
coredev/4.0/src/plone.app.users/plone/app/users/tests/flexible_user_registration.txt",
line 10, in flexible_user_registration.txt
Failed example:
form.getControl(name='form.location')
Exception raised:
Traceback (most recent call last):
File "/home/maurits/shared-
eggs/zope.testing-3.7.7-py2.6.egg/zope/testing/doctest.py", line 1361, in
__run
compileflags, 1) in test.globs
File "",
line 1, in
form.getControl(name='form.location')
File "/home/maurits/shared-
eggs/zope.testbrowser-3.6.0a2-py2.6.egg/zope/testbrowser/browser.py", line
755, in getControl
control, form = disambiguate(intermediate, msg, index)
File "/home/maurits/shared-
eggs/zope.testbrowser-3.6.0a2-py2.6.egg/zope/testbrowser/browser.py", line
54, in disambiguate
raise LookupError(msg)
LookupError: name 'form.location'
}}}
I am trying to integrate this plip with plip #9214 (see ticket #9643) and
having successful tests before I start would be nice.
This is with r30654. I did some test and pep8/pyflakes fixes after that
which did not result in extra test failures. And I have begun integrating
that plip anyway. Sorry if I step on anyone's foot. :)
--
Ticket URL: <http://dev.plone.org/plone/ticket/9310#comment:48>
Plone <http://plone.org>
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9330: Add ability to choose group when adding new site members
#9330: Add ability to choose group when adding new site members -+-- Reporter: aclark |Owner: aclark Type: PLIP | Status: assigned Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by aclark): (In [30655]) Branch for 9330, refs #9330 (I assume this is where the flexible registration stuff gets done.) -- Ticket URL: <http://dev.plone.org/plone/ticket/9330#comment:49> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9309: Better search for East Asian (multi-byte) languages.
#9309: Better search for East Asian (multi-byte) languages. -+-- Reporter: terapyon |Owner: terapyon Type: PLIP | Status: assigned Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: search splitter CJK | -+-- Comment(by tyam): (In [30617]) Changed cfg for aligning with merged branch. refs #9309 -- Ticket URL: <http://dev.plone.org/plone/ticket/9309#comment:53> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: focusarea | +--- Comment(by witsch): (In [30615]) upgrade to ZODB 3.9.2 — the [http://pypi.python.org/pypi/ZODB3/3.9.2#change-history fix in 3.9.1] sounds like something we want (refs #7822) -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:79> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: focusarea | +--- Comment(by witsch): (In [30597]) fix the missing dependency after [changeset:30566 not applying the blob gs profile] anymore (refs #7822) -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:78> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: focusarea | +--- Comment(by witsch): (In [30566]) partly revert r30541: it doesn't make sense to apply `plone.app.blob`'s own gs profiles in plone 4 — the FTI changes can simply be integrated instead (refs #7822) please note that the profiles need to stay for 3.x, though. -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:77> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9309: Better search for East Asian (multi-byte) languages.
#9309: Better search for East Asian (multi-byte) languages. -+-- Reporter: terapyon |Owner: terapyon Type: PLIP | Status: assigned Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: search splitter CJK | -+-- Comment(by terapyon): (In [30565]) merging PLIP9309 refs #9309 -- Ticket URL: <http://dev.plone.org/plone/ticket/9309#comment:52> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: focusarea | +--- Comment(by witsch): (In [30561]) with r30550 in place the ZODB pin (to 3.8.x) can be lifted again (refs #7822) -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:76> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: closed Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: fixed Keywords: | +--- Changes (by esteele): * status: reopened => closed * resolution: => fixed Comment: Merged in http://dev.plone.org/collective/changeset/99402 -- Ticket URL: <http://dev.plone.org/plone/ticket/9186#comment:52> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8814: Replace SecureMailHost with a standard Zope mailhost
#8814: Replace SecureMailHost with a standard Zope mailhost +--- Reporter: hannosch|Owner: alecm Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Changes (by esteele): * status: assigned => closed * resolution: => fixed -- Ticket URL: <http://dev.plone.org/plone/ticket/8814#comment:53> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: focusarea | +--- Comment(by witsch): (In [30550]) with zodb 3.9 `DemoStorage` already is a `BlobStorage`, in which case we better don't mess with the setup (refs #7822) -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:75> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: focusarea | +--- Comment(by witsch): (In [30549]) triggered by the insight that the blob test setup doesn't work with plone 4.0 and zodb 3.9, because it is messing with things too much when zodb 3.9's `DemoStorage` actually already is a `BlobStorage` as well, i thought i should try if the `custom_zodb.py` is still needed at all... (refs #7822) -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:74> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8814: Replace SecureMailHost with a standard Zope mailhost
#8814: Replace SecureMailHost with a standard Zope mailhost +--- Reporter: hannosch|Owner: alecm Type: PLIP| Status: assigned Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by alecm): This PLIP is now fully merged. -- Ticket URL: <http://dev.plone.org/plone/ticket/8814#comment:52> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8814: Replace SecureMailHost with a standard Zope mailhost
#8814: Replace SecureMailHost with a standard Zope mailhost +--- Reporter: hannosch|Owner: alecm Type: PLIP| Status: assigned Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by alecm): (In [30548]) Merged r28664:29350 from plip8814-mailhost branch (refs #8814) -- Ticket URL: <http://dev.plone.org/plone/ticket/8814#comment:51> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8814: Replace SecureMailHost with a standard Zope mailhost
#8814: Replace SecureMailHost with a standard Zope mailhost +--- Reporter: hannosch|Owner: alecm Type: PLIP| Status: assigned Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by alecm): (In [30547]) Merge r28921:30021 from plip8814-mailhost branch (refs #8814) -- Ticket URL: <http://dev.plone.org/plone/ticket/8814#comment:50> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8814: Replace SecureMailHost with a standard Zope mailhost
#8814: Replace SecureMailHost with a standard Zope mailhost +--- Reporter: hannosch|Owner: alecm Type: PLIP| Status: assigned Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by alecm): Oops, that should have been r28712:28918 for plone.app.contentrules -- Ticket URL: <http://dev.plone.org/plone/ticket/8814#comment:49> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8814: Replace SecureMailHost with a standard Zope mailhost
#8814: Replace SecureMailHost with a standard Zope mailhost +--- Reporter: hannosch|Owner: alecm Type: PLIP| Status: assigned Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by alecm): (In [30546]) Merge r28921:30021 from plip8814-mailhost branch (refs #8814) -- Ticket URL: <http://dev.plone.org/plone/ticket/8814#comment:48> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: focusarea | +--- Changes (by witsch): * status: assigned => closed * resolution: => fixed Comment: the PLIP has been merged, and even though there are still [browser:buildouts/plone-coredev/branches/4.0/plips/plip7822-blob- support@30545#l19 things left to wrap up & polish] this ticket is done as far as the PLIP is concerned... -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:73> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: assigned Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: focusarea | +--- Comment(by witsch): (In [30545]) change all imports from the former (and now deprecated) location of ATCT's zope3-style interfaces to make them work on plone 4.0 again (refs #7822) -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:72> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: assigned Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: focusarea | +--- Comment(by witsch): (In [30544]) merge [browser:buildouts/plone- coredev/branches/4.0/plips/plip7822-blob-support@30543 buildout changes for plip7822] (refs #7822) -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:71> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: assigned Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: focusarea | +--- Comment(by witsch): (In [30541]) merge [browser:Plone/branches/plip7822-blob-supp...@30540 branch for plip7822] into [browser:Plone/branches/4...@30540 4.0] (refs #7822) -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:70> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9309: Better search for East Asian (multi-byte) languages.
#9309: Better search for East Asian (multi-byte) languages. -+-- Reporter: terapyon |Owner: terapyon Type: PLIP | Status: assigned Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: search splitter CJK | -+-- Comment(by esteele): (In [30540]) Use the Zope 2.12 branch. PLIP #9309 will need it. This auto- checkout can be removed once we have a 2.12.1 available. Refs #9309. -- Ticket URL: <http://dev.plone.org/plone/ticket/9309#comment:51> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: closed Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Changes (by witsch): * status: assigned => closed * resolution: => fixed Comment: the PLIP has been merged, and even though there are still [browser:buildouts/plone-coredev/branches/4.0/plips/plip9316-unified- folders@30539#l21 things left to wrap up & polish] this ticket can be closed... -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:45> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: assigned Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by witsch): (In [30538]) merge [browser:buildouts/plone- coredev/branches/4.0/plips/plip9316-unified-folders@30536 buildout changes for plip9316] (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:44> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: assigned Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by witsch): (In [30537]) merge [browser:Plone/branches/plip9316-unified-fold...@30536 branch for plip9316] into [browser:Plone/branches/4.0 4...@30536] (refs #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:43> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9309: Better search for East Asian (multi-byte) languages.
#9309: Better search for East Asian (multi-byte) languages. -+-- Reporter: terapyon |Owner: terapyon Type: PLIP | Status: assigned Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: search splitter CJK | -+-- Comment(by limi): Which means that we'll need a Zope 2.12.1 release. Code should already be in the repository. -- Ticket URL: <http://dev.plone.org/plone/ticket/9309#comment:50> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9300: Well formed, valid XHTML
#9300: Well formed, valid XHTML --+- Reporter: benglynn |Owner: benglynn Type: PLIP | Status: assigned Priority: minor |Milestone: 4.0 Component: Unknown | Resolution: Keywords:| --+- Comment(by limi): Any updates on this? Was there ever a test suite set up to keep our XHTML from regressing? (Hanno said that there was work done on this during the Bristol sprint) -- Ticket URL: <http://dev.plone.org/plone/ticket/9300#comment:19> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8801: Move action icon support into actions, deprecate CMFActionIcons
#8801: Move action icon support into actions, deprecate CMFActionIcons +--- Reporter: hannosch|Owner: davisagli Type: PLIP| Status: closed Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Changes (by esteele): * status: assigned => closed * resolution: => fixed -- Ticket URL: <http://dev.plone.org/plone/ticket/8801#comment:25> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8802: Move our upgrade / migration infrastructure to GenericSetup
#8802: Move our upgrade / migration infrastructure to GenericSetup ---+ Reporter: hannosch |Owner: davisagli Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Upgrade/Migration | Resolution: fixed Keywords: | ---+ Changes (by esteele): * status: assigned => closed * resolution: => fixed -- Ticket URL: <http://dev.plone.org/plone/ticket/8802#comment:22> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0
#8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0 +--- Reporter: hannosch|Owner: davisagli Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Changes (by esteele): * status: assigned => closed * resolution: => fixed -- Ticket URL: <http://dev.plone.org/plone/ticket/8808#comment:27> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8805: Do not ship with NuPlone anymore
#8805: Do not ship with NuPlone anymore ---+ Reporter: hannosch |Owner: esteele Type: PLIP | Status: assigned Priority: minor |Milestone: 4.0 Component: Templates/CSS | Resolution: Keywords: | ---+ Comment(by limi): Quoting Eric Steele: > The one bit left is to make sure it works with 4.0. Since #9315 is done and merged, we're almost ready to close this one too — but it needs testing. -- Ticket URL: <http://dev.plone.org/plone/ticket/8805#comment:23> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9310: User registration process more flexible
#9310: User registration process more flexible -+-- Reporter: dokter |Owner: dokter Type: PLIP | Status: closed Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: fixed Keywords: | -+-- Changes (by esteele): * status: assigned => closed * resolution: => fixed -- Ticket URL: <http://dev.plone.org/plone/ticket/9310#comment:47> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #7822: Make standard file content types use ZODB BLOB support
#7822: Make standard file content types use ZODB BLOB support +--- Reporter: limi|Owner: witsch Type: PLIP| Status: assigned Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: focusarea | +--- Comment(by witsch): (In [30519]) aha, all new packages need to be added to `[test]` in order to make `$ bin/test ...` work (refs #7822, #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/7822#comment:69> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9316: Unify folder implementations
#9316: Unify folder implementations +--- Reporter: smcmahon|Owner: witsch Type: PLIP| Status: assigned Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by witsch): (In [30519]) aha, all new packages need to be added to `[test]` in order to make `$ bin/test ...` work (refs #7822, #9316) -- Ticket URL: <http://dev.plone.org/plone/ticket/9316#comment:42> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9310: User registration process more flexible
#9310: User registration process more flexible
-+--
Reporter: dokter |Owner: dokter
Type: PLIP | Status: assigned
Priority: minor|Milestone: 4.0
Component: Unknown | Resolution:
Keywords: |
-+--
Comment(by khink):
Changes have been merged into Plone 4.0 branch.
Details:
{{{
* Merge the used branches:
* merge https://svn.plone.org/svn/plone/Plone/branches/plip9310
-flexible-member-registration/
into https://svn.plone.org/svn/plone/Plone/branches/4.0/
(r30489)
A merge in two parts, [28069:28274] and [28275:30488], because
r28275 was a merge of
the current 4.0 branch unwise back into the plip-branch. (Unwise, in
retrospect.)
* merge
https://svn.plone.org/svn/plone/plone.app.users/branches/plip9310
-flexible-member-registration
into https://svn.plone.org/svn/plone/plone.app.users/trunk/
(r30468)
Also done:
* use z3c.autoinclude (r30493)
* modify rendering so it looks like other user/group configlets
(r30494)
* fix import of PloneMessageFactory (r30492)
* merge
https://svn.plone.org/svn/plone/plone.app.controlpanel/branches/plip9310
-flexible-member-registration
into https://svn.plone.org/svn/plone/plone.app.controlpanel/trunk/
(Merge not needed (trunk has 'utils' module), so not done.)
* merge
https://svn.plone.org/svn/plone/plone.app.form/branches/plip9310-flexible-
member-registration/
into https://svn.plone.org/svn/plone/plone.app.form/trunk/
(r30463)
(No real merge, just added '' to pageform.pt.)
* Merge buildout:
* Added plone.app.users to sources.cfg (r30490)
* Added plone.app.users to Plone 4.0's egg dependencies (r30491)
* Made sure buildout uses trunk version of plone.app.form
* Checkout and run new version of buildout
* Delete PLIP9310-branches (r30503, r30504, r30505, r30506)
}}}
--
Ticket URL: <http://dev.plone.org/plone/ticket/9310#comment:46>
Plone <http://plone.org>
Plone Content Management System
_______
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9309: Better search for East Asian (multi-byte) languages.
#9309: Better search for East Asian (multi-byte) languages. -+-- Reporter: terapyon |Owner: terapyon Type: PLIP | Status: assigned Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: search splitter CJK | -+-- Comment(by tyam): (In [30502]) Changed cfg since Zope code merged to 2.12. refs #9309 -- Ticket URL: <http://dev.plone.org/plone/ticket/9309#comment:49> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9315: New theme for Plone 4
#9315: New theme for Plone 4 ---+ Reporter: limi |Owner: limi Type: PLIP | Status: closed Priority: n/a|Milestone: 4.0 Component: Templates/CSS | Resolution: fixed Keywords: | ---+ Changes (by esteele): * status: assigned => closed * resolution: => fixed -- Ticket URL: <http://dev.plone.org/plone/ticket/9315#comment:53> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9256: Expand variable substitution in mailing action of plone.app.contentrules
#9256: Expand variable substitution in mailing action of plone.app.contentrules ---+ Reporter: smcmahon |Owner: smcmahon Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Content Rules | Resolution: fixed Keywords: | ---+ Changes (by esteele): * status: assigned => closed * resolution: => fixed -- Ticket URL: <http://dev.plone.org/plone/ticket/9256#comment:46> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9250: Add jQuery Tools to base install
#9250: Add jQuery Tools to base install +--- Reporter: limi|Owner: smcmahon Type: PLIP| Status: closed Priority: minor |Milestone: 4.0 Component: Javascript | Resolution: fixed Keywords: | +--- Changes (by esteele): * status: assigned => closed * resolution: => fixed -- Ticket URL: <http://dev.plone.org/plone/ticket/9250#comment:52> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9286: Allow to show/hide portlets
#9286: Allow to show/hide portlets +--- Reporter: igbun |Owner: igbun Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: portlets| +--- Comment(by esteele): (In [30486]) Merge in #9286, refs #9286. -- Ticket URL: <http://dev.plone.org/plone/ticket/9286#comment:36> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9286: Allow to show/hide portlets
#9286: Allow to show/hide portlets +--- Reporter: igbun |Owner: igbun Type: PLIP| Status: closed Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: portlets| +--- Changes (by esteele): * status: assigned => closed * resolution: => fixed Comment: (In [30487]) Remove PLIP branches. Closes #9286. -- Ticket URL: <http://dev.plone.org/plone/ticket/9286#comment:37> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9285: Show blocked portlets in management interface
#9285: Show blocked portlets in management interface ---+ Reporter: igbun |Owner: igbun Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Templates/CSS | Resolution: fixed Keywords: portlets | ---+ Changes (by esteele): * status: assigned => closed * resolution: => fixed Comment: (In [30485]) Removing PLIP branch. Closes #9285. -- Ticket URL: <http://dev.plone.org/plone/ticket/9285#comment:26> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9285: Show blocked portlets in management interface
#9285: Show blocked portlets in management interface ---+ Reporter: igbun |Owner: igbun Type: PLIP | Status: assigned Priority: minor |Milestone: 4.0 Component: Templates/CSS | Resolution: Keywords: portlets | ---+ Comment(by esteele): (In [30484]) Merge PLIP #9285. Refs #9285. -- Ticket URL: <http://dev.plone.org/plone/ticket/9285#comment:25> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9272: Exposing and editing Dublin Core properties
#9272: Exposing and editing Dublin Core properties ---+ Reporter: jaroel |Owner: jaroel Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Templates/CSS | Resolution: fixed Keywords: | ---+ Comment(by esteele): (In [30483]) Factor the Dublin Core information out into an htmlhead viewlet. Refs #9272 -- Ticket URL: <http://dev.plone.org/plone/ticket/9272#comment:41> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9272: Exposing and editing Dublin Core properties
#9272: Exposing and editing Dublin Core properties ---+ Reporter: jaroel |Owner: jaroel Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Templates/CSS | Resolution: fixed Keywords: | ---+ Comment(by esteele): (In [30482]) Merge changes from #9272 into Sunburst. This is probably worth refactoring. Refs #9272. -- Ticket URL: <http://dev.plone.org/plone/ticket/9272#comment:40> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9272: Exposing and editing Dublin Core properties
#9272: Exposing and editing Dublin Core properties ---+ Reporter: jaroel |Owner: jaroel Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Templates/CSS | Resolution: fixed Keywords: | ---+ Comment(by esteele): (In [30481]) Missed Plone merge when merging #9272. Refs #9272. -- Ticket URL: <http://dev.plone.org/plone/ticket/9272#comment:39> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9272: Exposing and editing Dublin Core properties
#9272: Exposing and editing Dublin Core properties ---+ Reporter: jaroel |Owner: jaroel Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Templates/CSS | Resolution: fixed Keywords: | ---+ Changes (by esteele): * status: assigned => closed * resolution: => fixed Comment: (In [30480]) Removing PLIP branches. Closes #9272. -- Ticket URL: <http://dev.plone.org/plone/ticket/9272#comment:38> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9321: Reimplement the search form with an eye on usability
#9321: Reimplement the search form with an eye on usability -+-- Reporter: csenger |Owner: csenger Type: PLIP | Status: closed Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: fixed Keywords: | -+-- Changes (by esteele): * status: reopened => closed * resolution: => fixed Comment: (In [30477]) Removing PLIP branches. Closes #9321. -- Ticket URL: <http://dev.plone.org/plone/ticket/9321#comment:38> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9259: Group dashboards
#9259: Group dashboards +--- Reporter: optilude|Owner: optilude Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Changes (by esteele): * status: assigned => closed * resolution: => fixed Comment: (In [30475]) Removing PLIP branches. Closes #9259 -- Ticket URL: <http://dev.plone.org/plone/ticket/9259#comment:30> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9264: Merge backport patches from plone.app.dexterity into Plone
#9264: Merge backport patches from plone.app.dexterity into Plone +--- Reporter: optilude|Owner: optilude Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Changes (by esteele): * status: assigned => closed * resolution: => fixed Comment: (In [30473]) Removing PLIP branches. Closes #9264. -- Ticket URL: <http://dev.plone.org/plone/ticket/9264#comment:32> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9263: GenericSetup syntax for importing Sharing page roles
#9263: GenericSetup syntax for importing Sharing page roles +--- Reporter: optilude|Owner: optilude Type: PLIP| Status: closed Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: fixed Keywords: | +--- Changes (by esteele): * status: assigned => closed * resolution: => fixed Comment: (In [30471]) Removing PLIP branch. Closes #9263. -- Ticket URL: <http://dev.plone.org/plone/ticket/9263#comment:30> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9322: Ensure that Plone 4 can upgrade Zope on Windows and Mac OS X via binary eggs
#9322: Ensure that Plone 4 can upgrade Zope on Windows and Mac OS X via binary eggs +--- Reporter: limi|Owner: smcmahon Type: PLIP| Status: assigned Priority: major |Milestone: 4.0 Component: Installers | Resolution: Keywords: | +--- Changes (by smcmahon): * priority: n/a => major -- Ticket URL: <http://dev.plone.org/plone/ticket/9322#comment:15> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9256: Expand variable substitution in mailing action of plone.app.contentrules
#9256: Expand variable substitution in mailing action of plone.app.contentrules ---+ Reporter: smcmahon |Owner: smcmahon Type: PLIP | Status: assigned Priority: minor |Milestone: 4.0 Component: Content Rules | Resolution: Keywords: | ---+ Comment(by smcmahon): Merge complete. -- Ticket URL: <http://dev.plone.org/plone/ticket/9256#comment:45> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9256: Expand variable substitution in mailing action of plone.app.contentrules
#9256: Expand variable substitution in mailing action of plone.app.contentrules ---+ Reporter: smcmahon |Owner: smcmahon Type: PLIP | Status: assigned Priority: minor |Milestone: 4.0 Component: Content Rules | Resolution: Keywords: | ---+ Comment(by smcmahon): (In [30430]) Add plone.stringinterp to sources. Refs #9256. -- Ticket URL: <http://dev.plone.org/plone/ticket/9256#comment:44> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9256: Expand variable substitution in mailing action of plone.app.contentrules
#9256: Expand variable substitution in mailing action of plone.app.contentrules ---+ Reporter: smcmahon |Owner: smcmahon Type: PLIP | Status: assigned Priority: minor |Milestone: 4.0 Component: Content Rules | Resolution: Keywords: | ---+ Comment(by smcmahon): (In [30429]) Merge branches/plip9256-contentrules-variables. Refs #9256. -- Ticket URL: <http://dev.plone.org/plone/ticket/9256#comment:43> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9250: Add jQuery Tools to base install
#9250: Add jQuery Tools to base install +--- Reporter: limi|Owner: smcmahon Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Javascript | Resolution: Keywords: | +--- Comment(by smcmahon): Merged. Merge affected Products.CMFPlone and plone.app.upgrade. Also added plone.app.jquerytools to sources.cfg for dev buildout. -- Ticket URL: <http://dev.plone.org/plone/ticket/9250#comment:51> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9250: Add jQuery Tools to base install
#9250: Add jQuery Tools to base install +--- Reporter: limi|Owner: smcmahon Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Javascript | Resolution: Keywords: | +--- Comment(by smcmahon): (In [30393]) Add plone.app.jquerytools to svn auto checkout. Refs #9250. -- Ticket URL: <http://dev.plone.org/plone/ticket/9250#comment:50> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9250: Add jQuery Tools to base install
#9250: Add jQuery Tools to base install +--- Reporter: limi|Owner: smcmahon Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Javascript | Resolution: Keywords: | +--- Comment(by smcmahon): (In [30392]) Merge branches/plip9250-jquery-integration. Refs #9250. -- Ticket URL: <http://dev.plone.org/plone/ticket/9250#comment:49> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9250: Add jQuery Tools to base install
#9250: Add jQuery Tools to base install +--- Reporter: limi|Owner: smcmahon Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Javascript | Resolution: Keywords: | +--- Comment(by smcmahon): (In [30391]) Merge branches/plip9250-jquery-integration. Refs #9250. -- Ticket URL: <http://dev.plone.org/plone/ticket/9250#comment:48> Plone <http://plone.org> Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9305: Use real names instead of usernames
#9305: Use real names instead of usernames --+- Reporter: laurenskling |Owner: ralphjacobs Type: PLIP | Status: closed Priority: minor |Milestone: 4.0 Component: Unknown | Resolution: fixed Keywords:| --+- Changes (by robgietema): * status: assigned => closed * resolution: => fixed Comment: This plip has been merged. -- Ticket URL: <http://dev.plone.org/plone/ticket/9305#comment:30> Plone <http://plone.org> Plone Content Management System _______ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
