headers
Eric Steele | 1 Mar 2011 03:25
Picon
Gravatar

4.1b1 blocker

I'm looking for some help clearing up a blocker before packaging up 4.1b1.

We have a migration issue in the 4.1a3 upgrade reported and confirmed. http://dev.plone.org/plone/ticket/11521

I really don't want to move into the beta stage without having that fixed. Is anyone able to look into it?

Eric
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev
Permalink | Reply | 3 comments |
headers
Yuri | 1 Mar 2011 08:16
Picon

Re: configurable portlets availability

Il 28/02/2011 21:24, Laurence Rowe ha scritto:
> On 28 February 2011 19:18, Johannes Raggam<raggam-nl@...>  wrote:
>    
>> On Mon, 2011-02-28 at 18:55 +0000, Laurence Rowe wrote:
>>      
>>>> any suggestions on this?
>>>>          
>>> You may already override the display of a portlet based on the 5-way
>>> multi-adapter, allowing you to render it blank where you need to.
>>>        
>> hm ... that would be possible
>>
>>      
>>> But for your use-case the extremely simple solution is to just set the
>>> portlet on the left hand column and block the right hand column
>>> portlets for the front-page object and set the portlet only on the
>>> right hand column for the portal root itself (where it will be
>>> inherited.)
>>>        
>> it's just some portlets, i want to turn off and on, based on the
>> context. both columns - left and right - should be displayed on the
>> front-page.
>>
>> the way i'll do it is to subclass the portlets i need and provide the
>> available property as described...
>>      
> At risk of repeating myself, the general case of needing different
> portlets on the front-page to the rest of the site is already
> supported, via the following steps:
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Yuri | 1 Mar 2011 08:18
Picon

Re: configurable portlets availability

Il 28/02/2011 22:02, Johannes Raggam ha scritto:
> hmmm....
>
> i have to rethink my strategy... i've seen that you can even define
> portlets per content-type and export/import it per GS (and a declarative
> configuration is what i need).
>
> well, i'll go your way since it fits my needs and i don't have to
> subclass existing portlets to achieve what i need.
>
> but the approach i described previously is easy. and it would help to
> switch portlets on and off based on conditions, which still can't be
> implemented with what plone offers. like: if it's 12:00, display portlet
> with id "time-to-eat"... #sillyexample
>    

The "plone strategy" is to load always the portlet, and having the 
portlet template with a condition "is 12:00?" on the main tag :)

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev
Permalink | Reply | 1 comment |
headers
Raphael Ritz | 1 Mar 2011 10:28
Picon
Favicon

Re: configurable portlets availability

On 3/1/11 8:16 AM, Yuri wrote:

[..]

>
> I confirm it works (I use it quite often), but there's no interface
> support for editing portlets of an item which is the default view of a
> folder. A good way to solve it could be to do as we already do for
> editing. We can display a message like: "you're editing the portlets of
> the container, if you want to edit the portlets of the default view,
> click here:<link to item_default_view/ <at>  <at> manage-portlets>
>
> Recently, I've told to my collagues to not set an item as the default
> view, until all the portlets are set ok, otherwise some confusion would
> arise.
>
> A cool feature could be to render with some opacity the content in the
> middle, so users could understand where they're acting.

https://dev.plone.org/plone/ticket/10672

Raphael

>
>> I'm strongly against adding more complexity to plone.app.portlets
>> unless your plip can demonstrate it brings a real benefit, not just
>> another way of achieving the same ends.
>>
>> Laurence
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Johannes Raggam | 1 Mar 2011 11:12
Picon
Gravatar

Re: configurable portlets availability

On Tue, 2011-03-01 at 08:18 +0100, Yuri wrote:
> Il 28/02/2011 22:02, Johannes Raggam ha scritto:
> > hmmm....
> >
> > i have to rethink my strategy... i've seen that you can even define
> > portlets per content-type and export/import it per GS (and a declarative
> > configuration is what i need).
> >
> > well, i'll go your way since it fits my needs and i don't have to
> > subclass existing portlets to achieve what i need.
> >
> > but the approach i described previously is easy. and it would help to
> > switch portlets on and off based on conditions, which still can't be
> > implemented with what plone offers. like: if it's 12:00, display portlet
> > with id "time-to-eat"... #sillyexample
> >    
> 
> The "plone strategy" is to load always the portlet, and having the 
> portlet template with a condition "is 12:00?" on the main tag :)

but then you have to modify the portlet template, which you might not
have easily access to. and you cannot set it for individual portlet
assignments, but only for all portlets, using the same template...

i still think the approach above is worth to consider ...

> 
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in 
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data
(Continue reading)

Permalink | Reply | 0 comments |
headers
Johannes Raggam | 1 Mar 2011 11:20
Picon
Gravatar

Re: configurable portlets availability

On Mon, 2011-02-28 at 23:53 +0000, Laurence Rowe wrote:
> You can already change the rendering of the portlet based on
> multi-adapters, indeed I think this may do want you want already, as
> it is the renderer that has the 'available' property.
the available property is what i used in [1].

> So assuming you had a custom view as the front page that implements an
> ISpecialView interface you could register a special renderer for your
> portlet on that view when it is rendered in the left column with:
> 
>     <plone:portletRenderer
>         portlet=".portlets.IMyPortletData"
>         class=".portlets.SpecialRenderer"
>         view=".browser.ISpecialView"
>         manager="plone.app.portlets.interfaces.ILeftColumn"
>         />
well, that sounds also flexible! i didn't know that. that might also
solve the use case.

,,,johannes

> 
> Laurence

[1]
https://svn.plone.org/svn/collective/collective.developermanual/trunk/source/portlets/appendix/available_adapter.txt

--

-- 
johannes raggam / thet
python plone zope development
(Continue reading)

Permalink | Reply | 0 comments |
headers
Johannes Raggam | 1 Mar 2011 11:42
Picon
Gravatar

Re: configurable portlets availability

to sum up, the different methods of controlling the display of portlets
are:

* in own portlets or subclassed portlets, just use the available
 <at> property.

* to display portlets side-wide, configure the display per context,
content-type or group, and even configure blocking of inheriting of
portlets, use generic setup or the through the web approach
( <at>  <at> manage-portlets,  <at>  <at> manage-content-type-portlets?key=CONTENTTYPE).

* you might register an 5-way adapter based on
context,request,view,manager,data, overriding the default renderer for
the portlet type.

* you can also register a custom portlet renderer for a specific view.

* use conditional statements in the template, if possible.

* and there is the approach i brought in where the available property in
the base renderer should use an adapter, which can be overridden then.

i think the 5-way adapter solution laurence brought in could solve the
same use cases than my approach. you could register an adapter, which
overrides the default renderer for a portlet but subclasses it at the
same time and provide a custom available property there. you might have
to reference the pagetemplatefile also. i haven't tried this yet.

plip submission stalled! unless i or someone else comes up with an
argument, why it's still needed.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Plone Tests Summarizer | 1 Mar 2011 12:58
Picon

Plone Tests: 5 OK, 1 Failed

Summary of messages to the testbot list.
Period Mon Feb 28 12:00:00 2011 UTC to Tue Mar  1 12:00:00 2011 UTC.
There were 6 messages: 1 from ATContentTypes Tests, 1 from Archetypes Tests, 1 from Plone Libraries Tests,
1 from Plone Products Tests, 2 from Plone Tests.

Test failures
-------------

Subject: FAILED (113 packages, 5 failures) : Plone-4.1 Zope-2.13 Python-2.6.5
From: Plone Tests
Date: Tue Mar  1 08:01:22 UTC 2011
URL: https://lists.plone.org/pipermail/testbot/2011-March/016219.html

Tests passed OK
---------------

Subject: OK : Plone-3.3 Zope-2.10 Python-2.4.6
From: Plone Products Tests
Date: Tue Mar  1 07:36:37 UTC 2011
URL: https://lists.plone.org/pipermail/testbot/2011-March/016214.html

Subject: OK : Plone-3.3 Zope-2.10 Python-2.4.6
From: Plone Libraries Tests
Date: Tue Mar  1 07:41:38 UTC 2011
URL: https://lists.plone.org/pipermail/testbot/2011-March/016215.html

Subject: OK : AT-1.5 Plone-3.3 Zope-2.10 Python-2.4.6
From: Archetypes Tests
Date: Tue Mar  1 07:47:54 UTC 2011
URL: https://lists.plone.org/pipermail/testbot/2011-March/016216.html
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ross Patterson | 1 Mar 2011 18:10
Favicon
Gravatar

Re: 4.1b1 blocker

Eric Steele <ems174@...> writes:

> I'm looking for some help clearing up a blocker before packaging up
> 4.1b1.
>
> We have a migration issue in the 4.1a3 upgrade reported and
> confirmed. http://dev.plone.org/plone/ticket/11521
>
> I really don't want to move into the beta stage without having that
> fixed. Is anyone able to look into it?

Just committed a fix for the immediate problem.  David mentioned some
larger problem so look in the ticket for his comments to come.

Ross

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev
Permalink | Reply | 0 comments |
headers
Eric Steele | 1 Mar 2011 20:43
Picon
Gravatar

4.0.4 released (was: Re: Plone 4.0.4 release is pending)

4.0.4 is now released. Enjoy.

Eric

On Feb 27, 2011, at 12:25 AM, Eric Steele wrote:

> Plone 4.0.4 is now in the "pending" state. This release includes the patches for CVE-2011-0720, so the
hotfix is not needed with this release.
> Point your buildouts at http://dist.plone.org/release/4.0.4-pending/versions.cfg and be sure to
add http://dist.plone.org/release/4.0.4-pending/ to your find-links.
> 
> I'll plan on releasing on Tuesday morning if there are no regressions found.
> Thanks,
> Eric
> 
> == Combined changelog for Plone 4.0.4 ==
> 
> Zope 2.12.16
> ------------
> See http://docs.zope.org/zope2/releases/2.12/CHANGES.html
> 
> Plone
> -----
> - Remove useless trailing slash in 404. This fixes http://dev.plone.org/plone/ticket/11550 [gotcha]
> - Use correct argument order in utranslate.py script. This fixes
http://dev.plone.org/plone/ticket/10395 [fRiSi]
> - Add missing security declarations on PropertiesTool. [davisagli]
> - Add fallback icon for control panels with no icon, in the portlet_prefs portlet. This fixes
http://dev.plone.org/plone/tickets/11112. [topherh, davisagli]
> - Remove js-generated inline style from searchbox. Same CSS is in public.css. See
(Continue reading)

Permalink | Reply | 0 comments |

Gmane