[PLIP-Advisories] Re: [Plone] #9210: Folderish pages
#9210: Folderish pages --+- Reporter: laurenskling |Owner: Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure| Resolution: Keywords: folder, page, folderish page | --+- Comment(by calvinhp): FWT Vote: -1 and to wait until 5 to see a better final implementation. Although I wouldn't mind seeing another related PLIP to add a rich body field to the current folder. -- Ticket URL: https://dev.plone.org/old/plone/ticket/9210#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] #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: new Priority: minor |Milestone: 4.0 Component: Unknown| Resolution: Keywords: | ---+ Comment(by calvinhp): FWT Vote: +1 -- Ticket URL: https://dev.plone.org/old/plone/ticket/9214#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] #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: new Priority: minor |Milestone: 4.0 Component: Content Rules | Resolution: Keywords: | ---+ Comment(by calvinhp): FWT Vote: +1 an excellent addition to an already powerful feature in Plone. -- Ticket URL: https://dev.plone.org/old/plone/ticket/9256#comment:14 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] #9258: Replace Products.ATReferenceBrowserWidget with archetypes.referencebrowserwidget
#9258: Replace Products.ATReferenceBrowserWidget with archetypes.referencebrowserwidget +--- Reporter: tom_gross |Owner: tom_gross Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by calvinhp): FWT Vote: +1 sounds solid -- Ticket URL: https://dev.plone.org/plone/ticket/9258#comment:11 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: assigned Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by calvinhp): FWT Vote: +1 but ditto on rossp, we have a PLIP format for a reason. -- Ticket URL: https://dev.plone.org/plone/ticket/9259#comment:12 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] #9313: Mobile View with Mobile Image selection options
#9313: Mobile View with Mobile Image selection options --+- Reporter: pigeonflight |Owner: Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Unknown | Resolution: Keywords:| --+- Comment(by raphael): FWT vote: -1 I see this as a feature request more than anything else -- Ticket URL: http://dev.plone.org/plone/ticket/9313#comment:8 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] #9314: Plone Developer Pack option for installers
#9314: Plone Developer Pack option for installers +--- Reporter: smcmahon|Owner: smcmahon Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Installers | Resolution: Keywords: | +--- Comment(by raphael): FWT vote: +1 and I agree with others to leave out PDBDebugMode. -- Ticket URL: http://dev.plone.org/plone/ticket/9314#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] #9279: Making document actions optional
#9279: Making document actions optional --+- Reporter: laurenskling |Owner: Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Unknown | Resolution: Keywords: document actions | --+- Comment(by calvinhp): FWT Vote: -1 I agree with Joel's arguments that our users actually love these features and we have seen similar evidence in our implementations. -- Ticket URL: https://dev.plone.org/old/plone/ticket/9279#comment:17 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] #9281: Use dashboard as social networking tool
#9281: Use dashboard as social networking tool ---+ Reporter: laurenskling |Owner: Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Unknown| Resolution: Keywords: social network, dashboard, web2.0 | ---+ Comment(by calvinhp): FWT Vote: -1 a great add-on, but not part of our core features as it deviates from our primary focus of managing content. -- Ticket URL: https://dev.plone.org/old/plone/ticket/9281#comment:11 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] #9282: Improved search results presentation
#9282: Improved search results presentation ---+ Reporter: elvix |Owner: Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Templates/CSS | Resolution: Keywords: | ---+ Comment(by calvinhp): FWT Vote: +1 and +1 for the merging. -- Ticket URL: https://dev.plone.org/old/plone/ticket/9282#comment:21 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] #9284: Allow views to override skin layer elements easily
#9284: Allow views to override skin layer elements easily ---+ Reporter: MatthewWilkes |Owner: Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Unknown| Resolution: Keywords: | ---+ Comment(by calvinhp): FWT Vote: +1 consistency is always good -- Ticket URL: https://dev.plone.org/old/plone/ticket/9284#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] #9288: Improved commenting infrastructure
#9288: Improved commenting infrastructure +--- Reporter: timo|Owner: timo Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by calvinhp): FWT Vote: +1 much needed and the current implementation makes Plone look low end compared to other similar CMSes. -- Ticket URL: http://dev.plone.org/plone/ticket/9288#comment:17 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] #9295: Improved UI for collections
#9295: Improved UI for collections -+-- Reporter: elvix|Owner: Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by calvinhp): FWT Vote: +1 can this be combined with your dependant PLIP for review? -- Ticket URL: https://dev.plone.org/old/plone/ticket/9295#comment:16 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: Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Unknown | Resolution: Keywords:| --+- Comment(by calvinhp): FWT Vote: +1 -- Ticket URL: https://dev.plone.org/old/plone/ticket/9305#comment:11 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: Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: search splitter CJK | -+-- Comment(by calvinhp): FWT Vote: +1 with the updated PLIP to include more detail -- Ticket URL: https://dev.plone.org/old/plone/ticket/9309#comment:10 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] #9314: Plone Developer Pack option for installers
#9314: Plone Developer Pack option for installers +--- Reporter: smcmahon|Owner: smcmahon Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Installers | Resolution: Keywords: | +--- Comment(by calvinhp): FWT Vote: +1 I'd also like to see the following included: * ipython interpreter shell * PrintingMailHost * collective.workflowed * zope.testrecorder * dcworkflowgraph I'm +1 for leaving in PDBDebugMode as it is an invaluable tool in debugging problems. -- Ticket URL: https://dev.plone.org/old/plone/ticket/9314#comment:16 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: new Priority: n/a|Milestone: 4.0 Component: Templates/CSS | Resolution: Keywords: | ---+ Comment(by calvinhp): FWT Vote: +1 as long as we keep the current theme as an alternate that is bundled with the release. -- Ticket URL: https://dev.plone.org/old/plone/ticket/9315#comment:16 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 calvinhp): FWT Vote: +1 -- Ticket URL: https://dev.plone.org/old/plone/ticket/9316#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] #9320: Add global status bar for site notifications
#9320: Add global status bar for site notifications +--- Reporter: limi|Owner: mj Type: PLIP| Status: new Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by calvinhp): FWT Vote: +1 I also agree with rossp on this one, we have seen many uses for this and would appreciate it being part of the core. -- Ticket URL: http://dev.plone.org/plone/ticket/9320#comment:13 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: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by calvinhp): FWT Vote: +1 based on the new proposal (I had comments and different vote based on the PLIP as it was yesterday, one disadvantage of offline PLIP review) -- Ticket URL: http://dev.plone.org/plone/ticket/9321#comment:13 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: new Priority: n/a |Milestone: 4.0 Component: Installers | Resolution: Keywords: | +--- Comment(by calvinhp): FWT Vote: +1 Is there a place that these types of requirements are documented? A kind of Business Requirements for Plone? -- Ticket URL: https://dev.plone.org/old/plone/ticket/9322#comment:10 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] #9323: Ship with Vice for syndication
#9323: Ship with Vice for syndication ---+ Reporter: MatthewWilkes |Owner: MatthewWilkes Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Unknown| Resolution: Keywords: | ---+ Comment(by calvinhp): FWT Vote: -0 we really need to address this need, syndication is so weak in the currently shipping plone and we specialize in content and it publication. I'd feel better to vote this one in if there was a better effort in place to support Vice moving forward. -- Ticket URL: http://dev.plone.org/plone/ticket/9323#comment:8 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] #9324: Use Amberjack to offer guided help for first-time users
#9324: Use Amberjack to offer guided help for first-time users ---+ Reporter: limi |Owner: Type: PLIP | Status: new Priority: n/a|Milestone: 4.0 Component: Documentation | Resolution: Keywords: | ---+ Comment(by calvinhp): FWT Vote: -0, but I could be swayed to a +1 if we were to only include this functionality as an extended install option that was off by default in the standard installers a la the firefox installers option to install the developer plugins. I don't see this as a core part of Plone, but more of an installer feature. -- Ticket URL: https://dev.plone.org/old/plone/ticket/9324#comment:17 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] #9327: unified interface for lists of content
#9327: unified interface for lists of content +--- Reporter: elvix |Owner: elvix Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by calvinhp): FWT Vote: +1 but I would suggest that we only do this in a way that would allow for the old templates to still be used as rossp mentions. It would make sense to get this new unifed listing API settled now so any new views created during this release use it, but I wouldn't make it a priority to break any old ones yet. -- Ticket URL: https://dev.plone.org/old/plone/ticket/9327#comment:13 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] #9328: content im-/export
#9328: content im-/export -+-- Reporter: csenger |Owner: csenger Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by calvinhp): FWT Vote: +1 -- Ticket URL: https://dev.plone.org/old/plone/ticket/9328#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] #9330: Add ability to choose role when adding new site members
#9330: Add ability to choose role when adding new site members -+-- Reporter: aclark |Owner: aclark Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by calvinhp): FWT Vote: +1 if we are using groups and not roles -- Ticket URL: https://dev.plone.org/old/plone/ticket/9330#comment:18 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] #9328: content im-/export
#9328: content im-/export -+-- Reporter: csenger |Owner: csenger Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Changes (by bohdan_koval): * cc: koval.bog...@gmail.com (added) Comment: Replying to [comment:6 optilude]: I'd also consider how we deal with partial import and export. It's going to be quite commont to import/export a particular folder and its children, for example. Partial export and import can be easily done, because transmogrifier is implemented as adapter for IFolderish interface and can be called in any folderish context. Another good thing about transmogrifier based ex-/import system is that it can be well tested. Transmogrifier pipeline consists of small sections, which can be individually tested. When I was writing quintagroup.transmogrifier package it was very easy to create unit tests for all blueprints. -- Ticket URL: https://dev.plone.org/plone/ticket/9328#comment:16 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] #9323: Ship with Vice for syndication
#9323: Ship with Vice for syndication ---+ Reporter: MatthewWilkes |Owner: MatthewWilkes Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Unknown| Resolution: Keywords: | ---+ Comment(by raphael): FWT vote: -1 unless someone convinces me why it needs to go into the core distribution. IMHO this can be handled as an add-on like today. It could certainly be advertised more aggressively if it were more mature. -- Ticket URL: http://dev.plone.org/plone/ticket/9323#comment:9 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] #9329: Manage actions through-the-plone
#9329: Manage actions through-the-plone ---+ Reporter: igbun |Owner: igbun Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: actions, controlpanel | ---+ Comment(by raphael): I've mixed feelings about this PLIP. One concern is that we would add even more confusion if we need to explain that there are now two different kinds of actions: those managed TTP versus those managed through ZMI although we are dealing with the same action machinery. I also don't by the argument of being nicer. To use actions sensibly you need to know TALES. If you require that you can also handle the ZMI. I'd turn it around and use the future perspective (moving away from CMF actions) as an argument in favor of this PLIP if we can be confident that whatever will come up can be handled through the same UI - ideally without changing it later even. So if this could be turned into a path moving forward (like managing CMF actions now while supporting action tiles or whatever later on) I'd be +1 on this. -- Ticket URL: http://dev.plone.org/plone/ticket/9329#comment:17 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] #9319: Merging archetypes.fieldtraverser into Product.Archetypes
#9319: Merging archetypes.fieldtraverser into Product.Archetypes --+- Reporter: thet |Owner: Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Archetypes| Resolution: Keywords: Archetypes, traverse | --+- Comment(by raphael): I'm not sure everybody understands the motivation behind this PLIP. At least as I understand it the development of archetypes.fieldtraverser has been initiated by the fact that our current machinery does NOT work for binary data when using AnnotationStorage (AS). AS on the other hand has several advantages over todays default (AttributeStorage) like better performance, lower risk of name clashes, possibility to turn fields into properties (in the Python sense) etc. At least for those reasons I'm using archetypes.fieldtraverser today already myself. The fact that archetypes.fieldtraverser also adds an expanded convenience API might come in handy but I'd consider that secondary. Now, this could continue as an add-on but (1) it has to monkey patch Archetypes quite a bit and that should be avoided (2) it would let us move to AnnotationStorage as default storage for all field types - and don't tell me Archetypes is going to die any time soon ;-) It's used so much in the wild that it will continue even after Plone itself moved away from it if only through all those add-ons that will then pull it in as a dependency. Therefore, I'm +1 on this PLIP. -- Ticket URL: https://dev.plone.org/old/plone/ticket/9319#comment:10 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] #9331: Invite to share
#9331: Invite to share -+-- Reporter: djay |Owner: djay Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by raphael): FWT vote: -1 for Plone core (but a big +1 for an add-on) -- Ticket URL: http://dev.plone.org/plone/ticket/9331#comment:12 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: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by raphael): FWT Vote: +1 based on the new proposal -- Ticket URL: http://dev.plone.org/plone/ticket/9321#comment:14 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] #9328: content im-/export
#9328: content im-/export -+-- Reporter: csenger |Owner: csenger Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by raphael): FWT Vote: +1 although I think that can just as well be an independent add-on -- Ticket URL: http://dev.plone.org/plone/ticket/9328#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] #9330: Add ability to choose role when adding new site members
#9330: Add ability to choose role when adding new site members -+-- Reporter: aclark |Owner: aclark Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by raphael): FWT Vote: +1 if we are using groups and not roles -- Ticket URL: http://dev.plone.org/plone/ticket/9330#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] #9327: unified interface for lists of content
#9327: unified interface for lists of content +--- Reporter: elvix |Owner: elvix Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by raphael): FWT Vote: +1 provided the old stuff stays available for some transitional period as well. -- Ticket URL: http://dev.plone.org/plone/ticket/9327#comment:14 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] #9327: unified interface for lists of content
#9327: unified interface for lists of content +--- Reporter: elvix |Owner: elvix Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by MatthewWilkes): I've thought about this some more in the last few days, and gradually convinced myself to become +1, but not sure if it'll happen in time. Therefore, FWT Vote (changed): +1 -- Ticket URL: http://dev.plone.org/plone/ticket/9327#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] #8801: Move action icon support into actions, remove CMFActionIcons
#8801: Move action icon support into actions, remove CMFActionIcons +--- Reporter: hannosch|Owner: davisagli Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by erikrose): +1, assuming... * We can get some DeprecationWarnings into 3.x * This change is documented in the Developer's Upgrade Guide to Plone 4 -- Ticket URL: https://dev.plone.org/plone/ticket/8801#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] #8802: Move our upgrade / migration infrastructure to GenericSetup
#8802: Move our upgrade / migration infrastructure to GenericSetup ---+ Reporter: hannosch |Owner: davisagli Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Upgrade/Migration | Resolution: Keywords: | ---+ Comment(by erikrose): GS currently runs into problems in real-life situations where things gets removed from sites without being properly uninstalled, refusing to install further products until the improperly removed products are dug up and reinstalled (https://weblion.psu.edu/trac/weblion/wiki/GenericSetup#Troubleshooting). GS makes me a little nervous. Could the proposed code run into similar problems? I vote -1 until the risks are enumerated. -- Ticket URL: http://dev.plone.org/plone/ticket/8802#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] #8805: Do not ship with NuPlone anymore
#8805: Do not ship with NuPlone anymore ---+ Reporter: hannosch |Owner: Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Templates/CSS | Resolution: Keywords: | ---+ Comment(by erikrose): +1 as long as we ship with some installable-through-the-Plone theme, a la #9315. Also, for upgraders' sake, NuPlone must be made compatible with 4.0 ''or'' be able to be uninstalled cleanly (if it isn't already). -- Ticket URL: http://dev.plone.org/plone/ticket/8805#comment:21 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] #8809: Make KSS optional
#8809: Make KSS optional +--- Reporter: hannosch|Owner: Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: KSS (Ajax) | Resolution: Keywords: | +--- Comment(by erikrose): I'd rather not change a bunch of stuff that's just going to change again in 5. FWT vote: -1. -- Ticket URL: http://dev.plone.org/plone/ticket/8809#comment:24 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: Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by erikrose): Abstaining since this is my PLIP. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:24 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] #9236: Include CachableRedirects or equivalent functionality so that 301 redirects don't pound Zope
#9236: Include CachableRedirects or equivalent functionality so that 301 redirects don't pound Zope +--- Reporter: jonstahl|Owner: Type: PLIP| Status: reopened Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by erikrose): FWT Vote: +1 as long as purging is implemented. In response to rossp, IIRC, this can't be done straightforwardly in CacheSetup due to the really wacky way into which Plone fires off redirects. It all funnels through the error reporting template, which then checks to see if the error is 404. I would like to hook the config into CacheSetup, perhaps via alecm's suggestion of an empty skin template. -- Ticket URL: https://dev.plone.org/plone/ticket/9236#comment:16 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: new Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by erikrose): Does SecureMailHost presently fire off DeprecationWarnings? If not, I think we should before ripping it out. FWT vote: -1 until some deprecation warnings are added in some (possibly 3.x) release. -- Ticket URL: http://dev.plone.org/plone/ticket/8814#comment:18 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: new Priority: minor |Milestone: 4.0 Component: Unknown| Resolution: Keywords: | ---+ Comment(by erikrose): Having spent a lot of time in the PAS and membership code, I'm concerned at adding more branches in there; there are a lot of cleanups that should happen first. * As alecm says, we need need NEED to stop using loginname to reference users internally; userid is the correct immutable key. I routinely change loginnames when clients move from Plone's built-in auth to our Kerberos auth. * The OpenID plugin has to do some truly awful hacks (the same ones I do in WebServerAuth) to be able to authenticate a non-enumeratable user; that needs to get fixed in PAS. * The setting of the last-login time and, IIRC, the firing of some important events are essentially hard-coded into the login_form. These should be moved elsewhere so non-form-based login can be a first-class citizen. I wonder if email-based login could be better implemented as an add-on once we improve the hook situation in PAS and the rest of the auth code. FWT vote: -1 for now. I think the idea is good, given that so many people seem to request this, but I want to be sure we implement it in a maintainable way rather than just glomming more branches onto an already hard-to-follow subsystem. -- Ticket URL: https://dev.plone.org/plone/ticket/9214#comment:24 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: new Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by alecm): I think the only method we'd have to deprecate is secureSend. I'll probably end up patching that into our new mailhost along with a deprecation warning. The patched method could then be removed in a later release. There are also some convenience regexps and similar in SMH that developers may be importing and relying on. We may want to consider providing some BBB imports for those, since they can be quite convenient. -- Ticket URL: http://dev.plone.org/plone/ticket/8814#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] #9320: Add global status bar for site notifications
#9320: Add global status bar for site notifications +--- Reporter: limi|Owner: mj Type: PLIP| Status: new Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by raphael): FWT vote: -1 for Plone core - +1 for add-on -- Ticket URL: http://dev.plone.org/plone/ticket/9320#comment:14 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
Images choose their IDs based on entered Titles, as with other types. * The Title field remains unrequired. Choosing an image file should stick its name in the Title field via JS if that field was empty, thus effectively providing the current behavior as an option as well as showing the user what's about to happen. * On creation form submission, the object's ID is assigned as follows: * If the Title field is the same as the name of the uploaded file, the ID is the contents of the Title field, without going through the typical Title-field-normalization filter. This maintains the current behavior as an option. * If the Title field is different than the name of the uploaded file, the ID is the normal munged Title field contents. * ~~If browsers are awful and require file extensions in URLs~~ (which they don't), ~~compute them from the uploaded MIME type using the existing `guess_content_type()` machinery or something. This solves the inconsistency where some files say `.jpg`, others `.jpeg`, and still others `.JPG`.~~ == Addendum: the File type == P.S. Though this PLIP shouldn't succeed or fail based on this, we might also consider making a similar change to the behavior of the File type. -- Comment(by erikrose): Revised to dodge Title field normalization in certain cases, as discussed on FWT telecon. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#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] #9186: Set Image IDs from Title field
to another app to rename the file (which, if the user had good reason to name the local file Picture 1, is pretty intrusive). 1. The case of image extensions differs depending on platform. Windows tends to use capital `.JPG`; Mac, `.jpg`. Such inconsistency makes URLs hard to guess. 1. There's no other way in Plone, short of manually enabling short-name editing, to end up with capital letters in URLs. == The Proposal == * Have Images choose their IDs based on entered Titles, as with other types. * The Title field remains unrequired, thus maintaining happiness with uploads via WebDAV or FTP, which don't provide opportunity to enter a title. Choosing an image file should stick its name in the Title field via JS if that field was empty, thus effectively providing the current behavior as an option as well as showing the user what's about to happen. * On creation form submission, the object's ID is assigned as follows: * If the Title field is the same as the name of the uploaded file, the ID is the contents of the Title field, without going through the typical Title-field-normalization filter. This maintains the current behavior as an option. * If the Title field is different than the name of the uploaded file, the ID is the normal munged Title field contents. * ~~If browsers are awful and require file extensions in URLs~~ (which they don't), ~~compute them from the uploaded MIME type using the existing `guess_content_type()` machinery or something. This solves the inconsistency where some files say `.jpg`, others `.jpeg`, and still others `.JPG`.~~ == Addendum: the File type == P.S. Though this PLIP shouldn't succeed or fail based on this, we might also consider making a similar change to the behavior of the File type. -- -- Ticket URL: http://dev.plone.org/plone/ticket/9186#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] #9324: Use Amberjack to offer guided help for first-time users
#9324: Use Amberjack to offer guided help for first-time users ---+ Reporter: limi |Owner: Type: PLIP | Status: new Priority: n/a|Milestone: 4.0 Component: Documentation | Resolution: Keywords: | ---+ Comment(by raphael): FWT Vote: -0 I don't get why that should be in core -- Ticket URL: http://dev.plone.org/plone/ticket/9324#comment:18 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] #9329: Manage actions through-the-plone
#9329: Manage actions through-the-plone ---+ Reporter: igbun |Owner: igbun Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: actions, controlpanel | ---+ Comment(by igbun): OK, after reading carefully all arguments and chatting with some of the people who commented this PLIP, I believe we should postpone it, even if accepted for Plone 4. As Raphael states, we should be confident that the UI will also fit whatever the future brings for actions. We're pretty far from that right now. So, I'll happily re-submit this PLIP for Plone 4.1, if it still makes sense. Then we should have more information to base our decisions on, including: a more enlightened perspective of the future of actions; an add-on product providing this feature; we'll all be older and wiser :) -- Ticket URL: http://dev.plone.org/plone/ticket/9329#comment:18 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] #9314: Plone Developer Pack option for installers
#9314: Plone Developer Pack option for installers +--- Reporter: smcmahon|Owner: smcmahon Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Installers | Resolution: Keywords: | +--- Comment(by witsch): not sure if it's too late, but i'd also nominate [http://pypi.python.org/pypi/mr.freeze/ mr.freeze] [http://pypi.python.org/pypi/Products.signalstack/ Products.signalstack/]. both are extremely useful! -- Ticket URL: http://dev.plone.org/plone/ticket/9314#comment:17 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] #9314: Plone Developer Pack option for installers
#9314: Plone Developer Pack option for installers +--- Reporter: smcmahon|Owner: smcmahon Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Installers | Resolution: Keywords: | +--- Comment(by smcmahon): Replying to [comment:17 witsch]: not sure if it's too late, but i'd also nominate [http://pypi.python.org/pypi/mr.freeze/ mr.freeze] [http://pypi.python.org/pypi/Products.signalstack/ Products.signalstack/]. both are extremely useful! As Hanno just pointed out: remember the dev pack is more of an integrators pack, so GloWorm and stuff is good. developers won't use the installer anyways and want to have it all custom with vimacs plugins... Or, in my words: if you know how to send a USR1 signal, you're not the target audience. -- Ticket URL: http://dev.plone.org/plone/ticket/9314#comment:18 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): Replying to [comment:33 klm]: [...] just trying to factor in what might be pitfalls to address when the time comes to decide about adoption. i know you are, and like i said, much appreciate it... :) -- Ticket URL: http://dev.plone.org/plone/ticket/7822#comment:35 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] #9319: Merging archetypes.fieldtraverser into Product.Archetypes
#9319: Merging archetypes.fieldtraverser into Product.Archetypes
--+-
Reporter: thet |Owner:
Type: PLIP | Status: new
Priority: minor |Milestone: 4.0
Component: Archetypes| Resolution:
Keywords: Archetypes, traverse |
--+-
Comment(by witsch):
Replying to [comment:8 davisagli]:
This would be a win for accessing the value of schema-extender fields --
context/++atfield++myfield instead of
python:context.getField('myfield').getAccessor(context)() ...but we don't
ship with archetypes.schemaextender.
just as a note: `plone.app.blob` currently requires
`archetypes.schemaextender`, so unless it sees a major rewrite (and if the
[ticket:7822 blob plip] is accepted, of course), we might end up shipping
with it. please see [comment:ticket:7822:36 my comment] over in #7822 for
the motivation behind this...
--
Ticket URL: https://dev.plone.org/old/plone/ticket/9319#comment:13
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: new Priority: n/a |Milestone: 4.0 Component: Installers | Resolution: Keywords: | +--- Comment(by limi): I think it should definitely be tracked as a PLIP, the whole point is that this isn't possible to do right now, and is new functionality that needs to be tested and kept in shape as a critical part of the release, IMO. Sounds like a PLIP to me. :) -- Ticket URL: http://dev.plone.org/plone/ticket/9322#comment:11 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] #9324: Use Amberjack to offer guided help for first-time users
#9324: Use Amberjack to offer guided help for first-time users ---+ Reporter: limi |Owner: Type: PLIP | Status: new Priority: n/a|Milestone: 4.0 Component: Documentation | Resolution: Keywords: | ---+ Comment(by limi): Replying to [comment:17 calvinhp]: FWT Vote: -0, but I could be swayed to a +1 if we were to only include this functionality as an extended install option that was off by default in the standard installers a la the firefox installers option to install the developer plugins. That's what I meant by optional install, sorry if I was unclear on that. -- Ticket URL: http://dev.plone.org/plone/ticket/9324#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] #9329: Manage actions through-the-plone
#9329: Manage actions through-the-plone ---+ Reporter: igbun |Owner: igbun Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: actions, controlpanel | ---+ Comment(by erikrose): * In regard to Hanno's planned Plone 5 UI, I see no problem providing a configlet now and a direct-manipulation UI later. Sounds like a continual path forward to me. * Editing actions in a common reason to need the ZMI, and I'm all about getting most site admins out of there. Besides, the portal_actions UI is awful. I look forward to seeing what the implementors come up with. * I disagree that editing portal_actions should be a scary thing confined to the Zope developers' interface. They're just links half the time. I have plenty of users who edit TAL and wouldn't have any trouble with a few CMF Expressions, though navigating the ZMI (which is organized according to implementation, not anything that makes sense to the user) confuses them. As long as no new actions API (to remove in 5) is introduced with this implementation (and I don't see any reason why there would be), my FWT vote is +1. -- Ticket URL: http://dev.plone.org/plone/ticket/9329#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] #9283: A more lightweight backend for collections
#9283: A more lightweight backend for collections
+---
Reporter: elvix |Owner:
Type: PLIP| Status: new
Priority: minor |Milestone: 4.0
Component: Infrastructure | Resolution:
Keywords: |
+---
Comment(by erikrose):
* How much do products currently depend on Collections API that would
change? How popular are custom criteria in the wild? These could hurt
hands-free migration, so I like Calvin's idea of a manual, optional
migration.
* I'd encourage the implementors to work closely with Hanno on this to
make sure any API changes change once: not now and then again in 5. It
sounds like they already have this in mind.
* If we're going to do this in 4.x, my guts tell me it should be in 4.0;
from a site manager's point of view, it seems a scary change for a .x
release.
* Can we get a UI (''any'' UI) for reordering Subfolders along with this?
I've had that request and personally done the crazy ZMI manual-bubble-sort
workarounds for it.
As others point out, this PLIP is light on detail, so I'll be light on my
opinion. FWT vote +1 so we can see what comes of it. We can always take a
step back during reviews if it doesn't work out. (My ulterior motive is
that I want the [ticket:9295 better Collections UI] that depends on this!)
--
Ticket URL: https://dev.plone.org/plone/ticket/9283#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] #9320: Add global status bar for site notifications
#9320: Add global status bar for site notifications +--- Reporter: limi|Owner: mj Type: PLIP| Status: new Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by erikrose): * The Site configlet is just where I expected this would be—right next to the throw your JS in here field—so color one user unastonished. :-) * What happens in Plone 5? It sounds like this should become a tile in a layout, editable through whatever the tile-editing UI ends up being. I haven't run into this use case among our clients, and Joel's experience of a lack of demand for this carries a lot of weight with me—he sees a lot of folks. I'm on the make-it-a-plugin side of the fence, so my FWT vote is -1. Can't wait to recommend the plugin to people, though! -- Ticket URL: http://dev.plone.org/plone/ticket/9320#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] #9323: Ship with Vice for syndication
#9323: Ship with Vice for syndication ---+ Reporter: MatthewWilkes |Owner: MatthewWilkes Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Unknown| Resolution: Keywords: | ---+ Comment(by erikrose): I read Vice's PyPI page but don't have time to play-test it extensively. I'll hang out at +0 but could be moved if some specific wins it would give us were enumerated. FWT Vote: +0 -- Ticket URL: https://dev.plone.org/plone/ticket/9323#comment:10 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: new Priority: minor |Milestone: 4.0 Component: Javascript | Resolution: Keywords: | +--- Comment(by erikrose): FWT Vote: +1 iff we actually make use of it. And when you're making the shiny new login popup whatchamajiggit, please don't forget that some of us don't use form-based login. :-) (I.e., make sure it's hide-able like the current login portlet.) -- Ticket URL: http://dev.plone.org/plone/ticket/9250#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] #9324: Use Amberjack to offer guided help for first-time users
#9324: Use Amberjack to offer guided help for first-time users ---+ Reporter: limi |Owner: Type: PLIP | Status: new Priority: n/a|Milestone: 4.0 Component: Documentation | Resolution: Keywords: | ---+ Comment(by erikrose): Saw Nate's lightning talk and think AJ has a lot of potential! Reminds me of [http://devworld.apple.com/documentation/mac/AppleGuide/AppleGuide-12.html Apple Guide] a lot. If we ever end up with any kind of online help system (e.g. you're in the middle of a task and get confused, so you hit some Help icon someplace), I could see a context-sensitive selection of AJ tours being offered. That said, I like the AJ-on-demo.plone.org idea. We can link to it from the default front page and see whether people find it useful. If they do, I could see AJ becoming the engine that drives the context-sensitive help I fantasize about above. But until then, I don't see a gain from installing this on people's local machines (though I'm always open to enlightenment). My FWT vote is -1 for shipping it with Plone, but I would love to see it done on demo.plone.org and linked from the default front page. -- Ticket URL: https://dev.plone.org/plone/ticket/9324#comment:20 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] #9283: A more lightweight backend for collections
#9283: A more lightweight backend for collections
+---
Reporter: elvix |Owner:
Type: PLIP| Status: new
Priority: minor |Milestone: 4.0
Component: Infrastructure | Resolution:
Keywords: |
+---
Comment(by elvix):
Replying to [comment:23 erikrose]:
* How much do products currently depend on Collections API that would
change? How popular are custom criteria in the wild? These could hurt
hands-free migration, so I like Calvin's idea of a manual, optional
migration.
I don't know about others but : We (Jarn) commonly add criteria
registrations for new indexes. We almost never write custom criteria
types. I think the latter is very uncommon.
* I'd encourage the implementors to work closely with Hanno on this to
make sure any API changes change once: not now and then again in 5. It
sounds like they already have this in mind.
We share offices with Hanno, and would never do this without consulting
him.
* Can we get a UI (''any'' UI) for reordering Subfolders along with
this? I've had that request and personally done the crazy ZMI manual-
bubble-sort workarounds for it.
What is reordering subfolders and how does this relate to collections?
Subfolders in collections? Shouldn't they use the same ui as other
subfolders do? I don't think this PLIP will supply any such UI.
--
Ticket URL: http://dev.plone.org/plone/ticket/9283#comment:24
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: Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by erikrose): FWT vote: +1. Go ahead and have a shot. Here's what will determine my vote on the implementation: * As optilude said, if you're going to workflow things, figure out a way to use the existing workflow framework. * We seem to have member data spread all over the place at the moment. Showing a good understanding of which way we're moving and moving with it will make me really happy. :-) -- Ticket URL: https://dev.plone.org/plone/ticket/9310#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] #9310: User registration process more flexible
#9310: User registration process more flexible -+-- Reporter: dokter |Owner: Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Description changed by dokter: Old description: '''Proposer:''' Duco Dokter [[BR]] '''Seconder:''' Alexander Limi, David Convent [[BR]] [[BR]] == Motivation == Registration of new users in Plone is very restricted in functionality: there is the choice between unsupervised registration or no registration at all. For registration that should go through approval, one needs to install Membrane/Remember. When registration '''is''' allowed, the registration fields are a fixed set. Adding extra fields to the form implies manually changing the HTML of the form, and customizing the registration_form template and process. == Assumptions == There is a need for at least two registration policies: 1. unsupervised registration 2. registration with approval There is a need for more flexibility in the registration fields: one would like to be able to ask for a phonenumber, or company name, for instance. == Proposal Implementation == Add configlet for registration fields and a registration policy to the site configuration options. Allow admin users to decide upon a registration policy, and to determine what fields need to be filled in upon registration. These fields will be required on the registration form. Change the join form into a dynamic form that will use the configuration settings to display the fields to the user to be able to register. Add a portlet for registrations that need approval. These users need to be stored in a utility, and will be created upon approval. == Deliverables == * New configlet in site setup for registration providing two settings: - join policy - join fields * Dynamic form for join process * Utility for storing non-approved users * Portlet for join policy with approval, showing pending registrations * Unit tests * Localization * Documentation == Risks == Default behavior will be same as current situation. No risk assessed. == Participants == * Duco Dokter, dokter * Kim Chee Leong, kcleong * Kees Hink, khink * David Convent, davconvent == Progress == Some of the work has been done at the Baarn 2009 sprint. New description: '''Proposer:''' Duco Dokter [[BR]] '''Seconder:''' Alexander Limi, David Convent [[BR]] [[BR]] == Motivation == Registration of new users in Plone is very restricted in functionality: the registration fields are a fixed set. Adding extra fields to the form implies manually changing the HTML of the form, and customizing the registration_form template and process. == Assumptions == There is a need for more flexibility in the registration fields: one would like to be able to ask for a phonenumber, or company name, for instance. == Proposal Implementation == Add configlet for registration fields. Allow admin users to determine what fields need to be filled in upon registration. These fields will be required on the registration form. Change the join form into a dynamic form that will use the configuration settings to display the fields to the user to be able to register. == Deliverables == * New configlet in site setup for registration providing two settings: - join fields * Dynamic form for join process * Unit tests * Localization * Documentation == Risks == Default behavior will be same as current situation. When migration from an older Plone version si performed, the issue with join_form adaptations needs to be addressed. Most probably a warning is enough for a detected join_form customization. == Participants == * Duco Dokter, dokter * Kim Chee Leong, kcleong * Kees Hink, khink * David Convent, davconvent == Progress == Some of the work has been done at the Baarn 2009 sprint. -- -- Ticket URL: https://dev.plone.org/plone/ticket/9310#comment:16 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] #9347: registration policy
#9347: registration policy -+-- Reporter: dokter |Owner: dokter Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Changes (by raphael): * cc: plip-advisor...@lists.plone.org (added) * owner: = dokter -- Ticket URL: http://dev.plone.org/plone/ticket/9347#comment:1 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 esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/7822#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] #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 esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9316#comment:18 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: new Priority: n/a|Milestone: 4.0 Component: Templates/CSS | Resolution: Keywords: | ---+ Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/9315#comment:18 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 role when adding new site members
#9330: Add ability to choose role when adding new site members -+-- Reporter: aclark |Owner: aclark Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9330#comment:20 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] #9328: content im-/export
#9328: content im-/export -+-- Reporter: csenger |Owner: csenger Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9328#comment:21 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] #9327: unified interface for lists of content
#9327: unified interface for lists of content +--- Reporter: elvix |Owner: elvix Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9327#comment:16 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] #9314: Plone Developer Pack option for installers
#9314: Plone Developer Pack option for installers +--- Reporter: smcmahon|Owner: smcmahon Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Installers | Resolution: Keywords: | +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9314#comment:20 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: Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: search splitter CJK | -+-- Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9309#comment:11 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: Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Unknown | Resolution: Keywords:| --+- Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/9305#comment:12 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] #9302: Improving the event type with recurrence, etc.
#9302: Improving the event type with recurrence, etc. --+- Reporter: regebro |Owner: Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure| Resolution: Keywords: calendar, recurrence | --+- Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/9302#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] #9292: Group management delegation
#9292: Group management delegation +--- Reporter: glenfant|Owner: Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9292#comment:13 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] #9288: Improved commenting infrastructure
#9288: Improved commenting infrastructure +--- Reporter: timo|Owner: timo Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/9288#comment:18 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: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: portlets| +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/9286#comment:18 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] #9271: Improving the search results page
#9271: Improving the search results page --+- Reporter: laurenskling |Owner: Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Unknown | Resolution: Keywords: search, listings | --+- Comment(by esteele): Approved by FWT vote (pending merge). -- Ticket URL: http://dev.plone.org/plone/ticket/9271#comment:10 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] #9249: Add TinyMCE as the default visual editor
#9249: Add TinyMCE as the default visual editor --+- Reporter: limi |Owner: Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Visual Editor (Kupu) | Resolution: Keywords:| --+- Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9249#comment:14 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: new Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/8808#comment:21 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: assigned Priority: major |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/9259#comment:13 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: new Priority: minor |Milestone: 4.0 Component: Unknown | Resolution: Keywords:| --+- Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9300#comment:14 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] #9284: Allow views to override skin layer elements easily
#9284: Allow views to override skin layer elements easily ---+ Reporter: MatthewWilkes |Owner: Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Unknown| Resolution: Keywords: | ---+ Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/9284#comment:16 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: new Priority: minor |Milestone: 4.0 Component: Content Rules | Resolution: Keywords: | ---+ Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9256#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] #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: new Priority: minor |Milestone: 4.0 Component: Unknown| Resolution: Keywords: | ---+ Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9214#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] #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: new Priority: n/a |Milestone: 4.0 Component: Installers | Resolution: Keywords: | +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9322#comment:12 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: new Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/8814#comment:20 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: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/9321#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] #9311: Clean up of user related actions UI
#9311: Clean up of user related actions UI -+-- Reporter: dokter |Owner: Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/9311#comment:10 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: new Priority: minor |Milestone: 4.0 Component: Upgrade/Migration | Resolution: Keywords: | ---+ Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/8802#comment:16 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, remove CMFActionIcons
#8801: Move action icon support into actions, remove CMFActionIcons +--- Reporter: hannosch|Owner: davisagli Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/8801#comment:16 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] #9329: Manage actions through-the-plone
#9329: Manage actions through-the-plone ---+ Reporter: igbun |Owner: igbun Type: PLIP | Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: actions, controlpanel | ---+ Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9329#comment:20 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] #9295: Improved UI for collections
#9295: Improved UI for collections -+-- Reporter: elvix|Owner: Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9295#comment:18 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: Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#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] #9283: A more lightweight backend for collections
#9283: A more lightweight backend for collections +--- Reporter: elvix |Owner: Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: https://dev.plone.org/plone/ticket/9283#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] #9250: Add jQuery Tools to base install
#9250: Add jQuery Tools to base install +--- Reporter: limi|Owner: smcmahon Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Javascript | Resolution: Keywords: | +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/9250#comment:20 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: Type: PLIP | Status: new Priority: minor|Milestone: 4.0 Component: Unknown | Resolution: Keywords: | -+-- Comment(by esteele): Marked Approved -- Ticket URL: http://dev.plone.org/plone/ticket/9310#comment:18 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] #8809: Make KSS optional
#8809: Make KSS optional +--- Reporter: hannosch|Owner: Type: PLIP| Status: new Priority: minor |Milestone: 5.0 Component: KSS (Ajax) | Resolution: Keywords: | +--- Changes (by esteele): * milestone: 4.0 = 5.0 Comment: Rejected for Plone 4.0 by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/8809#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
