All plugins accessible in exclusive state

Description

Any plugin portlet can be viewed by using the "exclusive" window state. The amount of information exposed depends greatly on how the plugin is designed. Issue does not affect built in portlets and other window states.

Activity

Show:

Sebastian Monte June 20, 2012 at 8:38 AM

I should have been more specific in my previous comment, sorry about that.

I have few portlets that are included directly in a theme, for example:

$theme.runtime("myPortlet_WAR_myContext")

Before this patch, it was possible to send requests from the view to the controller using an "exclusive" window state:

<portlet:renderURL windowState="<%= LiferayWindowState.EXCLUSIVE.toString() %>" />

However, these requests don't reach the controller anymore. Does this patch prohibit such use, so I can not have runtime portlets that use an exclusive window state to get some content? All the other window states are working properly.

Sebastian Monte June 20, 2012 at 6:59 AM

After installing this patch, I am not able to use "exclusive" window state in any plugins portlets. For example, trying to use ajax the get a view from portlet does not go through at the moment. This side behavior is probably not intended?

Samuel Kong April 25, 2012 at 12:19 AM

The code for this ticket was committed under

Fixed

Details

Assignee

Reporter

Components

Priority

Zendesk Support

Created April 25, 2012 at 12:18 AM
Updated June 24, 2023 at 3:53 PM
Resolved April 25, 2012 at 7:03 PM
Loading...