Menu
▾
▴
plone-developers — Plone Core Development
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
(1) |
Mar
(62) |
Apr
(21) |
May
(138) |
Jun
(105) |
Jul
(231) |
Aug
(172) |
Sep
(283) |
Oct
(292) |
Nov
(179) |
Dec
(92) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(151) |
Feb
(149) |
Mar
(59) |
Apr
(90) |
May
(177) |
Jun
(161) |
Jul
(231) |
Aug
(170) |
Sep
(362) |
Oct
(448) |
Nov
(253) |
Dec
(175) |
| 2004 |
Jan
(327) |
Feb
(254) |
Mar
(336) |
Apr
(215) |
May
(260) |
Jun
(300) |
Jul
(193) |
Aug
(200) |
Sep
(120) |
Oct
(346) |
Nov
(131) |
Dec
(156) |
| 2005 |
Jan
(127) |
Feb
(153) |
Mar
(219) |
Apr
(481) |
May
(391) |
Jun
(351) |
Jul
(496) |
Aug
(332) |
Sep
(335) |
Oct
(213) |
Nov
(351) |
Dec
(238) |
| 2006 |
Jan
(268) |
Feb
(499) |
Mar
(355) |
Apr
(293) |
May
(244) |
Jun
(341) |
Jul
(207) |
Aug
(286) |
Sep
(229) |
Oct
(197) |
Nov
(247) |
Dec
(292) |
| 2007 |
Jan
(505) |
Feb
(460) |
Mar
(373) |
Apr
(197) |
May
(106) |
Jun
(268) |
Jul
(200) |
Aug
(263) |
Sep
(193) |
Oct
(188) |
Nov
(378) |
Dec
(222) |
| 2008 |
Jan
(255) |
Feb
(553) |
Mar
(303) |
Apr
(436) |
May
(290) |
Jun
(340) |
Jul
(310) |
Aug
(179) |
Sep
(223) |
Oct
(286) |
Nov
(240) |
Dec
(162) |
| 2009 |
Jan
(164) |
Feb
(110) |
Mar
(220) |
Apr
(175) |
May
(227) |
Jun
(369) |
Jul
(224) |
Aug
(234) |
Sep
(146) |
Oct
(168) |
Nov
(239) |
Dec
(119) |
| 2010 |
Jan
(217) |
Feb
(216) |
Mar
(322) |
Apr
(217) |
May
(215) |
Jun
(209) |
Jul
(268) |
Aug
(209) |
Sep
(195) |
Oct
(163) |
Nov
(147) |
Dec
(145) |
| 2011 |
Jan
(147) |
Feb
(163) |
Mar
(185) |
Apr
(279) |
May
(269) |
Jun
(237) |
Jul
(397) |
Aug
(168) |
Sep
(394) |
Oct
(225) |
Nov
(278) |
Dec
(145) |
| 2012 |
Jan
(182) |
Feb
(264) |
Mar
(326) |
Apr
(254) |
May
(221) |
Jun
(250) |
Jul
(187) |
Aug
(247) |
Sep
(487) |
Oct
(256) |
Nov
(180) |
Dec
(146) |
| 2013 |
Jan
(176) |
Feb
(141) |
Mar
(181) |
Apr
(274) |
May
(138) |
Jun
(332) |
Jul
(136) |
Aug
(114) |
Sep
(74) |
Oct
(82) |
Nov
(165) |
Dec
(130) |
| 2014 |
Jan
(66) |
Feb
(229) |
Mar
(286) |
Apr
(96) |
May
(163) |
Jun
(103) |
Jul
(70) |
Aug
(81) |
Sep
(76) |
Oct
(60) |
Nov
(103) |
Dec
(95) |
| 2015 |
Jan
(79) |
Feb
(33) |
Mar
(89) |
Apr
(87) |
May
(46) |
Jun
(29) |
Jul
(45) |
Aug
(23) |
Sep
(107) |
Oct
(134) |
Nov
(146) |
Dec
(14) |
| 2016 |
Jan
(10) |
Feb
(26) |
Mar
(12) |
Apr
(12) |
May
(21) |
Jun
(9) |
Jul
(1) |
Aug
(7) |
Sep
(4) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
(1) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
(2) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2019 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
(3) |
Jun
(2) |
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Ramon B. <ram...@go...> - 2015-09-07 18:14:02
|
Hi, yes, I had the drag&drop functionality already in, but I faced some problems with the inline editing of the fields, so I removed it for version 0.1.0. But there will be dnd in future releases for sure;) Another interesting thing would be, to actually drag files from the desktop into some folder of Plone. This should actually work with Electron/node.js. Maybe also a feature for the next major version. Cheers, Ramon > Am 07.09.2015 um 16:29 schrieb espen <es...@me...>: > > When (if) things are as smooth as that, some users might asume that they can drag/drop items into folders (?) > > >> 6. sep. 2015 kl. 23.31 skrev T. Kim Nguyen-2 [via Plone] <[hidden email] <x-msg://28/user/SendEmail.jtp?type=node&node=7574161&i=0>>: >> >> I liked how quickly you could create new folders. The current Plone 5 folder contents still takes you to a standard add form that leaves you looking at the newly created object. +1 for your joining forces and improving Plone 5 even more! >> >> Kim >> >> >> >> On Sep 6, 2015, at 3:43 PM, Nathan Van Gheem <<a href="x-msg://14/user/SendEmail.jtp?type=node&node=7574158&i=0" target="_top" rel="nofollow" link="external" class="">[hidden email]> wrote: >> >> Very nice work! >> >> What are your final goals for this project? Or is it more just a proof of concept on what you can do with plone.jsonapi.* ? >> >> Have you looked at Plone 5's folder contents? It seems like there are similar goals going on here and it'd be great to have your help on making Plone 5's folder contents even better. >> >> >> Cheers, >> Nathan >> >> On Sun, Sep 6, 2015 at 11:12 AM, Ramon Bartl <<a href="x-msg://14/user/SendEmail.jtp?type=node&node=7574158&i=1" target="_top" rel="nofollow" link="external" class="">[hidden email]> wrote: >> Hello Plone Commanders:) >> >> https://youtu.be/h9Bc37_eutE <https://youtu.be/h9Bc37_eutE> >> >> I am the developer of the plone.jsonapi.* packages and would like to >> introduce you today a new cross platform application, which is based on it >> — Plone Commander. >> >> I know that the developer mailing list is not the right place for such announcements… >> But since I just founded my own company 3 months ago, I wanted to use this chance >> to introduce my company as well to the community:) >> Feel free to contact me if you need support for great open source projects:) >> >> Btw.: It would be great if you share/tweet/blog the youtube link (only if you like it of course) >> or simply give me a thumb up on youtube:) >> >> Cheers Ramon >> >> -- >> Ramon Bartl >> Geschäftsführer / Managing Director >> >> Riding Bytes UG (haftungsbeschränkt) >> International Coding Company >> >> Mobile: <a href="tel:%2B49%20160%20555%2010%2008" value="+491605551008" target="_blank">+49 160 555 10 08 >> Web: www.ridingbytes.com <http://www.ridingbytes.com/> >> Email: <a href="x-msg://14/user/SendEmail.jtp?type=node&node=7574158&i=2" target="_top" rel="nofollow" link="external" class="">[hidden email] >> >> HRB 732278, Amtsgericht Ulm >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Plone-developers mailing list >> <a href="x-msg://14/user/SendEmail.jtp?type=node&node=7574158&i=3" target="_top" rel="nofollow" link="external" class="">[hidden email] >> https://lists.sourceforge.net/lists/listinfo/plone-developers <https://lists.sourceforge.net/lists/listinfo/plone-developers> >> >> >> >> >> -- >> Nathan Van Gheem >> Solutions Architect >> Wildcard Corp >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Plone-developers mailing list >> <a href="x-msg://14/user/SendEmail.jtp?type=node&node=7574158&i=4" target="_top" rel="nofollow" link="external" class="">[hidden email] >> https://lists.sourceforge.net/lists/listinfo/plone-developers <https://lists.sourceforge.net/lists/listinfo/plone-developers> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Plone-developers mailing list >> <a href="x-msg://14/user/SendEmail.jtp?type=node&node=7574158&i=5" target="_top" rel="nofollow" link="external" style="font-family: Helvetica; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">[hidden email] >> https://lists.sourceforge.net/lists/listinfo/plone-developers <https://lists.sourceforge.net/lists/listinfo/plone-developers> >> >> >> If you reply to this email, your message will be added to the discussion below: >> http://plone.293351.n2.nabble.com/Plone-Commander-tp7574155p7574158.html <http://plone.293351.n2.nabble.com/Plone-Commander-tp7574155p7574158.html> >> To start a new topic under Core Developers, email [hidden email] <x-msg://28/user/SendEmail.jtp?type=node&node=7574161&i=1> >> To unsubscribe from Plone, click here <applewebdata://7DE0695D-AC43-4F51-A360-9EAEDDE7EAF2>. >> NAML <http://plone.293351.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > > View this message in context: Re: Plone Commander <http://plone.293351.n2.nabble.com/Plone-Commander-tp7574155p7574161.html> > Sent from the Core Developers mailing list archive <http://plone.293351.n2.nabble.com/Core-Developers-f293355.html> at Nabble.com. > ------------------------------------------------------------------------------ > _______________________________________________ > Plone-developers mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-developers -- Ramon Bartl Dipl. Informatiker (FH) mail: ramon.bartl@googlemail. <mailto:ram...@ya...>com fon: +49 160 5551008 https://github.com/ramonski <https://github.com/ramonski> https://www.linkedin.com/in/ramonski <https://www.linkedin.com/in/ramonski> |
|
From: espen <es...@me...> - 2015-09-07 14:47:34
|
When (if) things are as smooth as that, some users might asume that they can drag/drop items into folders (?) > 6. sep. 2015 kl. 23.31 skrev T. Kim Nguyen-2 [via Plone] <ml-...@n2...>: > > I liked how quickly you could create new folders. The current Plone 5 folder contents still takes you to a standard add form that leaves you looking at the newly created object. +1 for your joining forces and improving Plone 5 even more! > > Kim > > > > On Sep 6, 2015, at 3:43 PM, Nathan Van Gheem <[hidden email] <x-msg://14/user/SendEmail.jtp?type=node&node=7574158&i=0>> wrote: > > Very nice work! > > What are your final goals for this project? Or is it more just a proof of concept on what you can do with plone.jsonapi.* ? > > Have you looked at Plone 5's folder contents? It seems like there are similar goals going on here and it'd be great to have your help on making Plone 5's folder contents even better. > > > Cheers, > Nathan > > On Sun, Sep 6, 2015 at 11:12 AM, Ramon Bartl <[hidden email] <x-msg://14/user/SendEmail.jtp?type=node&node=7574158&i=1>> wrote: > Hello Plone Commanders:) > > https://youtu.be/h9Bc37_eutE <https://youtu.be/h9Bc37_eutE> > > I am the developer of the plone.jsonapi.* packages and would like to > introduce you today a new cross platform application, which is based on it > — Plone Commander. > > I know that the developer mailing list is not the right place for such announcements… > But since I just founded my own company 3 months ago, I wanted to use this chance > to introduce my company as well to the community:) > Feel free to contact me if you need support for great open source projects:) > > Btw.: It would be great if you share/tweet/blog the youtube link (only if you like it of course) > or simply give me a thumb up on youtube:) > > Cheers Ramon > > -- > Ramon Bartl > Geschäftsführer / Managing Director > > Riding Bytes UG (haftungsbeschränkt) > International Coding Company > > Mobile: <a href="tel:%2B49%20160%20555%2010%2008" value="+491605551008" target="_blank">+49 160 555 10 08 > Web: www.ridingbytes.com <http://www.ridingbytes.com/> > Email: [hidden email] <x-msg://14/user/SendEmail.jtp?type=node&node=7574158&i=2> > > HRB 732278, Amtsgericht Ulm > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Plone-developers mailing list > [hidden email] <x-msg://14/user/SendEmail.jtp?type=node&node=7574158&i=3> > https://lists.sourceforge.net/lists/listinfo/plone-developers <https://lists.sourceforge.net/lists/listinfo/plone-developers> > > > > > -- > Nathan Van Gheem > Solutions Architect > Wildcard Corp > ------------------------------------------------------------------------------ > _______________________________________________ > Plone-developers mailing list > [hidden email] <x-msg://14/user/SendEmail.jtp?type=node&node=7574158&i=4> > https://lists.sourceforge.net/lists/listinfo/plone-developers <https://lists.sourceforge.net/lists/listinfo/plone-developers> > > ------------------------------------------------------------------------------ > > _______________________________________________ > Plone-developers mailing list > [hidden email] <x-msg://14/user/SendEmail.jtp?type=node&node=7574158&i=5> > https://lists.sourceforge.net/lists/listinfo/plone-developers <https://lists.sourceforge.net/lists/listinfo/plone-developers> > > > If you reply to this email, your message will be added to the discussion below: > http://plone.293351.n2.nabble.com/Plone-Commander-tp7574155p7574158.html <http://plone.293351.n2.nabble.com/Plone-Commander-tp7574155p7574158.html> > To start a new topic under Core Developers, email ml-...@n2... <mailto:ml-...@n2...> > To unsubscribe from Plone, click here <http://plone.293351.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=293351&code=ZXNwZW5AbWVkaWFsb2cubm98MjkzMzUxfC01OTUzNTQ2MjI=>. > NAML <http://plone.293351.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> -- View this message in context: http://plone.293351.n2.nabble.com/Plone-Commander-tp7574155p7574161.html Sent from the Core Developers mailing list archive at Nabble.com. |
|
From: Gauthier B. <gau...@im...> - 2015-09-07 12:47:35
|
Hi, this was just fixed : https://pypi.python.org/pypi/setuptools#downloads +++ PS: also you need a recent version of bootstrap.py so --setuptools-version is available. Gauthier Bastien <http://www.imio.be> Zoning industriel, 34 5190 Mornimont Tél: 0032(65)32 96 77 gau...@im... <mailto:gau...@im...> La mutualisation informatique au service des pouvoirs locaux Le 07/09/2015 13:36, Gil Forcada Codinachs a écrit : > Hi, > > I'm not sure if somebody already noticed it, but our (der Freitag) > jenkins server started to fail with setuptools 18.3 if it was not > pinned down when bootstraping, i.e.: > > python2.7 bootstrap.py -c buildout.cfg # fails > python2.7 bootstrap.py -c buildout.cfg --setuptools-version 18.2 # works > > Cheers, > Gil > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > Plone-developers mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-developers |
|
From: Gil F. C. <gfo...@gn...> - 2015-09-07 11:36:17
|
Hi, I'm not sure if somebody already noticed it, but our (der Freitag) jenkins server started to fail with setuptools 18.3 if it was not pinned down when bootstraping, i.e.: python2.7 bootstrap.py -c buildout.cfg # fails python2.7 bootstrap.py -c buildout.cfg --setuptools-version 18.2 # works Cheers, Gil |
|
From: T. K. N. <ng...@pl...> - 2015-09-06 21:30:31
|
I liked how quickly you could create new folders. The current Plone 5 folder contents still takes you to a standard add form that leaves you looking at the newly created object. +1 for your joining forces and improving Plone 5 even more!
Kim
On Sep 6, 2015, at 3:43 PM, Nathan Van Gheem <van...@gm...> wrote:
Very nice work!
What are your final goals for this project? Or is it more just a proof of concept on what you can do with plone.jsonapi.* ?
Have you looked at Plone 5's folder contents? It seems like there are similar goals going on here and it'd be great to have your help on making Plone 5's folder contents even better.
Cheers,
Nathan
> On Sun, Sep 6, 2015 at 11:12 AM, Ramon Bartl <ram...@go...> wrote:
> Hello Plone Commanders:)
>
> https://youtu.be/h9Bc37_eutE
>
> I am the developer of the plone.jsonapi.* packages and would like to
> introduce you today a new cross platform application, which is based on it
> — Plone Commander.
>
> I know that the developer mailing list is not the right place for such announcements…
> But since I just founded my own company 3 months ago, I wanted to use this chance
> to introduce my company as well to the community:)
> Feel free to contact me if you need support for great open source projects:)
>
> Btw.: It would be great if you share/tweet/blog the youtube link (only if you like it of course)
> or simply give me a thumb up on youtube:)
>
> Cheers Ramon
>
> --
> Ramon Bartl
> Geschäftsführer / Managing Director
>
> Riding Bytes UG (haftungsbeschränkt)
> International Coding Company
>
> Mobile: +49 160 555 10 08
> Web: www.ridingbytes.com
> Email: rb...@ri...
>
> HRB 732278, Amtsgericht Ulm
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Plone-developers mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-developers
--
Nathan Van Gheem
Solutions Architect
Wildcard Corp
------------------------------------------------------------------------------
_______________________________________________
Plone-developers mailing list
Plo...@li...
https://lists.sourceforge.net/lists/listinfo/plone-developers
|
|
From: Ramon B. <ram...@go...> - 2015-09-06 21:07:13
|
Hei Nathan, Thank you very much! It is basically a proof of concept of what is possible with plone.jsonapi and some testing with the new ExtJS 6 Framework. On the long run, I would like to have a mobile (phone) application for Plone, where you can manage Plone contents more efficient on such a device. This was also the main reason, why I started plone.jsonapi.* already 3 years ago;) This is actually the next planned milestone for Plone Commander, since ExtJS 6 offers a modern toolkit to address mobile devices with Apache Cordova. Until today I had only a quick look into Plone 5 to see if it is compatible with plone.jsonapi — yes, it is. But I will have a look into it tomorrow to see if I can help you to improve the folder contents behavior. Thanks again for the positive feedback Cheers Ramon > Am 06.09.2015 um 22:43 schrieb Nathan Van Gheem <van...@gm...>: > > Very nice work! > > What are your final goals for this project? Or is it more just a proof of concept on what you can do with plone.jsonapi.* ? > > Have you looked at Plone 5's folder contents? It seems like there are similar goals going on here and it'd be great to have your help on making Plone 5's folder contents even better. > > > Cheers, > Nathan > > On Sun, Sep 6, 2015 at 11:12 AM, Ramon Bartl <ram...@go... <mailto:ram...@go...>> wrote: > Hello Plone Commanders:) > > https://youtu.be/h9Bc37_eutE <https://youtu.be/h9Bc37_eutE> > > I am the developer of the plone.jsonapi.* packages and would like to > introduce you today a new cross platform application, which is based on it > — Plone Commander. > > I know that the developer mailing list is not the right place for such announcements… > But since I just founded my own company 3 months ago, I wanted to use this chance > to introduce my company as well to the community:) > Feel free to contact me if you need support for great open source projects:) > > Btw.: It would be great if you share/tweet/blog the youtube link (only if you like it of course) > or simply give me a thumb up on youtube:) > > Cheers Ramon > > -- > Ramon Bartl > Geschäftsführer / Managing Director > > Riding Bytes UG (haftungsbeschränkt) > International Coding Company > > Mobile: +49 160 555 10 08 <tel:%2B49%20160%20555%2010%2008> > Web: www.ridingbytes.com <http://www.ridingbytes.com/> > Email: rb...@ri... <mailto:rb...@ri...> > > HRB 732278, Amtsgericht Ulm > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Plone-developers mailing list > Plo...@li... <mailto:Plo...@li...> > https://lists.sourceforge.net/lists/listinfo/plone-developers <https://lists.sourceforge.net/lists/listinfo/plone-developers> > > > > > -- > Nathan Van Gheem > Solutions Architect > Wildcard Corp -- Ramon Bartl Dipl. Informatiker (FH) mail: ramon.bartl@googlemail. <mailto:ram...@ya...>com fon: +49 160 5551008 https://github.com/ramonski <https://github.com/ramonski> https://www.linkedin.com/in/ramonski <https://www.linkedin.com/in/ramonski> |
|
From: Nathan V. G. <van...@gm...> - 2015-09-06 20:43:10
|
Very nice work! What are your final goals for this project? Or is it more just a proof of concept on what you can do with plone.jsonapi.* ? Have you looked at Plone 5's folder contents? It seems like there are similar goals going on here and it'd be great to have your help on making Plone 5's folder contents even better. Cheers, Nathan On Sun, Sep 6, 2015 at 11:12 AM, Ramon Bartl <ram...@go...> wrote: > Hello Plone Commanders:) > > https://youtu.be/h9Bc37_eutE > > I am the developer of the plone.jsonapi.* packages and would like to > introduce you today a new cross platform application, which is based on it > — Plone Commander. > > I know that the developer mailing list is not the right place for such > announcements… > But since I just founded my own company 3 months ago, I wanted to use this > chance > to introduce my company as well to the community:) > Feel free to contact me if you need support for great open source > projects:) > > Btw.: It would be great if you share/tweet/blog the youtube link (only if > you like it of course) > or simply give me a thumb up on youtube:) > > Cheers Ramon > > -- > Ramon Bartl > Geschäftsführer / Managing Director > > Riding Bytes UG (haftungsbeschränkt) > International Coding Company > > Mobile: +49 160 555 10 08 > Web: www.ridingbytes.com > Email: rb...@ri... > > HRB 732278, Amtsgericht Ulm > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Plone-developers mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-developers > > -- Nathan Van Gheem Solutions Architect Wildcard Corp |
|
From: Ramon B. <ram...@go...> - 2015-09-06 16:12:31
|
Hello Plone Commanders:) https://youtu.be/h9Bc37_eutE I am the developer of the plone.jsonapi.* packages and would like to introduce you today a new cross platform application, which is based on it — Plone Commander. I know that the developer mailing list is not the right place for such announcements… But since I just founded my own company 3 months ago, I wanted to use this chance to introduce my company as well to the community:) Feel free to contact me if you need support for great open source projects:) Btw.: It would be great if you share/tweet/blog the youtube link (only if you like it of course) or simply give me a thumb up on youtube:) Cheers Ramon -- Ramon Bartl Geschäftsführer / Managing Director Riding Bytes UG (haftungsbeschränkt) International Coding Company Mobile: +49 160 555 10 08 Web: www.ridingbytes.com <http://www.ridingbytes.com/> Email: rb...@ri... <mailto:rb...@ri...> HRB 732278, Amtsgericht Ulm |
|
From: Johannes R. <rag...@ad...> - 2015-09-05 02:08:57
|
I'd prefer to have the core-patterns bundled within the mockup repository and other than that, one repository per mockup-addon. Like patternslib is doing it. AFAIK, extra mockup-addons can be easily added to Plone and compiled through the web with the new resource registry. For precompiling or using it outside Plone, one would need a meta package, which configures grunt and requirejs properly. On Fri, 2015-09-04 at 21:01 +0000, Dominik Ruf wrote: > Nathan Van Gheem <vangheem@...> writes: > > > > > > > mockup-extra would probably better be in the collective. > > It seems to me like it'd make sense to create a new package in the > collective for it. > > OK should I create a new repository in collective for this? > How should I call it? > > For now I have created my own repository based on mockup > -minimalpatterns > > https://github.com/domruf/mockup-mypatterns > > you can see the demo here > http://domruf.github.io/mockup-mypatterns/ > > > > > > > On Tue, Aug 25, 2015 at 9:32 AM, Dominik Ruf <dominikruf- > Re5...@pu...> wrote:Hi, > > recently the tablesorter pattern has been removed from the mockup > > repository. (see https://github.com/plone/mockup/pull/540) > > One comment suggested it could live on as an addon. > > That let me wonder, where do/should non core mockup patterns live? > > If foundhttps://github.com/plone/mockup-extra > > but it doesn't seem to be used anymore. > > Or should I create my own repository based > onhttps://github.com/collective/mockup-minimalpattern > > and share it in https://github.com/collective? > > The tutorial onhttp://plone.github.io/mockup/dev/#learn > > tells you to create new patterns directly in the mockup > > environment. > > But if the mockup repository is only meant for plone core patterns, > > that > > doesn't seem to be practical to me. > > Wouldn't it be better if the tutorial were based > onhttps://github.com/collective/mockup-minimalpattern ? > > cheers > > Dominik |
|
From: Dominik R. <dom...@gm...> - 2015-09-04 21:01:36
|
Nathan Van Gheem <vangheem@...> writes: > > > mockup-extra would probably better be in the collective. > It seems to me like it'd make sense to create a new package in the collective for it. OK should I create a new repository in collective for this? How should I call it? For now I have created my own repository based on mockup-minimalpatterns https://github.com/domruf/mockup-mypatterns you can see the demo here http://domruf.github.io/mockup-mypatterns/ > > > On Tue, Aug 25, 2015 at 9:32 AM, Dominik Ruf <dominikruf- Re5...@pu...> wrote:Hi, > recently the tablesorter pattern has been removed from the mockup > repository. (see https://github.com/plone/mockup/pull/540) > One comment suggested it could live on as an addon. > That let me wonder, where do/should non core mockup patterns live? > If foundhttps://github.com/plone/mockup-extra > but it doesn't seem to be used anymore. > Or should I create my own repository based onhttps://github.com/collective/mockup-minimalpattern > and share it in https://github.com/collective? > The tutorial onhttp://plone.github.io/mockup/dev/#learn > tells you to create new patterns directly in the mockup environment. > But if the mockup repository is only meant for plone core patterns, that > doesn't seem to be practical to me. > Wouldn't it be better if the tutorial were based onhttps://github.com/collective/mockup-minimalpattern ? > cheers > Dominik > ------------------------------------------------------------------------- ----- > _______________________________________________ > Plone-developers mailing listPlone-developers <at> lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/plone- developers > > > -- Nathan Van GheemSolutions Architect > Wildcard Corp > > > > > ------------------------------------------------------------------------- ----- > > > _______________________________________________ > Plone-developers mailing list > Plone-developers@... > https://lists.sourceforge.net/lists/listinfo/plone-developers > |
|
From: Eric S. <es...@pl...> - 2015-09-03 01:35:38
|
Status update: # Blockers ## Needs love: * [Dexterity field model editor (ace) broken :: Issue #826](https://github.com/plone/Products.CMFPlone/issues/826) * [Styles for plone.app.discussion need some love :: Issue #764](https://github.com/plone/Products.CMFPlone/issues/764) * [@@historyview publicly visible :: Issue #739](https://github.com/plone/Products.CMFPlone/issues/739) and [History view / document by line :: Issue #828](https://github.com/plone/Products.CMFPlone/issues/828) * [Building LESS files from theme editor issues :: Issue #705](https://github.com/plone/Products.CMFPlone/issues/705) * [Plone 5 i18n issues :: Issue #379](https://github.com/plone/Products.CMFPlone/issues/379) * [Use plone lock settings from editing-controlpanel :: Issue #345](https://github.com/plone/Products.CMFPlone/issues/345) * [Remove portal_properties Tool. :: Issue #125](https://github.com/plone/Products.CMFPlone/issues/125) * [p.a.controlpanel migration doesn't copy p.a.multilingual settings yet :: Issue #145](https://github.com/plone/Products.CMFPlone/issues/145)= * [missing display_pub_date_in_byline in ISite controlpanel :: Issue #346](https://github.com/plone/Products.CMFPlone/issues/346) * Clean out portal_skins. There are a number of no-longer-referenced items in there that should be removable at this point. ## In progress: * plone.api * "1.3.2 released. Would be good to have https://github.com/plone/plone.api/issues/204 resolved before shipping with Plone core" * [Bump to Zope 2.13.23](https://github.com/plone/buildout.coredev/pull/99) * Tests pass. May need more work for updated pytz, testrunner support. * [Remove global_defines :: Issue #836](https://github.com/plone/Products.CMFPlone/issues/836) * [Bump to lxml 3.x: :: Issue #857](https://github.com/plone/Products.CMFPlone/issues/857) ## Closed: * [@@manage-viewlets is defective](https://github.com/plone/Products.CMFPlone/issues/782). Thanks, Philip! * [plone.app.users upgrade step does not disappear :: Issue #719](https://github.com/plone/Products.CMFPlone/issues/719). Thanks, Maurits! * [No default table styles when using TinyMCE :: Issue #755](https://github.com/plone/Products.CMFPlone/issues/755). Thanks, Nathan! |
|
From: Tom G. <itc...@gm...> - 2015-09-02 19:04:54
|
On 20.08.15 14:37, Maurits van Rees wrote: > - QI is an alternative installation system, with Extensions/Install.py. > Products depending on this would need to be changed to use GS. In the > basis this is not hard. I expect any product that was created for Plone > 3 or higher to have a GS profile. That is not true for every case: https://github.com/plone/Products.CMFPlone/issues/527 -- Author of the book "Plone 3 Multimedia" - http://amzn.to/dtrp0C Tom Gross email..........itc...@gm... skype.....................tom_gross web.........http://toms-projekte.de blog...http://blog.toms-projekte.de |
|
From: Maurits v. R. <m.v...@ze...> - 2015-08-27 00:05:43
|
Eric Steele schreef op 25-08-15 om 13:49: > * plone.app.users upgrade step does not disappear · Issue #719 > <https://github.com/plone/Products.CMFPlone/issues/719> This is already fixed in Plone 5.0b4. > * Bump to Zope 2.13.23. I need to reexamine the versions for these. > Tres has rearranged the latest KGS and things are missing or aren't > where they used to be. Jens created a pull request for this a while ago: https://github.com/plone/buildout.coredev/pull/99 But it has test failures: http://jenkins.plone.org/job/pull-request-5.0/220/ Looks like mostly stuff to do with dates. Ideas welcome. Note that I have opened a similar pull request, with similar problems, for Plone 4.3: https://github.com/plone/buildout.coredev/pull/100 -- Maurits van Rees: http://maurits.vanrees.org/ Zest Software: http://zestsoftware.nl |
|
From: Eric S. <es...@pl...> - 2015-08-26 20:13:14
|
Thanks, gents. 5.0b4 has been released. On 25 Aug 2015, at 7:16, Eric Steele wrote: > 5.0b4 is ready for testing at = > > http://dist.plone.org/release/5.0b4-pending/versions.cfg > > > > > ## Changelog: > > docutils: 0.9.1 -> 0.12 > ---------------------- > > plone.recipe.zope2instance: 4.2.17 -> 4.2.18 > ------------------------------------------- > - Allow to disable logs. Set ``z2-log`` to the value ``disable`` to > disable the Z2 access log. Set ``event-log`` to the value > ``disable`` to disable the event log. > [frapell] > > > > setuptools: 5.8 -> 18.0.1 > ------------------------ > > zc.buildout: 2.2.5 -> 2.4.0 > -------------------------- > > Pygments: 1.6 -> 2.0.2 > --------------------- > > Plone: 5.0b3 -> 5.0b4 > -------------------- > - Release Plone 5.0b4 > [esteele] > > > > Products.CMFDiffTool: 3.0.1 -> 3.0.2 > ----------------------------------- > - Fixed UnicodeDecodeError in dump/ndiff. > Issue https://github.com/plone/Products.CMFPlone/issues/820 > [maurits] > > - Provide diff for dexterity behaviors' fields. > [cedricmessiant] > > - Fix bug with encoding in TextDiff. > [cedricmessiant] > > > > Products.CMFDynamicViewFTI: 4.1.2 -> 4.1.3 > ----------------------------------------- > - Cleanup: PEP8 et al., security/zca via decorators, ... > [jensens] > > > > Products.CMFEditions: 2.2.13 -> 2.2.14 > ------------------------------------- > - Do not call ndiff unless there is no html_diff. Removed strange > unicode space from template. Related to > https://github.com/plone/Products.CMFPlone/issues/820 > [maurits] > > > > Products.CMFPlone: 5.0b3 -> 5.0b4 > -------------------------------- > - fix #350: "plone.app.content circular dependency on Products.CMFPlone" = > > - this > fixes the imports only, not on zcml/genericsetup level. > [jensens] > > - move Plone specific ``getDefaultPage`` (magic) code from = > > plone.app.layout > over to Products.CMFPlone. This avoids a circular dependency. Also = > > its > not really layout only related code. > [jensens] > > - Fix add-ons to be installed using CMFQuickInstaller (restore support > for Extensions/Install.py) > [datakurre] > > - Rename showEditableBorder to showToolbar and deprecate using > disable_border and enable_border for enable_toolbar and = > > disable_toolbar > [vangheem] > > - Not using less variables in toolbar everywhere > [vangheem] > > - Fix link to documentation > > - Rework timezone selection in @@plone-addsite. > [jaroel] > > - Rework language selection in @@plone-addsite. > [jaroel] > > - Turn @@tinymce-controlpanel ``content_css`` field into a list, so we = > > can add > several CSS URLs (useful when add-ons need to provide extra TinyMCE = > > styles), > and fix TinyMCE config getter so it considers the ``content_css`` = > > value. > [ebrehault] > > > > Products.CMFQuickInstallerTool: 3.0.9 -> 3.0.11 > ---------------------------------------------- > - Fixed getting profiles registered explicitly for ``IPloneSiteRoot`` > instead CMFCore ``ISiteRoot``. Bug introduced in 3.0.10. See for > example https://github.com/plone/plone.app.mosaic/issues/124 > [maurits] > > > - Cleanup: PEP8, decorators for security+zca, et al. > [jensens] > > > > Products.GenericSetup: 1.7.5 -> 1.7.7 > ------------------------------------ > - Fix: when the last applied upgrade step had a checker, the profile > version was not updated. Now we no longer look at the checker of > the last applied step when deciding whether to set the profile > version. The checker, if any is set, normally returns True before > running the step (it can be applied), and False afterwards (it > was already applied). > > - Add ``upgradeProfile`` method to setup tool. This method applies all > upgrades steps for the given profile, or updates it to the optional > given version. If the profile does not exist, or if there is no = > > upgrade > step to go to the specified version, the method warns and does = > > nothing. > > - Check the boolean value of the ``remove`` option when importing > objects. Previously we only checked if the ``remove`` option was > given, regardless of its value. Supported are ``True``, ``Yes``, > and ``1``, where case does not matter. The syntax for removing > objects, properties, and elements is now the same. > > - Support ``remove=3D"True"`` for properties. > > > - Enable testing under Travis. > > - Fix compatibility with Setuptools 8.0 and later. Upgrade steps > could get sorted in the wrong order, especially an empty version > string (upgrade step from any source version) sorted last instead of > first. > > > > Products.PortalTransforms: 2.1.7 -> 2.1.8 > ---------------------------------------- > - fix error mis-configured transforms would cause: > "AttributeError: 'NoneType' object has no attribute 'items'" > [vangheem] > > > > mockup: 2.0.5 -> 2.0.6 > --------------------- > > plone.app.blob: 1.5.14 -> 1.5.16 > ------------------------------- > - Fix migrator for AT-based types that got broken in 1.5.8 release and = > > add > an option to remove the content of the non-blob field during = > > migration to > not end up having stale data in the ZODB > [fRiSi] > > > - fix permission for download > [david-batranu] > > > > plone.app.content: 3.0.7 -> 3.0.9 > -------------------------------- > - Respect view-action (e.g. for files and image) in rename, copy and = > > cut. > Fixes https://github.com/plone/Products.CMFPlone/issues/829 > [pbauer] > > > - Added basic test for folder contents "rearrange" and "item order" = > > features. > Minor restructuring of actions in own files to have a consistent = > > structure > (bbb imports in place). Minor changes in touched area regarding pep8, > code-analysis, et al. > [jensens] > > - Do not setDefaultPage in rename handler, there is already an = > > subscriber that > do so in `Products.CMFDynamicViewFTI`. > [jensens] > > - Do not clear clipboard when pasting content > [vangheem] > > - Fix i18n of '"title" has already been deleted'. > > - When clicking cancel on the delete_confirmation got to the view_url. > [ale-rt] > > - Fix deletion of objects with unicode charaters in the title. > [cillianderoiste] > > > > plone.app.contentmenu: 2.1.5 -> 2.1.6 > ------------------------------------ > - Fix: Permission check ``ManageWorkflowPolicies`` was always on = > > fallback to > ``ManagerPortal``. Now checks the correct permission after using the > pkg_resources.get_distribution api for checking (never catch an = > > ImportError). > [jensens] > > - pep8, zca decorators, plone code conventions > [jensens] > > - do not open manage portlets in a modal > [vangheem] > > > > plone.app.contenttypes: 1.2b3 -> 1.2b4 > ------------------------------------- > - Test Creator criterion with Any selection. > [mvanrees] > > - Selection criterion converter: allow selection.is alternative = > > operation. > [mvanrees] > > - Fixed corner case in topic migration. > [mvanrees] > > - Use event_listung for /events/aggregator in new sites. > [pbauer] > > - Remove obsolete collections.css > [pbauer] > > - Add plone.app.querystring as a dependency (fixes collections migrated = > > to p5 > and dexterity). > [pbauer] > > - Migrate layout of portal to use the new listing-views when migrating = > > to dx. > [pbauer] > > - Migrate layout using the new listing-views when migrating folders, > collections, topics. > [pbauer] > > - Update allowed view_methods of the site-root on installing or = > > migrating. > Fixes #25. > [pbauer] > > - Set default_view when updating view_methods. Fixes #250. > [pbauer] > > - Fix bug in reference-migrations where linkintegrity-relations were = > > turned > into relatedItems. > [pbauer] > > - Setup calendar and visible ids even when no default-content gets = > > created. > [pbauer] > > - Remove upgrade-step that resets all behaviors. Fixes #246. > [pbauer] > > - Add convenience-view @@export_all_relations to export all relations. > [pbauer] > > - Add method link_items that allows to link any kind of item (AT/DX) = > > with any > kind of relationship. > [pbauer] > > - New implementation of reference-migrations. > [pbauer] > > - Fix i18n on custom_migration view. > [vincentfretin] > > > > plone.app.dexterity: 2.1.7 -> 2.1.8 > ---------------------------------- > - Avoid ``DeprecationWarning`` for ``getIcon`` and ``splitSchemaName``. > [maurits] > > > > plone.app.event: 2.0b1 -> 2.0b2 > ------------------------------ > - Unified event_listing style with plonetheme.barceloneta styles and = > > added svg > icons. > [agitator] > > - initialize events.js javascript after all patterns are initialized. > [garbas] > > - removing dependency on plone.app.contenttypes that introduce with = > > latest > changes to portlets code. > [garbas] > > > > plone.app.iterate: 3.1.0 -> 3.1.1 > -------------------------------- > - Check if object does not have iterate policy. This fixes > iterate causing toolbar errors on portal root. > [vangheem] > > > > plone.app.layout: 2.5.9 -> 2.5.10 > -------------------------------- > - Correctly display selected item in global navigation for images and = > > files. > Fixes https://github.com/plone/Products.CMFPlone/issues/830 > [pbauer] > > - Add view url to document as data-view-url > [ale-rt] > > - If toolbar logo is empty, use default > [vangheem] > > - Move getDefaultPage, isDefaultPage, IDefaultPage and DefaultPage view = > > to > Products.CMFPlone in order to avoid circular imports between both = > > packages. > Moved test for it as well. Placed deferred deprecated imports for all = > > old > names here. > [jensens] > > - Remove deprecated ``context`` parameter from ``DefaultPage`` methods. > [jensens] > > - minor cleanup in getDefaultPage function > [jensens] > > - Added a test for the complex getDefaultPage function > [jensens] > > > plone.app.querystring: 1.3.3 -> 1.3.6 > ------------------------------------ > > - Fix migration from Plone 4 to Plone 5. > [pbauer] > > - Creator criteria: pur currentUser on top. > [mvanrees] > > - Migrate Creator string.is to selection.any. > [mvanrees] > > - add user vocabulary to plone.app.querystring.field.Creator. > [vangheem] > > - do not need "is" when there is an "any" operator. > [vangheem] > > > - Hide upgrade-profiles when creating a new site. > [pbauer] > > - Replace selection.is with selection.any for portal_types and = > > review_state > operations, and add selection.any for Creator operation. > [frapell] > > - Actually convert the value to a datetime for the DateIndex query = > > modifier. > [frapell] > > - Do not fail if the 'Between' operation is called with an empty value, = > > and > instead return a list with 2 empty values. > [frapell] > > - Fixed possible problem with ``custom_query`` parameter where > theoretically a second invocation could inadvertently be using the > value from the first invocation. > [maurits] > > > > plone.app.redirector: 1.2.1 -> 1.3 > --------------------------------- > - Rerelease of 1.2.1 as 1.3 for clarity. This is for Plone 5 only. > [maurits] > > > - Rerelease of same code as 1.2. The changes from 1.2.1 are for Plone = > > 5. > [maurits] > > > > plone.app.registry: 1.3.1 -> 1.3.2 > --------------------------------- > - Added the `structure` keyword to the TALES expression that returns the = > > description for registry entries. > This ensures that descriptions are properly escaped and HTML entities = > > don't show up in descriptions. > [pigeonflight] > > > > plone.app.testing: 5.0b5 -> 5.0b6 > -------------------------------- > - No need for unittest2. > [gforcada] > > > > plone.app.theming: 1.2.7 -> 1.2.9 > -------------------------------- > - Build thememapper resources. > [vangheem] > > - Added cache invalidation option. > [swartz] > > > - change link from plone.org to plone.com. > [tkimnguyen] > > - fix toolbar on control panel > [vangheem] > > - fix less building > [obct537] > > - Fixed copy modal for themes with a dot in the name. > [Gagaro] > > > > plone.app.upgrade: 1.3.12 -> 1.3.13 > ---------------------------------- > - Unregister removed collection.css. > [pbauer] > > - 5.0 beta: do not set ``url_expr`` on configlet. This must be done > with ``setActionExpression``. > Fixes https://github.com/plone/Products.CMFPlone/issues/814 > [maurits] > > - Turn @@tinymce-controlpanel ``content_css`` field into a list > [ebrehault] > > > > plone.app.users: 2.3 -> 2.3.1 > ---------------------------- > - Gave upgrade step destination 1. With the previous destination '*' > the upgrade step was always offered. > [vanrees] > > - Cache schemas in volatile attributes on portal. > [gotcha] > > - Package cleanup. > [gotcha] > > - Disable toolbar buttons on personal preferences > [vangheem] > > - Remove extra spaces in userschema.xml messages to avoid i18n = > > extraction > warnings. > [vincentfretin] > > > > plone.app.vocabularies: 2.1.18 -> 2.1.20 > --------------------------------------- > - Cleanup: PEP8, decorators for zca, et al. Also pimped the README. > [jensens] > > > - Fixed SyndicatableFeedItems to allow unicode characters in objects = > > titles. > [Gagaro] > > > plone.dexterity: 2.3.2 -> 2.3.4 > ------------------------------ > - Avoid our own DeprecationWarning about portalTypeToSchemaName. > [maurits] > > > - Check add_permission before checking constrains. Refs #37 > [jaroel] > > - Remove obsolete css-class and text from statusmessages. > [pbauer] > > > > plone.folder: 1.0.5 -> 1.0.7 > --------------------------- > - Depend on ``Products.CMFCore`` and remove fake-cmf, because this = > > confuses > more than it helps to reduce complexcity. > [jensens] > > - Cleanup: PEP8 and do not use ``id`` built-in as identifier. > [jensens] > > > - Whitespace cleanup, git ignores, cleanup package info. > [gforcada, rnixx, maurits] > > > > plone.namedfile: 3.0.2 -> 3.0.3 > ------------------------------ > - Don't fail, when accessing the ``tag`` method of the ``@@images`` = > > view, if > ``scale`` returns ``None``. > [thet] > > > > plone.resourceeditor: 2.0.0 -> 2.0.1 > ----------------------------------- > - Added ability to convert absolute to relative urls > [obct537] > > - Fixed issue with ascii encoding > [obct537] > > - now properly serves filesystem files to the thememapper > [obct537] > > - resourceeditor will now register non-standard mimetypes in the python > mimetype module > [obct537] > > > > plone.session: 3.5.5 -> 3.5.6 > ---------------------------- > - Cleanup: Pep8, plone style conventions, better readbility. > [jensens] > > > > plone.subrequest: 1.6.9 -> 1.6.10 > -------------------------------- > - propagate registered safe writes from plone.protect to parent request = > > object. > [vangheem] > > > > plone.testing: 4.0.13 -> 4.0.15 > ------------------------------ > - Prevent exception masking in finally clause of zopeApp context > [do3cc] > > > - Rerelease for clarity due to double release of 4.0.13. > [maurits] > > - Added ``multiinit``-parameter to z2.installProduct > to allow multiple initialize methods for a package > [tomgross] > > > > plonetheme.barceloneta: 1.6.8 -> 1.6.9 > ------------------------------------- > - Hide searchbox, personaltools, breadcrumbs in print.css > [gomez] > > - Updated font-weight on portlet headers > [pigeonflight] > > - Update font-weight on portlet management items > [vangheem] > > - Updated to index.html: link to plone.com opens in new window/tab > [tkimnguyen] > > > > plone.app.multilingual: 3.0.4 -> 3.0.6 > ------------------------------------- > - Rerelease due to possible brown bag release. Jenkins complains > about 3.0.5. > [maurits] > > > - Move @@multilingual-selector registration from PloneRoot to Navigation = > > root > This allows to hide language folders in nginx and to use different = > > domains. > [do3cc] > > - Update Traditional Chinese translation. > [l34marr] > > > plone.app.blocks: 2.1.0 -> 2.1.2 > ------------------------------- > > > plone.app.drafts: 1.0b1 -> 1.0b3 > ------------------------------- |
|
From: Dylan J. <dj...@pr...> - 2015-08-26 17:58:53
|
Hi, I’d really like to somehow get this in as I think it’s strategically important we make theming as easy as we can. https://github.com/plone/buildout.coredev/blob/47d8e78ed08a596a5209d1fbae7b7055fe2245fc/plips/plip-20154-easy-backend-theming.cfg It is about making it much easier to theme a site by having an out of the box way to not have to theme the backend UI such as site setup and edit etc. Also to help isolate the frontend theme to minimize the risk of js/css clashes. This code introduces a new body tag of viewpermission-X to differentiate from front vs back, and a set of rules that can be included into your custom theme from barceloneta. This should also be demonstrated in the example theme. Based on this original PLIP - https://dev.plone.org/ticket/20154 and discussion in https://github.com/plone/Products.CMFPlone/issues/465 > On 25 Aug 2015, at 6:49 pm, Eric Steele <es...@pl...> wrote: > > First of all, thank you all for putting in such an epic amount of work > on Plone 5. It's really close now and I think we can wrap it up with one > last push. > > Here's what's on my shortlist for release candidate status: > > • Dexterity field model editor (ace) broken · Issue #826 > • @@manage-viewlets is defective > • Styles for plone.app.discussion need some love · Issue #764 > • @@historyview publicly visible · Issue #739 and History view / document by line · Issue #828 > • plone.app.users upgrade step does not disappear · Issue #719 > • Building LESS files from theme editor issues · Issue #705 > • Plone 5 i18n issues · Issue #379 > • use plone lock settings from editing-controlpanel · Issue #345 > • Remove portal_properties Tool. · Issue #125 > • p.a.controlpanel migration doesn't copy p.a.multilingual settings yet · Issue #145 > • missing display_pub_date_in_byline in ISite controlpanel · Issue #346 > • Remove global_defines · Issue #836 > • No default table styles when using TinyMCE · Issue #755 > • plone.api? What's our status on this one? > • Bump to Zope 2.13.23. I need to reexamine the versions for these. Tres has rearranged the latest KGS and things are missing or aren't where they used to be. > • I'd like to jump to current versions of lxml (currently using one released in 2011). This would be the best time to do that. > • Clean out portal_skins. There are a number of no-longer-referenced items in there that should be removable at this point. > I'd like to try to get these wrapped up by the end of next week. > > Have I missed any glaring issues at this point? > > Eric > > ------------------------------------------------------------------------------ > _______________________________________________ > Plone-developers mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-developers |
|
From: Steve M. <st...@dc...> - 2015-08-25 21:26:01
|
The installer builds cleanly. :) On Tue, Aug 25, 2015 at 4:49 AM, Philip Bauer <ba...@st...> wrote: > Thanks. Looking good so far. I migrated a small page from 4.3.6 to 5.0b4 > and then from AT to DX. > > Philip > > -- > Starzel.de > Philip Bauer > Schleißheimer Straße 23 > 80333 München > Tel: 089 - 189 29 533 > ba...@st... > www.starzel.de > > > Am 25.08.2015 um 13:16 schrieb Eric Steele <es...@pl...>: > > > > 5.0b4 is ready for testing at = > > > > http://dist.plone.org/release/5.0b4-pending/versions.cfg > > > > Changelog: > > > > docutils: 0.9.1 -> 0.12 > > > > plone.recipe.zope2instance: 4.2.17 -> 4.2.18 > > > > • Allow to disable logs. Set z2-log to the value disable to > disable the Z2 access log. Set event-log to the value disable to disable > the event log. [frapell] > > setuptools: 5.8 -> 18.0.1 > > > > zc.buildout: 2.2.5 -> 2.4.0 > > > > Pygments: 1.6 -> 2.0.2 > > > > Plone: 5.0b3 -> 5.0b4 > > > > • Release Plone 5.0b4 [esteele] > > Products.CMFDiffTool: 3.0.1 -> 3.0.2 > > > > • Fixed UnicodeDecodeError in dump/ndiff. > > Issue https://github.com/plone/Products.CMFPlone/issues/820 > > [maurits] > > > > • Provide diff for dexterity behaviors' fields. > > [cedricmessiant] > > > > • Fix bug with encoding in TextDiff. > > [cedricmessiant] > > > > Products.CMFDynamicViewFTI: 4.1.2 -> 4.1.3 > > > > • Cleanup: PEP8 et al., security/zca via decorators, ... [jensens] > > Products.CMFEditions: 2.2.13 -> 2.2.14 > > > > • Do not call ndiff unless there is no html_diff. Removed strange > unicode space from template. Related to > https://github.com/plone/Products.CMFPlone/issues/820 [maurits] > > Products.CMFPlone: 5.0b3 -> 5.0b4 > > > > • fix #350: "plone.app.content circular dependency on > Products.CMFPlone" = > > > > • this > > fixes the imports only, not on zcml/genericsetup level. > > [jensens] > > > > • move Plone specific getDefaultPage (magic) code from = > > > > plone.app.layout > > over to Products.CMFPlone. This avoids a circular dependency. Also = > > > > its > > not really layout only related code. > > [jensens] > > > > • Fix add-ons to be installed using CMFQuickInstaller (restore > support > > for Extensions/Install.py) > > [datakurre] > > > > • Rename showEditableBorder to showToolbar and deprecate using > > disable_border and enable_border for enable_toolbar and = > > > > disable_toolbar > > [vangheem] > > > > • Not using less variables in toolbar everywhere > > [vangheem] > > > > • Fix link to documentation > > > > • Rework timezone selection in @@plone-addsite. > > [jaroel] > > > > • Rework language selection in @@plone-addsite. > > [jaroel] > > > > • Turn @@tinymce-controlpanel content_css field into a list, so we > = > > > > can add > > several CSS URLs (useful when add-ons need to provide extra TinyMCE = > > > > styles), > > and fix TinyMCE config getter so it considers the content_css = > > > > value. > > [ebrehault] > > > > Products.CMFQuickInstallerTool: 3.0.9 -> 3.0.11 > > > > • Fixed getting profiles registered explicitly for IPloneSiteRoot > > instead CMFCore ISiteRoot. Bug introduced in 3.0.10. See for > > example https://github.com/plone/plone.app.mosaic/issues/124 > > [maurits] > > > > • Cleanup: PEP8, decorators for security+zca, et al. > > [jensens] > > > > Products.GenericSetup: 1.7.5 -> 1.7.7 > > > > • Fix: when the last applied upgrade step had a checker, the > profile > > version was not updated. Now we no longer look at the checker of > > the last applied step when deciding whether to set the profile > > version. The checker, if any is set, normally returns True before > > running the step (it can be applied), and False afterwards (it > > was already applied). > > > > • Add upgradeProfile method to setup tool. This method applies all > > upgrades steps for the given profile, or updates it to the optional > > given version. If the profile does not exist, or if there is no = > > > > upgrade > > step to go to the specified version, the method warns and does = > > > > nothing. > > > > • Check the boolean value of the remove option when importing > > objects. Previously we only checked if the remove option was > > given, regardless of its value. Supported are True, Yes, > > and 1, where case does not matter. The syntax for removing > > objects, properties, and elements is now the same. > > > > • Support remove=3D"True" for properties. > > > > • Enable testing under Travis. > > > > • Fix compatibility with Setuptools 8.0 and later. Upgrade steps > > could get sorted in the wrong order, especially an empty version > > string (upgrade step from any source version) sorted last instead of > > first. > > > > Products.PortalTransforms: 2.1.7 -> 2.1.8 > > > > • fix error mis-configured transforms would cause: > "AttributeError: 'NoneType' object has no attribute 'items'" [vangheem] > > mockup: 2.0.5 -> 2.0.6 > > > > plone.app.blob: 1.5.14 -> 1.5.16 > > > > • Fix migrator for AT-based types that got broken in 1.5.8 release > and = > > add > > an option to remove the content of the non-blob field during = > > > > migration to > > not end up having stale data in the ZODB > > [fRiSi] > > > > • fix permission for download [david-batranu] > > plone.app.content: 3.0.7 -> 3.0.9 > > > > • Respect view-action (e.g. for files and image) in rename, copy > and = > > cut. > > Fixes https://github.com/plone/Products.CMFPlone/issues/829 > > [pbauer] > > > > • Added basic test for folder contents "rearrange" and "item > order" = > > features. > > Minor restructuring of actions in own files to have a consistent = > > > > structure > > (bbb imports in place). Minor changes in touched area regarding pep8, > > code-analysis, et al. > > [jensens] > > > > • Do not setDefaultPage in rename handler, there is already an = > > subscriber that > > do so in Products.CMFDynamicViewFTI. > > [jensens] > > > > • Do not clear clipboard when pasting content > > [vangheem] > > > > • Fix i18n of '"title" has already been deleted'. > > > > • When clicking cancel on the delete_confirmation got to the > view_url. > > [ale-rt] > > > > • Fix deletion of objects with unicode charaters in the title. > > [cillianderoiste] > > > > plone.app.contentmenu: 2.1.5 -> 2.1.6 > > > > • Fix: Permission check ManageWorkflowPolicies was always on = > > fallback to > > ManagerPortal. Now checks the correct permission after using the > > pkg_resources.get_distribution api for checking (never catch an = > > > > ImportError). > > [jensens] > > > > • pep8, zca decorators, plone code conventions > > [jensens] > > > > • do not open manage portlets in a modal > > [vangheem] > > > > plone.app.contenttypes: 1.2b3 -> 1.2b4 > > > > • Test Creator criterion with Any selection. > > [mvanrees] > > > > • Selection criterion converter: allow selection.is alternative = > > > > operation. > > [mvanrees] > > > > • Fixed corner case in topic migration. > > [mvanrees] > > > > • Use event_listung for /events/aggregator in new sites. > > [pbauer] > > > > • Remove obsolete collections.css > > [pbauer] > > > > • Add plone.app.querystring as a dependency (fixes collections > migrated = > > > > to p5 > > and dexterity). > > [pbauer] > > > > • Migrate layout of portal to use the new listing-views when > migrating = > > to dx. > > [pbauer] > > > > • Migrate layout using the new listing-views when migrating > folders, > > collections, topics. > > [pbauer] > > > > • Update allowed view_methods of the site-root on installing or = > > > > migrating. > > Fixes #25. > > [pbauer] > > > > • Set default_view when updating view_methods. Fixes #250. > > [pbauer] > > > > • Fix bug in reference-migrations where linkintegrity-relations > were = > > > > turned > > into relatedItems. > > [pbauer] > > > > • Setup calendar and visible ids even when no default-content gets > = > > created. > > [pbauer] > > > > • Remove upgrade-step that resets all behaviors. Fixes #246. > > [pbauer] > > > > • Add convenience-view @@export_all_relations to export all > relations. > > [pbauer] > > > > • Add method link_items that allows to link any kind of item > (AT/DX) = > > > > with any > > kind of relationship. > > [pbauer] > > > > • New implementation of reference-migrations. > > [pbauer] > > > > • Fix i18n on custom_migration view. > > [vincentfretin] > > > > plone.app.dexterity: 2.1.7 -> 2.1.8 > > > > • Avoid DeprecationWarning for getIcon and splitSchemaName. > [maurits] > > plone.app.event: 2.0b1 -> 2.0b2 > > > > • Unified event_listing style with plonetheme.barceloneta styles > and = > > added svg > > icons. > > [agitator] > > > > • initialize events.js javascript after all patterns are > initialized. > > [garbas] > > > > • removing dependency on plone.app.contenttypes that introduce > with = > > > > latest > > changes to portlets code. > > [garbas] > > > > plone.app.iterate: 3.1.0 -> 3.1.1 > > > > • Check if object does not have iterate policy. This fixes iterate > causing toolbar errors on portal root. [vangheem] > > plone.app.layout: 2.5.9 -> 2.5.10 > > > > • Correctly display selected item in global navigation for images > and = > > files. > > Fixes https://github.com/plone/Products.CMFPlone/issues/830 > > [pbauer] > > > > • Add view url to document as data-view-url > > [ale-rt] > > > > • If toolbar logo is empty, use default > > [vangheem] > > > > • Move getDefaultPage, isDefaultPage, IDefaultPage and DefaultPage > view = > > > > to > > Products.CMFPlone in order to avoid circular imports between both = > > > > packages. > > Moved test for it as well. Placed deferred deprecated imports for all = > > > > old > > names here. > > [jensens] > > > > • Remove deprecated context parameter from DefaultPage methods. > > [jensens] > > > > • minor cleanup in getDefaultPage function > > [jensens] > > > > • Added a test for the complex getDefaultPage function > > [jensens] > > > > plone.app.querystring: 1.3.3 -> 1.3.6 > > > > • Fix migration from Plone 4 to Plone 5. > > [pbauer] > > > > • Creator criteria: pur currentUser on top. > > [mvanrees] > > > > • Migrate Creator string.is to selection.any. > > [mvanrees] > > > > • add user vocabulary to plone.app.querystring.field.Creator. > > [vangheem] > > > > • do not need "is" when there is an "any" operator. > > [vangheem] > > > > • Hide upgrade-profiles when creating a new site. > > [pbauer] > > > > • Replace selection.is with selection.any for portal_types and = > > > > review_state > > operations, and add selection.any for Creator operation. > > [frapell] > > > > • Actually convert the value to a datetime for the DateIndex query > = > > modifier. > > [frapell] > > > > • Do not fail if the 'Between' operation is called with an empty > value, = > > and > > instead return a list with 2 empty values. > > [frapell] > > > > • Fixed possible problem with custom_query parameter where > theoretically a second invocation could inadvertently be using the value > from the first invocation. [maurits] > > plone.app.redirector: 1.2.1 -> 1.3 > > > > • Rerelease of 1.2.1 as 1.3 for clarity. This is for Plone 5 only. > > [maurits] > > > > • Rerelease of same code as 1.2. The changes from 1.2.1 are for > Plone = > > > > 5. > > [maurits] > > > > plone.app.registry: 1.3.1 -> 1.3.2 > > > > • Added the structure keyword to the TALES expression that returns > the = > > description for registry entries. > > This ensures that descriptions are properly escaped and HTML entities = > > > > don't show up in descriptions. > > [pigeonflight] > > > > plone.app.testing: 5.0b5 -> 5.0b6 > > > > • No need for unittest2. [gforcada] > > plone.app.theming: 1.2.7 -> 1.2.9 > > > > • Build thememapper resources. > > [vangheem] > > > > • Added cache invalidation option. > > [swartz] > > > > • change link from plone.org to plone.com. > > [tkimnguyen] > > > > • fix toolbar on control panel > > [vangheem] > > > > • fix less building > > [obct537] > > > > • Fixed copy modal for themes with a dot in the name. > > [Gagaro] > > > > plone.app.upgrade: 1.3.12 -> 1.3.13 > > > > • Unregister removed collection.css. > > [pbauer] > > > > • 5.0 beta: do not set url_expr on configlet. This must be done > > with setActionExpression. > > Fixes https://github.com/plone/Products.CMFPlone/issues/814 > > [maurits] > > > > • Turn @@tinymce-controlpanel content_css field into a list > > [ebrehault] > > > > plone.app.users: 2.3 -> 2.3.1 > > > > • Gave upgrade step destination 1. With the previous destination > '*' > > the upgrade step was always offered. > > [vanrees] > > > > • Cache schemas in volatile attributes on portal. > > [gotcha] > > > > • Package cleanup. > > [gotcha] > > > > • Disable toolbar buttons on personal preferences > > [vangheem] > > > > • Remove extra spaces in userschema.xml messages to avoid i18n = > > > > extraction > > warnings. > > [vincentfretin] > > > > plone.app.vocabularies: 2.1.18 -> 2.1.20 > > > > • Cleanup: PEP8, decorators for zca, et al. Also pimped the README. > > [jensens] > > > > • Fixed SyndicatableFeedItems to allow unicode characters in > objects = > > > > titles. > > [Gagaro] > > > > plone.dexterity: 2.3.2 -> 2.3.4 > > > > • Avoid our own DeprecationWarning about portalTypeToSchemaName. > > [maurits] > > > > • Check add_permission before checking constrains. Refs #37 > > [jaroel] > > > > • Remove obsolete css-class and text from statusmessages. > > [pbauer] > > > > plone.folder: 1.0.5 -> 1.0.7 > > > > • Depend on Products.CMFCore and remove fake-cmf, because this = > > confuses > > more than it helps to reduce complexcity. > > [jensens] > > > > • Cleanup: PEP8 and do not use id built-in as identifier. > > [jensens] > > > > • Whitespace cleanup, git ignores, cleanup package info. > > [gforcada, rnixx, maurits] > > > > plone.namedfile: 3.0.2 -> 3.0.3 > > > > • Don't fail, when accessing the tag method of the @@images = > > view, if > > scale returns None. > > [thet] > > > > plone.resourceeditor: 2.0.0 -> 2.0.1 > > > > • Added ability to convert absolute to relative urls > > [obct537] > > > > • Fixed issue with ascii encoding > > [obct537] > > > > • now properly serves filesystem files to the thememapper > > [obct537] > > > > • resourceeditor will now register non-standard mimetypes in the > python > > mimetype module > > [obct537] > > > > plone.session: 3.5.5 -> 3.5.6 > > > > • Cleanup: Pep8, plone style conventions, better readbility. > [jensens] > > plone.subrequest: 1.6.9 -> 1.6.10 > > > > • propagate registered safe writes from plone.protect to parent > request = > > object. > > [vangheem] > > > > plone.testing: 4.0.13 -> 4.0.15 > > > > • Prevent exception masking in finally clause of zopeApp context > > [do3cc] > > > > • Rerelease for clarity due to double release of 4.0.13. > > [maurits] > > > > • Added multiinit-parameter to z2.installProduct > > to allow multiple initialize methods for a package > > [tomgross] > > > > plonetheme.barceloneta: 1.6.8 -> 1.6.9 > > > > • Hide searchbox, personaltools, breadcrumbs in print.css > > [gomez] > > > > • Updated font-weight on portlet headers > > [pigeonflight] > > > > • Update font-weight on portlet management items > > [vangheem] > > > > • Updated to index.html: link to plone.com opens in new window/tab > > [tkimnguyen] > > > > plone.app.multilingual: 3.0.4 -> 3.0.6 > > > > • Rerelease due to possible brown bag release. Jenkins complains > > about 3.0.5. > > [maurits] > > > > • Move @@multilingual-selector registration from PloneRoot to > Navigation = > > > > root > > This allows to hide language folders in nginx and to use different = > > > > domains. > > [do3cc] > > > > • Update Traditional Chinese translation. [l34marr] > > plone.app.blocks: 2.1.0 -> 2.1.2 > > > > plone.app.drafts: 1.0b1 -> 1.0b3 > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Plone-developers mailing list > > Plo...@li... > > https://lists.sourceforge.net/lists/listinfo/plone-developers > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Plone-developers mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-developers > > |
|
From: Nathan V. G. <van...@gm...> - 2015-08-25 19:48:08
|
mockup-extra would probably better be in the collective. It seems to me like it'd make sense to create a new package in the collective for it. On Tue, Aug 25, 2015 at 9:32 AM, Dominik Ruf <dom...@gm...> wrote: > Hi, > > recently the tablesorter pattern has been removed from the mockup > repository. (see https://github.com/plone/mockup/pull/540) > One comment suggested it could live on as an addon. > That let me wonder, where do/should non core mockup patterns live? > > If found > https://github.com/plone/mockup-extra > but it doesn't seem to be used anymore. > > Or should I create my own repository based on > https://github.com/collective/mockup-minimalpattern > and share it in https://github.com/collective? > > The tutorial on > http://plone.github.io/mockup/dev/#learn > tells you to create new patterns directly in the mockup environment. > But if the mockup repository is only meant for plone core patterns, that > doesn't seem to be practical to me. > Wouldn't it be better if the tutorial were based on > https://github.com/collective/mockup-minimalpattern ? > > cheers > Dominik > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Plone-developers mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-developers > -- Nathan Van Gheem Solutions Architect Wildcard Corp |
|
From: Roel B. <ro...@fo...> - 2015-08-25 17:06:21
|
Hi friends, It would be awesome to get some feedback on plone.api 1.3.3. Please use it and file tickets and/or pull requests! We've done a lot of work already, and I'm confident plone.api 1.3.3 is a good enough. For some details on the latest version, check https://www.fourdigits.nl/blog/plone-api-1-3-3-released. Gil's flake8-plone-api checks for code usages that can be replaced with plone.api calls, and combined with plone.recipe.codeanalysis should give a solid base for anyone. It would be nice to see https://github.com/plone/plone.api/issues/204 resolved before shipping with Plone core. There is a known workaround, so no blocker afaik. -Roel |
|
From: Dominik R. <dom...@gm...> - 2015-08-25 14:35:15
|
Hi, recently the tablesorter pattern has been removed from the mockup repository. (see https://github.com/plone/mockup/pull/540) One comment suggested it could live on as an addon. That let me wonder, where do/should non core mockup patterns live? If found https://github.com/plone/mockup-extra but it doesn't seem to be used anymore. Or should I create my own repository based on https://github.com/collective/mockup-minimalpattern and share it in https://github.com/collective? The tutorial on http://plone.github.io/mockup/dev/#learn tells you to create new patterns directly in the mockup environment. But if the mockup repository is only meant for plone core patterns, that doesn't seem to be practical to me. Wouldn't it be better if the tutorial were based on https://github.com/collective/mockup-minimalpattern ? cheers Dominik |
|
From: Philip B. <ba...@st...> - 2015-08-25 11:50:29
|
Thanks. Looking good so far. I migrated a small page from 4.3.6 to 5.0b4 and then from AT to DX. Philip -- Starzel.de Philip Bauer Schleißheimer Straße 23 80333 München Tel: 089 - 189 29 533 ba...@st... www.starzel.de > Am 25.08.2015 um 13:16 schrieb Eric Steele <es...@pl...>: > > 5.0b4 is ready for testing at = > > http://dist.plone.org/release/5.0b4-pending/versions.cfg > > Changelog: > > docutils: 0.9.1 -> 0.12 > > plone.recipe.zope2instance: 4.2.17 -> 4.2.18 > > • Allow to disable logs. Set z2-log to the value disable to disable the Z2 access log. Set event-log to the value disable to disable the event log. [frapell] > setuptools: 5.8 -> 18.0.1 > > zc.buildout: 2.2.5 -> 2.4.0 > > Pygments: 1.6 -> 2.0.2 > > Plone: 5.0b3 -> 5.0b4 > > • Release Plone 5.0b4 [esteele] > Products.CMFDiffTool: 3.0.1 -> 3.0.2 > > • Fixed UnicodeDecodeError in dump/ndiff. > Issue https://github.com/plone/Products.CMFPlone/issues/820 > [maurits] > > • Provide diff for dexterity behaviors' fields. > [cedricmessiant] > > • Fix bug with encoding in TextDiff. > [cedricmessiant] > > Products.CMFDynamicViewFTI: 4.1.2 -> 4.1.3 > > • Cleanup: PEP8 et al., security/zca via decorators, ... [jensens] > Products.CMFEditions: 2.2.13 -> 2.2.14 > > • Do not call ndiff unless there is no html_diff. Removed strange unicode space from template. Related to https://github.com/plone/Products.CMFPlone/issues/820 [maurits] > Products.CMFPlone: 5.0b3 -> 5.0b4 > > • fix #350: "plone.app.content circular dependency on Products.CMFPlone" = > > • this > fixes the imports only, not on zcml/genericsetup level. > [jensens] > > • move Plone specific getDefaultPage (magic) code from = > > plone.app.layout > over to Products.CMFPlone. This avoids a circular dependency. Also = > > its > not really layout only related code. > [jensens] > > • Fix add-ons to be installed using CMFQuickInstaller (restore support > for Extensions/Install.py) > [datakurre] > > • Rename showEditableBorder to showToolbar and deprecate using > disable_border and enable_border for enable_toolbar and = > > disable_toolbar > [vangheem] > > • Not using less variables in toolbar everywhere > [vangheem] > > • Fix link to documentation > > • Rework timezone selection in @@plone-addsite. > [jaroel] > > • Rework language selection in @@plone-addsite. > [jaroel] > > • Turn @@tinymce-controlpanel content_css field into a list, so we = > > can add > several CSS URLs (useful when add-ons need to provide extra TinyMCE = > > styles), > and fix TinyMCE config getter so it considers the content_css = > > value. > [ebrehault] > > Products.CMFQuickInstallerTool: 3.0.9 -> 3.0.11 > > • Fixed getting profiles registered explicitly for IPloneSiteRoot > instead CMFCore ISiteRoot. Bug introduced in 3.0.10. See for > example https://github.com/plone/plone.app.mosaic/issues/124 > [maurits] > > • Cleanup: PEP8, decorators for security+zca, et al. > [jensens] > > Products.GenericSetup: 1.7.5 -> 1.7.7 > > • Fix: when the last applied upgrade step had a checker, the profile > version was not updated. Now we no longer look at the checker of > the last applied step when deciding whether to set the profile > version. The checker, if any is set, normally returns True before > running the step (it can be applied), and False afterwards (it > was already applied). > > • Add upgradeProfile method to setup tool. This method applies all > upgrades steps for the given profile, or updates it to the optional > given version. If the profile does not exist, or if there is no = > > upgrade > step to go to the specified version, the method warns and does = > > nothing. > > • Check the boolean value of the remove option when importing > objects. Previously we only checked if the remove option was > given, regardless of its value. Supported are True, Yes, > and 1, where case does not matter. The syntax for removing > objects, properties, and elements is now the same. > > • Support remove=3D"True" for properties. > > • Enable testing under Travis. > > • Fix compatibility with Setuptools 8.0 and later. Upgrade steps > could get sorted in the wrong order, especially an empty version > string (upgrade step from any source version) sorted last instead of > first. > > Products.PortalTransforms: 2.1.7 -> 2.1.8 > > • fix error mis-configured transforms would cause: "AttributeError: 'NoneType' object has no attribute 'items'" [vangheem] > mockup: 2.0.5 -> 2.0.6 > > plone.app.blob: 1.5.14 -> 1.5.16 > > • Fix migrator for AT-based types that got broken in 1.5.8 release and = > add > an option to remove the content of the non-blob field during = > > migration to > not end up having stale data in the ZODB > [fRiSi] > > • fix permission for download [david-batranu] > plone.app.content: 3.0.7 -> 3.0.9 > > • Respect view-action (e.g. for files and image) in rename, copy and = > cut. > Fixes https://github.com/plone/Products.CMFPlone/issues/829 > [pbauer] > > • Added basic test for folder contents "rearrange" and "item order" = > features. > Minor restructuring of actions in own files to have a consistent = > > structure > (bbb imports in place). Minor changes in touched area regarding pep8, > code-analysis, et al. > [jensens] > > • Do not setDefaultPage in rename handler, there is already an = > subscriber that > do so in Products.CMFDynamicViewFTI. > [jensens] > > • Do not clear clipboard when pasting content > [vangheem] > > • Fix i18n of '"title" has already been deleted'. > > • When clicking cancel on the delete_confirmation got to the view_url. > [ale-rt] > > • Fix deletion of objects with unicode charaters in the title. > [cillianderoiste] > > plone.app.contentmenu: 2.1.5 -> 2.1.6 > > • Fix: Permission check ManageWorkflowPolicies was always on = > fallback to > ManagerPortal. Now checks the correct permission after using the > pkg_resources.get_distribution api for checking (never catch an = > > ImportError). > [jensens] > > • pep8, zca decorators, plone code conventions > [jensens] > > • do not open manage portlets in a modal > [vangheem] > > plone.app.contenttypes: 1.2b3 -> 1.2b4 > > • Test Creator criterion with Any selection. > [mvanrees] > > • Selection criterion converter: allow selection.is alternative = > > operation. > [mvanrees] > > • Fixed corner case in topic migration. > [mvanrees] > > • Use event_listung for /events/aggregator in new sites. > [pbauer] > > • Remove obsolete collections.css > [pbauer] > > • Add plone.app.querystring as a dependency (fixes collections migrated = > > to p5 > and dexterity). > [pbauer] > > • Migrate layout of portal to use the new listing-views when migrating = > to dx. > [pbauer] > > • Migrate layout using the new listing-views when migrating folders, > collections, topics. > [pbauer] > > • Update allowed view_methods of the site-root on installing or = > > migrating. > Fixes #25. > [pbauer] > > • Set default_view when updating view_methods. Fixes #250. > [pbauer] > > • Fix bug in reference-migrations where linkintegrity-relations were = > > turned > into relatedItems. > [pbauer] > > • Setup calendar and visible ids even when no default-content gets = > created. > [pbauer] > > • Remove upgrade-step that resets all behaviors. Fixes #246. > [pbauer] > > • Add convenience-view @@export_all_relations to export all relations. > [pbauer] > > • Add method link_items that allows to link any kind of item (AT/DX) = > > with any > kind of relationship. > [pbauer] > > • New implementation of reference-migrations. > [pbauer] > > • Fix i18n on custom_migration view. > [vincentfretin] > > plone.app.dexterity: 2.1.7 -> 2.1.8 > > • Avoid DeprecationWarning for getIcon and splitSchemaName. [maurits] > plone.app.event: 2.0b1 -> 2.0b2 > > • Unified event_listing style with plonetheme.barceloneta styles and = > added svg > icons. > [agitator] > > • initialize events.js javascript after all patterns are initialized. > [garbas] > > • removing dependency on plone.app.contenttypes that introduce with = > > latest > changes to portlets code. > [garbas] > > plone.app.iterate: 3.1.0 -> 3.1.1 > > • Check if object does not have iterate policy. This fixes iterate causing toolbar errors on portal root. [vangheem] > plone.app.layout: 2.5.9 -> 2.5.10 > > • Correctly display selected item in global navigation for images and = > files. > Fixes https://github.com/plone/Products.CMFPlone/issues/830 > [pbauer] > > • Add view url to document as data-view-url > [ale-rt] > > • If toolbar logo is empty, use default > [vangheem] > > • Move getDefaultPage, isDefaultPage, IDefaultPage and DefaultPage view = > > to > Products.CMFPlone in order to avoid circular imports between both = > > packages. > Moved test for it as well. Placed deferred deprecated imports for all = > > old > names here. > [jensens] > > • Remove deprecated context parameter from DefaultPage methods. > [jensens] > > • minor cleanup in getDefaultPage function > [jensens] > > • Added a test for the complex getDefaultPage function > [jensens] > > plone.app.querystring: 1.3.3 -> 1.3.6 > > • Fix migration from Plone 4 to Plone 5. > [pbauer] > > • Creator criteria: pur currentUser on top. > [mvanrees] > > • Migrate Creator string.is to selection.any. > [mvanrees] > > • add user vocabulary to plone.app.querystring.field.Creator. > [vangheem] > > • do not need "is" when there is an "any" operator. > [vangheem] > > • Hide upgrade-profiles when creating a new site. > [pbauer] > > • Replace selection.is with selection.any for portal_types and = > > review_state > operations, and add selection.any for Creator operation. > [frapell] > > • Actually convert the value to a datetime for the DateIndex query = > modifier. > [frapell] > > • Do not fail if the 'Between' operation is called with an empty value, = > and > instead return a list with 2 empty values. > [frapell] > > • Fixed possible problem with custom_query parameter where theoretically a second invocation could inadvertently be using the value from the first invocation. [maurits] > plone.app.redirector: 1.2.1 -> 1.3 > > • Rerelease of 1.2.1 as 1.3 for clarity. This is for Plone 5 only. > [maurits] > > • Rerelease of same code as 1.2. The changes from 1.2.1 are for Plone = > > 5. > [maurits] > > plone.app.registry: 1.3.1 -> 1.3.2 > > • Added the structure keyword to the TALES expression that returns the = > description for registry entries. > This ensures that descriptions are properly escaped and HTML entities = > > don't show up in descriptions. > [pigeonflight] > > plone.app.testing: 5.0b5 -> 5.0b6 > > • No need for unittest2. [gforcada] > plone.app.theming: 1.2.7 -> 1.2.9 > > • Build thememapper resources. > [vangheem] > > • Added cache invalidation option. > [swartz] > > • change link from plone.org to plone.com. > [tkimnguyen] > > • fix toolbar on control panel > [vangheem] > > • fix less building > [obct537] > > • Fixed copy modal for themes with a dot in the name. > [Gagaro] > > plone.app.upgrade: 1.3.12 -> 1.3.13 > > • Unregister removed collection.css. > [pbauer] > > • 5.0 beta: do not set url_expr on configlet. This must be done > with setActionExpression. > Fixes https://github.com/plone/Products.CMFPlone/issues/814 > [maurits] > > • Turn @@tinymce-controlpanel content_css field into a list > [ebrehault] > > plone.app.users: 2.3 -> 2.3.1 > > • Gave upgrade step destination 1. With the previous destination '*' > the upgrade step was always offered. > [vanrees] > > • Cache schemas in volatile attributes on portal. > [gotcha] > > • Package cleanup. > [gotcha] > > • Disable toolbar buttons on personal preferences > [vangheem] > > • Remove extra spaces in userschema.xml messages to avoid i18n = > > extraction > warnings. > [vincentfretin] > > plone.app.vocabularies: 2.1.18 -> 2.1.20 > > • Cleanup: PEP8, decorators for zca, et al. Also pimped the README. > [jensens] > > • Fixed SyndicatableFeedItems to allow unicode characters in objects = > > titles. > [Gagaro] > > plone.dexterity: 2.3.2 -> 2.3.4 > > • Avoid our own DeprecationWarning about portalTypeToSchemaName. > [maurits] > > • Check add_permission before checking constrains. Refs #37 > [jaroel] > > • Remove obsolete css-class and text from statusmessages. > [pbauer] > > plone.folder: 1.0.5 -> 1.0.7 > > • Depend on Products.CMFCore and remove fake-cmf, because this = > confuses > more than it helps to reduce complexcity. > [jensens] > > • Cleanup: PEP8 and do not use id built-in as identifier. > [jensens] > > • Whitespace cleanup, git ignores, cleanup package info. > [gforcada, rnixx, maurits] > > plone.namedfile: 3.0.2 -> 3.0.3 > > • Don't fail, when accessing the tag method of the @@images = > view, if > scale returns None. > [thet] > > plone.resourceeditor: 2.0.0 -> 2.0.1 > > • Added ability to convert absolute to relative urls > [obct537] > > • Fixed issue with ascii encoding > [obct537] > > • now properly serves filesystem files to the thememapper > [obct537] > > • resourceeditor will now register non-standard mimetypes in the python > mimetype module > [obct537] > > plone.session: 3.5.5 -> 3.5.6 > > • Cleanup: Pep8, plone style conventions, better readbility. [jensens] > plone.subrequest: 1.6.9 -> 1.6.10 > > • propagate registered safe writes from plone.protect to parent request = > object. > [vangheem] > > plone.testing: 4.0.13 -> 4.0.15 > > • Prevent exception masking in finally clause of zopeApp context > [do3cc] > > • Rerelease for clarity due to double release of 4.0.13. > [maurits] > > • Added multiinit-parameter to z2.installProduct > to allow multiple initialize methods for a package > [tomgross] > > plonetheme.barceloneta: 1.6.8 -> 1.6.9 > > • Hide searchbox, personaltools, breadcrumbs in print.css > [gomez] > > • Updated font-weight on portlet headers > [pigeonflight] > > • Update font-weight on portlet management items > [vangheem] > > • Updated to index.html: link to plone.com opens in new window/tab > [tkimnguyen] > > plone.app.multilingual: 3.0.4 -> 3.0.6 > > • Rerelease due to possible brown bag release. Jenkins complains > about 3.0.5. > [maurits] > > • Move @@multilingual-selector registration from PloneRoot to Navigation = > > root > This allows to hide language folders in nginx and to use different = > > domains. > [do3cc] > > • Update Traditional Chinese translation. [l34marr] > plone.app.blocks: 2.1.0 -> 2.1.2 > > plone.app.drafts: 1.0b1 -> 1.0b3 > > ------------------------------------------------------------------------------ > _______________________________________________ > Plone-developers mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-developers |
|
From: Eric S. <es...@pl...> - 2015-08-25 11:49:24
|
First of all, thank you all for putting in such an epic amount of work on Plone 5. It's really close now and I think we can wrap it up with one last push. Here's what's on my shortlist for release candidate status: * [Dexterity field model editor (ace) broken · Issue #826](https://github.com/plone/Products.CMFPlone/issues/826) * [@@manage-viewlets is defective](https://github.com/plone/Products.CMFPlone/issues/782) * [Styles for plone.app.discussion need some love · Issue #764](https://github.com/plone/Products.CMFPlone/issues/764) * [@@historyview publicly visible · Issue #739](https://github.com/plone/Products.CMFPlone/issues/739) and [History view / document by line · Issue #828](https://github.com/plone/Products.CMFPlone/issues/828) * [plone.app.users upgrade step does not disappear · Issue #719](https://github.com/plone/Products.CMFPlone/issues/719) * [Building LESS files from theme editor issues · Issue #705](https://github.com/plone/Products.CMFPlone/issues/705) * [Plone 5 i18n issues · Issue #379](https://github.com/plone/Products.CMFPlone/issues/379) * [use plone lock settings from editing-controlpanel · Issue #345](https://github.com/plone/Products.CMFPlone/issues/345) * [Remove portal_properties Tool. · Issue #125](https://github.com/plone/Products.CMFPlone/issues/125) * [p.a.controlpanel migration doesn't copy p.a.multilingual settings yet · Issue #145](https://github.com/plone/Products.CMFPlone/issues/145) * [missing display_pub_date_in_byline in ISite controlpanel · Issue #346](https://github.com/plone/Products.CMFPlone/issues/346) * [Remove global_defines · Issue #836](https://github.com/plone/Products.CMFPlone/issues/836) * [No default table styles when using TinyMCE · Issue #755](https://github.com/plone/Products.CMFPlone/issues/755) * plone.api? What's our status on this one? * Bump to Zope 2.13.23. I need to reexamine the versions for these. Tres has rearranged the latest KGS and things are missing or aren't where they used to be. * I'd like to jump to current versions of lxml (currently using one released in 2011). This would be the best time to do that. * Clean out portal_skins. There are a number of no-longer-referenced items in there that should be removable at this point. I'd like to *try* to get these wrapped up by the end of next week. Have I missed any glaring issues at this point? Eric |
|
From: Eric S. <es...@pl...> - 2015-08-25 11:16:42
|
5.0b4 is ready for testing at = http://dist.plone.org/release/5.0b4-pending/versions.cfg ## Changelog: docutils: 0.9.1 -> 0.12 ---------------------- plone.recipe.zope2instance: 4.2.17 -> 4.2.18 ------------------------------------------- - Allow to disable logs. Set ``z2-log`` to the value ``disable`` to disable the Z2 access log. Set ``event-log`` to the value ``disable`` to disable the event log. [frapell] setuptools: 5.8 -> 18.0.1 ------------------------ zc.buildout: 2.2.5 -> 2.4.0 -------------------------- Pygments: 1.6 -> 2.0.2 --------------------- Plone: 5.0b3 -> 5.0b4 -------------------- - Release Plone 5.0b4 [esteele] Products.CMFDiffTool: 3.0.1 -> 3.0.2 ----------------------------------- - Fixed UnicodeDecodeError in dump/ndiff. Issue https://github.com/plone/Products.CMFPlone/issues/820 [maurits] - Provide diff for dexterity behaviors' fields. [cedricmessiant] - Fix bug with encoding in TextDiff. [cedricmessiant] Products.CMFDynamicViewFTI: 4.1.2 -> 4.1.3 ----------------------------------------- - Cleanup: PEP8 et al., security/zca via decorators, ... [jensens] Products.CMFEditions: 2.2.13 -> 2.2.14 ------------------------------------- - Do not call ndiff unless there is no html_diff. Removed strange unicode space from template. Related to https://github.com/plone/Products.CMFPlone/issues/820 [maurits] Products.CMFPlone: 5.0b3 -> 5.0b4 -------------------------------- - fix #350: "plone.app.content circular dependency on Products.CMFPlone" = - this fixes the imports only, not on zcml/genericsetup level. [jensens] - move Plone specific ``getDefaultPage`` (magic) code from = plone.app.layout over to Products.CMFPlone. This avoids a circular dependency. Also = its not really layout only related code. [jensens] - Fix add-ons to be installed using CMFQuickInstaller (restore support for Extensions/Install.py) [datakurre] - Rename showEditableBorder to showToolbar and deprecate using disable_border and enable_border for enable_toolbar and = disable_toolbar [vangheem] - Not using less variables in toolbar everywhere [vangheem] - Fix link to documentation - Rework timezone selection in @@plone-addsite. [jaroel] - Rework language selection in @@plone-addsite. [jaroel] - Turn @@tinymce-controlpanel ``content_css`` field into a list, so we = can add several CSS URLs (useful when add-ons need to provide extra TinyMCE = styles), and fix TinyMCE config getter so it considers the ``content_css`` = value. [ebrehault] Products.CMFQuickInstallerTool: 3.0.9 -> 3.0.11 ---------------------------------------------- - Fixed getting profiles registered explicitly for ``IPloneSiteRoot`` instead CMFCore ``ISiteRoot``. Bug introduced in 3.0.10. See for example https://github.com/plone/plone.app.mosaic/issues/124 [maurits] - Cleanup: PEP8, decorators for security+zca, et al. [jensens] Products.GenericSetup: 1.7.5 -> 1.7.7 ------------------------------------ - Fix: when the last applied upgrade step had a checker, the profile version was not updated. Now we no longer look at the checker of the last applied step when deciding whether to set the profile version. The checker, if any is set, normally returns True before running the step (it can be applied), and False afterwards (it was already applied). - Add ``upgradeProfile`` method to setup tool. This method applies all upgrades steps for the given profile, or updates it to the optional given version. If the profile does not exist, or if there is no = upgrade step to go to the specified version, the method warns and does = nothing. - Check the boolean value of the ``remove`` option when importing objects. Previously we only checked if the ``remove`` option was given, regardless of its value. Supported are ``True``, ``Yes``, and ``1``, where case does not matter. The syntax for removing objects, properties, and elements is now the same. - Support ``remove=3D"True"`` for properties. - Enable testing under Travis. - Fix compatibility with Setuptools 8.0 and later. Upgrade steps could get sorted in the wrong order, especially an empty version string (upgrade step from any source version) sorted last instead of first. Products.PortalTransforms: 2.1.7 -> 2.1.8 ---------------------------------------- - fix error mis-configured transforms would cause: "AttributeError: 'NoneType' object has no attribute 'items'" [vangheem] mockup: 2.0.5 -> 2.0.6 --------------------- plone.app.blob: 1.5.14 -> 1.5.16 ------------------------------- - Fix migrator for AT-based types that got broken in 1.5.8 release and = add an option to remove the content of the non-blob field during = migration to not end up having stale data in the ZODB [fRiSi] - fix permission for download [david-batranu] plone.app.content: 3.0.7 -> 3.0.9 -------------------------------- - Respect view-action (e.g. for files and image) in rename, copy and = cut. Fixes https://github.com/plone/Products.CMFPlone/issues/829 [pbauer] - Added basic test for folder contents "rearrange" and "item order" = features. Minor restructuring of actions in own files to have a consistent = structure (bbb imports in place). Minor changes in touched area regarding pep8, code-analysis, et al. [jensens] - Do not setDefaultPage in rename handler, there is already an = subscriber that do so in `Products.CMFDynamicViewFTI`. [jensens] - Do not clear clipboard when pasting content [vangheem] - Fix i18n of '"title" has already been deleted'. - When clicking cancel on the delete_confirmation got to the view_url. [ale-rt] - Fix deletion of objects with unicode charaters in the title. [cillianderoiste] plone.app.contentmenu: 2.1.5 -> 2.1.6 ------------------------------------ - Fix: Permission check ``ManageWorkflowPolicies`` was always on = fallback to ``ManagerPortal``. Now checks the correct permission after using the pkg_resources.get_distribution api for checking (never catch an = ImportError). [jensens] - pep8, zca decorators, plone code conventions [jensens] - do not open manage portlets in a modal [vangheem] plone.app.contenttypes: 1.2b3 -> 1.2b4 ------------------------------------- - Test Creator criterion with Any selection. [mvanrees] - Selection criterion converter: allow selection.is alternative = operation. [mvanrees] - Fixed corner case in topic migration. [mvanrees] - Use event_listung for /events/aggregator in new sites. [pbauer] - Remove obsolete collections.css [pbauer] - Add plone.app.querystring as a dependency (fixes collections migrated = to p5 and dexterity). [pbauer] - Migrate layout of portal to use the new listing-views when migrating = to dx. [pbauer] - Migrate layout using the new listing-views when migrating folders, collections, topics. [pbauer] - Update allowed view_methods of the site-root on installing or = migrating. Fixes #25. [pbauer] - Set default_view when updating view_methods. Fixes #250. [pbauer] - Fix bug in reference-migrations where linkintegrity-relations were = turned into relatedItems. [pbauer] - Setup calendar and visible ids even when no default-content gets = created. [pbauer] - Remove upgrade-step that resets all behaviors. Fixes #246. [pbauer] - Add convenience-view @@export_all_relations to export all relations. [pbauer] - Add method link_items that allows to link any kind of item (AT/DX) = with any kind of relationship. [pbauer] - New implementation of reference-migrations. [pbauer] - Fix i18n on custom_migration view. [vincentfretin] plone.app.dexterity: 2.1.7 -> 2.1.8 ---------------------------------- - Avoid ``DeprecationWarning`` for ``getIcon`` and ``splitSchemaName``. [maurits] plone.app.event: 2.0b1 -> 2.0b2 ------------------------------ - Unified event_listing style with plonetheme.barceloneta styles and = added svg icons. [agitator] - initialize events.js javascript after all patterns are initialized. [garbas] - removing dependency on plone.app.contenttypes that introduce with = latest changes to portlets code. [garbas] plone.app.iterate: 3.1.0 -> 3.1.1 -------------------------------- - Check if object does not have iterate policy. This fixes iterate causing toolbar errors on portal root. [vangheem] plone.app.layout: 2.5.9 -> 2.5.10 -------------------------------- - Correctly display selected item in global navigation for images and = files. Fixes https://github.com/plone/Products.CMFPlone/issues/830 [pbauer] - Add view url to document as data-view-url [ale-rt] - If toolbar logo is empty, use default [vangheem] - Move getDefaultPage, isDefaultPage, IDefaultPage and DefaultPage view = to Products.CMFPlone in order to avoid circular imports between both = packages. Moved test for it as well. Placed deferred deprecated imports for all = old names here. [jensens] - Remove deprecated ``context`` parameter from ``DefaultPage`` methods. [jensens] - minor cleanup in getDefaultPage function [jensens] - Added a test for the complex getDefaultPage function [jensens] plone.app.querystring: 1.3.3 -> 1.3.6 ------------------------------------ - Fix migration from Plone 4 to Plone 5. [pbauer] - Creator criteria: pur currentUser on top. [mvanrees] - Migrate Creator string.is to selection.any. [mvanrees] - add user vocabulary to plone.app.querystring.field.Creator. [vangheem] - do not need "is" when there is an "any" operator. [vangheem] - Hide upgrade-profiles when creating a new site. [pbauer] - Replace selection.is with selection.any for portal_types and = review_state operations, and add selection.any for Creator operation. [frapell] - Actually convert the value to a datetime for the DateIndex query = modifier. [frapell] - Do not fail if the 'Between' operation is called with an empty value, = and instead return a list with 2 empty values. [frapell] - Fixed possible problem with ``custom_query`` parameter where theoretically a second invocation could inadvertently be using the value from the first invocation. [maurits] plone.app.redirector: 1.2.1 -> 1.3 --------------------------------- - Rerelease of 1.2.1 as 1.3 for clarity. This is for Plone 5 only. [maurits] - Rerelease of same code as 1.2. The changes from 1.2.1 are for Plone = 5. [maurits] plone.app.registry: 1.3.1 -> 1.3.2 --------------------------------- - Added the `structure` keyword to the TALES expression that returns the = description for registry entries. This ensures that descriptions are properly escaped and HTML entities = don't show up in descriptions. [pigeonflight] plone.app.testing: 5.0b5 -> 5.0b6 -------------------------------- - No need for unittest2. [gforcada] plone.app.theming: 1.2.7 -> 1.2.9 -------------------------------- - Build thememapper resources. [vangheem] - Added cache invalidation option. [swartz] - change link from plone.org to plone.com. [tkimnguyen] - fix toolbar on control panel [vangheem] - fix less building [obct537] - Fixed copy modal for themes with a dot in the name. [Gagaro] plone.app.upgrade: 1.3.12 -> 1.3.13 ---------------------------------- - Unregister removed collection.css. [pbauer] - 5.0 beta: do not set ``url_expr`` on configlet. This must be done with ``setActionExpression``. Fixes https://github.com/plone/Products.CMFPlone/issues/814 [maurits] - Turn @@tinymce-controlpanel ``content_css`` field into a list [ebrehault] plone.app.users: 2.3 -> 2.3.1 ---------------------------- - Gave upgrade step destination 1. With the previous destination '*' the upgrade step was always offered. [vanrees] - Cache schemas in volatile attributes on portal. [gotcha] - Package cleanup. [gotcha] - Disable toolbar buttons on personal preferences [vangheem] - Remove extra spaces in userschema.xml messages to avoid i18n = extraction warnings. [vincentfretin] plone.app.vocabularies: 2.1.18 -> 2.1.20 --------------------------------------- - Cleanup: PEP8, decorators for zca, et al. Also pimped the README. [jensens] - Fixed SyndicatableFeedItems to allow unicode characters in objects = titles. [Gagaro] plone.dexterity: 2.3.2 -> 2.3.4 ------------------------------ - Avoid our own DeprecationWarning about portalTypeToSchemaName. [maurits] - Check add_permission before checking constrains. Refs #37 [jaroel] - Remove obsolete css-class and text from statusmessages. [pbauer] plone.folder: 1.0.5 -> 1.0.7 --------------------------- - Depend on ``Products.CMFCore`` and remove fake-cmf, because this = confuses more than it helps to reduce complexcity. [jensens] - Cleanup: PEP8 and do not use ``id`` built-in as identifier. [jensens] - Whitespace cleanup, git ignores, cleanup package info. [gforcada, rnixx, maurits] plone.namedfile: 3.0.2 -> 3.0.3 ------------------------------ - Don't fail, when accessing the ``tag`` method of the ``@@images`` = view, if ``scale`` returns ``None``. [thet] plone.resourceeditor: 2.0.0 -> 2.0.1 ----------------------------------- - Added ability to convert absolute to relative urls [obct537] - Fixed issue with ascii encoding [obct537] - now properly serves filesystem files to the thememapper [obct537] - resourceeditor will now register non-standard mimetypes in the python mimetype module [obct537] plone.session: 3.5.5 -> 3.5.6 ---------------------------- - Cleanup: Pep8, plone style conventions, better readbility. [jensens] plone.subrequest: 1.6.9 -> 1.6.10 -------------------------------- - propagate registered safe writes from plone.protect to parent request = object. [vangheem] plone.testing: 4.0.13 -> 4.0.15 ------------------------------ - Prevent exception masking in finally clause of zopeApp context [do3cc] - Rerelease for clarity due to double release of 4.0.13. [maurits] - Added ``multiinit``-parameter to z2.installProduct to allow multiple initialize methods for a package [tomgross] plonetheme.barceloneta: 1.6.8 -> 1.6.9 ------------------------------------- - Hide searchbox, personaltools, breadcrumbs in print.css [gomez] - Updated font-weight on portlet headers [pigeonflight] - Update font-weight on portlet management items [vangheem] - Updated to index.html: link to plone.com opens in new window/tab [tkimnguyen] plone.app.multilingual: 3.0.4 -> 3.0.6 ------------------------------------- - Rerelease due to possible brown bag release. Jenkins complains about 3.0.5. [maurits] - Move @@multilingual-selector registration from PloneRoot to Navigation = root This allows to hide language folders in nginx and to use different = domains. [do3cc] - Update Traditional Chinese translation. [l34marr] plone.app.blocks: 2.1.0 -> 2.1.2 ------------------------------- plone.app.drafts: 1.0b1 -> 1.0b3 ------------------------------- |
|
From: Maurits v. R. <m.v...@ze...> - 2015-08-20 12:37:40
|
You have uncovered my secret master plan. ;-) Well, not really, but getting rid of CMFQuickInstallerTool might be an option in Plone 5.1 or 6.0. The QI is more and more just a different way of talking to portal_setup. What QI now mostly does, is: - QI is an alternative installation system, with Extensions/Install.py. Products depending on this would need to be changed to use GS. In the basis this is not hard. I expect any product that was created for Plone 3 or higher to have a GS profile. Some old products, like Products.Marshall, would need a small profile, which could very roughly be: move Extensions/Install.py to setuphandlers.py and hook it up in zcml. - QI determines a link between a profile and its product and the other way around. And in the near future maybe a link between an uninstall and a default profile. The logic behind those links could in Plone 5 be moved to the new controlpanel/browser/quickinstaller.py. - QI keeps track of which products are installed. But when done correctly (see the TODO items in my original post) this information can be found in GS as well. - QI keeps a list of which things have been added during the install: skin layers, tools, etc, so it can automatically remove them during uninstall. It more or less works, but it does not do everything. With QI gone we would loose this. An uninstall profile would basically become mandatory for add-ons. When an uninstall profile is not found, the Add-ons control panel would need to display a big fat warning, probably already before activating the product: "This product has no uninstall profile: if you activate it you are stuck with it for eternity." Put a button next to it: "I feel lucky." ;-) Maurits Gil Forcada Codinachs schreef op 19-08-15 om 16:13: > Maybe an stupid idea, but is there any reason to not merge them (apart > from breaking everything?) From your description seems that the logic > about (not)installed packages is somewhat split between the two... > > 2015-08-19 14:44 GMT+02:00 Philip Bauer > <ba...@st... > <mailto:ba...@st...>>: > > Finally a plan for sanity! > +1 > > > Am 19.08.2015 um 00:01 schrieb Maurits van Rees > <m.v...@ze... > <mailto:m.v...@ze...>>: > > > > Hi, > > > > So, I have been having some fun with the CMFQuickInstallerTool (QI) > > and GenericSetup (GS) and how they cooperate. It's quite > interesting, > > really. Sit back and relax. > > > > Mostly this is about applying a GS profile and marking the > corresponding > > product as installed in the QI. And then uninstalling or unmarking. |
|
From: Gil F. C. <gfo...@gn...> - 2015-08-19 14:13:17
|
Maybe an stupid idea, but is there any reason to not merge them (apart from breaking everything?) From your description seems that the logic about (not)installed packages is somewhat split between the two... 2015-08-19 14:44 GMT+02:00 Philip Bauer <ba...@st...>: > Finally a plan for sanity! > +1 > > > Am 19.08.2015 um 00:01 schrieb Maurits van Rees < > m.v...@ze...>: > > > > Hi, > > > > So, I have been having some fun with the CMFQuickInstallerTool (QI) > > and GenericSetup (GS) and how they cooperate. It's quite interesting, > > really. Sit back and relax. > > > > Mostly this is about applying a GS profile and marking the corresponding > > product as installed in the QI. And then uninstalling or unmarking. > > > > Some version numbers: > > > > - QI 2.0.4 (introduced in Plone 3.0.4 or 3.0.5) starts using > > GenericSetup events: if a GS profile is applied, mark its > > corresponding product as installed in QI: generate an > > InstalledProduct instance, including a list of which skins etc were > > added during the install. > > > > - QI 3.0 (Plone 4.0) optimizes this logic by ignoring any > > non-installable profiles. These are profiles listed in a utility > > that implements Products.CMFPlone.interfaces.INonInstallable, with > > as goal to make some lists of profiles in the UI shorter and more > > comprehensible. Do not confuse this with > > Products.CMFQuickInstallerTool.interfaces.INonInstallable, which is > > about products. > > > > - QI 3.0.7 (Plone 4.3.4 / 5.0a3) removes the InstalledProduct instance > > when a product is uninstalled, because leaving the instance around > > can prevent settings from being stored properly on subsequent > > installation of the product. > > > > - QI 3.0.8 (Plone 4.3.5 / 5.0b1) no longer prevents INonInstallable > > profiles from being recorded as QI installed products, because > > really they are auto-installed products, not non-installable ones. > > > > BTW, are you looking for a script to download all versions.cfg files > > from dist.plone.org/release so you can easily grep through them to see > > which version of a package is used in which Plone version? See > > https://gist.github.com/mauritsvanrees/99cb4a25b622479e7dc3 > > > > With this in mind, how do you check whether a profile or product has > > been installed? For example, in plone.app.upgrade you may want to > > decide whether or not to run an upgrade step for plone.app.collection. > > You cannot always say 'this is Plone 4.2, so plone.app.collection is > > sure to be installed,' because an upgrade from 4.1 to 4.2 does not > > actually install this package. So you have to do some checks if you > > want to know this. > > > > For simplicity we only consider a product with one profile > > (``default``) and no External installation method. There are several > > ways to check its installed status: > > > > 1. Check the installed profile version in GS:: > > > > if portal_setup.getLastVersionForProfile('my.package:default') != > > 'unknown': > > # package is installed > > > > But wait: the profile was applied but the product may have been > > uninstalled afterwards. > > > > TODO: update QI so that uninstalling a product unsets its last > > profile version in GS. > > > > 2. Instead, check the product in QI:: > > > > if 'my.package' in QI: > > # product is installed > > > > But wait: this may find an outdated InstalledProduct instance for a > > product that is no longer installed. > > > > TODO: update code that uses this pattern to the next pattern. > > plone.app.upgrade uses it. > > > > 3. Instead, check the status in QI:: > > > > QI.isProductInstalled('my.package') > > > > But wait. If this is a profile that was listed as INonInstallable > > and was applied between QI 3.0 and 3.0.8, it will not have been > > marked as installed in the QI. > > > > TODO: write an upgrade step in plone.app.upgrade to go through all > > INonInstallable profiles, check if the profile was applied (method > > 1) and mark it as installed in QI. This might mark too many of > > these as installed, but so be it. > > > > TODO: write an upgrade step in plone.app.upgrade to go through all > > InstalledProduct items in the QI and remove any with getStatus() > > 'uninstalled'. And unset their last profile versions in GS too. > > > > And when you get this all right and conclude that a profile or product > > is installed and you want to run its upgrade steps, you should still > > first check whether the package is available, because it may be > > something like Kupu or TinyMCE that is no longer included in your > > Plone version. Oh, but when the package is not there, there will not > > be any upgrade steps registered in zcml, so that should not give a > > problem really. Some luck at last. > > > > Do those TODO items sound sane? > > I can see about implementing them. > > > > > > Somewhat related issue: > > Upgrade Plone 4.1 to 4.3: TinyMCE, CMFEditions and sunburst are not > > upgraded > > https://github.com/plone/Products.CMFPlone/issues/812 > > > > Pull request to fix those specific problems: > > 4.3: Properly update TinyMCE, CMFEditions, Sunburst > > https://github.com/plone/plone.app.upgrade/pull/42 > > > > Pull request to fix the general problem of not updated core packages: > > Upgrade core addons at end of Plone migration > > https://github.com/plone/Products.CMFPlone/pull/823 > > > > Note that those pull requests do NOT include the TODO items I mention > > above (except TODO number 2 partially). > > > > Comments? > > > > -- > > Maurits van Rees: http://maurits.vanrees.org/ > > Zest Software: http://zestsoftware.nl > > > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Plone-developers mailing list > > Plo...@li... > > https://lists.sourceforge.net/lists/listinfo/plone-developers > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Plone-developers mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-developers > > |
|
From: Philip B. <ba...@st...> - 2015-08-19 12:57:09
|
Finally a plan for sanity! +1 > Am 19.08.2015 um 00:01 schrieb Maurits van Rees <m.v...@ze...>: > > Hi, > > So, I have been having some fun with the CMFQuickInstallerTool (QI) > and GenericSetup (GS) and how they cooperate. It's quite interesting, > really. Sit back and relax. > > Mostly this is about applying a GS profile and marking the corresponding > product as installed in the QI. And then uninstalling or unmarking. > > Some version numbers: > > - QI 2.0.4 (introduced in Plone 3.0.4 or 3.0.5) starts using > GenericSetup events: if a GS profile is applied, mark its > corresponding product as installed in QI: generate an > InstalledProduct instance, including a list of which skins etc were > added during the install. > > - QI 3.0 (Plone 4.0) optimizes this logic by ignoring any > non-installable profiles. These are profiles listed in a utility > that implements Products.CMFPlone.interfaces.INonInstallable, with > as goal to make some lists of profiles in the UI shorter and more > comprehensible. Do not confuse this with > Products.CMFQuickInstallerTool.interfaces.INonInstallable, which is > about products. > > - QI 3.0.7 (Plone 4.3.4 / 5.0a3) removes the InstalledProduct instance > when a product is uninstalled, because leaving the instance around > can prevent settings from being stored properly on subsequent > installation of the product. > > - QI 3.0.8 (Plone 4.3.5 / 5.0b1) no longer prevents INonInstallable > profiles from being recorded as QI installed products, because > really they are auto-installed products, not non-installable ones. > > BTW, are you looking for a script to download all versions.cfg files > from dist.plone.org/release so you can easily grep through them to see > which version of a package is used in which Plone version? See > https://gist.github.com/mauritsvanrees/99cb4a25b622479e7dc3 > > With this in mind, how do you check whether a profile or product has > been installed? For example, in plone.app.upgrade you may want to > decide whether or not to run an upgrade step for plone.app.collection. > You cannot always say 'this is Plone 4.2, so plone.app.collection is > sure to be installed,' because an upgrade from 4.1 to 4.2 does not > actually install this package. So you have to do some checks if you > want to know this. > > For simplicity we only consider a product with one profile > (``default``) and no External installation method. There are several > ways to check its installed status: > > 1. Check the installed profile version in GS:: > > if portal_setup.getLastVersionForProfile('my.package:default') != > 'unknown': > # package is installed > > But wait: the profile was applied but the product may have been > uninstalled afterwards. > > TODO: update QI so that uninstalling a product unsets its last > profile version in GS. > > 2. Instead, check the product in QI:: > > if 'my.package' in QI: > # product is installed > > But wait: this may find an outdated InstalledProduct instance for a > product that is no longer installed. > > TODO: update code that uses this pattern to the next pattern. > plone.app.upgrade uses it. > > 3. Instead, check the status in QI:: > > QI.isProductInstalled('my.package') > > But wait. If this is a profile that was listed as INonInstallable > and was applied between QI 3.0 and 3.0.8, it will not have been > marked as installed in the QI. > > TODO: write an upgrade step in plone.app.upgrade to go through all > INonInstallable profiles, check if the profile was applied (method > 1) and mark it as installed in QI. This might mark too many of > these as installed, but so be it. > > TODO: write an upgrade step in plone.app.upgrade to go through all > InstalledProduct items in the QI and remove any with getStatus() > 'uninstalled'. And unset their last profile versions in GS too. > > And when you get this all right and conclude that a profile or product > is installed and you want to run its upgrade steps, you should still > first check whether the package is available, because it may be > something like Kupu or TinyMCE that is no longer included in your > Plone version. Oh, but when the package is not there, there will not > be any upgrade steps registered in zcml, so that should not give a > problem really. Some luck at last. > > Do those TODO items sound sane? > I can see about implementing them. > > > Somewhat related issue: > Upgrade Plone 4.1 to 4.3: TinyMCE, CMFEditions and sunburst are not > upgraded > https://github.com/plone/Products.CMFPlone/issues/812 > > Pull request to fix those specific problems: > 4.3: Properly update TinyMCE, CMFEditions, Sunburst > https://github.com/plone/plone.app.upgrade/pull/42 > > Pull request to fix the general problem of not updated core packages: > Upgrade core addons at end of Plone migration > https://github.com/plone/Products.CMFPlone/pull/823 > > Note that those pull requests do NOT include the TODO items I mention > above (except TODO number 2 partially). > > Comments? > > -- > Maurits van Rees: http://maurits.vanrees.org/ > Zest Software: http://zestsoftware.nl > > > ------------------------------------------------------------------------------ > _______________________________________________ > Plone-developers mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-developers |
1157 messages has been excluded from this view by a project administrator.
