Ticket #2509 (assigned defect)

Opened 7 years ago

Last modified 7 years ago

Refresh portlet edit form to update widget visibility

Reported by: gracinet Owned by: cgoutte
Priority: P2 Milestone: CPS 3.5.6
Component: CPSPortlets Version: 3.5.2
Severity: normal Keywords: portlet edit form usability


It is very customary in portlet edit and create form for the widgets to have visibility conditions depending of the value stored in the fields.

For example, in Content Portlet, the "Base folder" is presented only if "Contextual" is False.

This creates a usability problem, because one needs to save the settings first for the new options to be presented. In the above example, if Contextual is True and the user wants to change it to False, she'd have to save to get the "Base folder" widget and put a value in there. Nobody would expect that these days.

A simple short term solution would be to trigger the saving/reloading with javascript hooks (onchange, etc). We'll think of something more generic later, if appropriate.

Change History

comment:1 Changed 7 years ago by gracinet

  • Owner changed from gracinet to cgoutte
  • Status changed from new to assigned

IIRC, most widgets can have "onchange" properties (I may be confused by memories from CPSDashboards, too). In the meanwhile, an explicit message on the page to warn the users that they must save to see new options would be useful already

comment:2 Changed 7 years ago by gracinet

  • Component changed from CPS (global) to CPSPortlets

comment:3 Changed 7 years ago by gracinet

Standard widgets having the 'onchange' property are the Generic Select and MultiSelect widgets defined in CPSSchemas.ExtendedWidgets (CPS 3.5) and CPSSchemas.widgets.select (CPS 3.6)

The boolean widget does not inherit from these, and therefore should also be equipped with an 'onchange' property and render accordingly.

Last edited 7 years ago by gracinet (previous) (diff)

comment:4 Changed 7 years ago by cgoutte

it now seems to work fine on my local instances install, with some changes. will be pushed soon.

Note: See TracTickets for help on using tickets.