Question 1

Why does Liferay select all only select the current page?

Accepted Answer

The management toolbar's select-all checkbox is client-side React state with no name attribute; it only checks row checkboxes physically rendered on the current page. Submit a selectAll flag and recompute the full matching set server-side from the filter criteria.

Question 2

How do I read selection state from a Liferay search container?

Accepted Answer

Use Liferay.componentReady(searchContainerId).then(sc => sc.select.get('bulkSelection')) to read select-all state, and subscribe to the rowToggled event for any selection change. Never inspect checkbox DOM attributes, since the header checkbox has no name or value.

Question 3

How do I handle management toolbar action dropdown clicks in Liferay?

Accepted Answer

Wire a propsTransformer on the clay:management-toolbar tag and handle onActionButtonClick, matching item.data.action. This is the stock Liferay pattern and avoids unreliable DOM event delegation on React-rendered dropdown items.

Question 4

Why does my aui:script not find elements in a Liferay JSP?

Accepted Answer

An aui:script block can execute before the surrounding server-rendered HTML exists in the DOM, so getElementById returns null. Look elements up inside Liferay.componentReady(...).then() or use event delegation on a stable ancestor.

Question 5

Should clay:management-toolbar go inside or outside the aui:form?

Accepted Answer

Render the toolbar outside the aui:form. With showSearch enabled the toolbar renders its own nested form, and nesting forms produces invalid HTML that can detach row checkboxes from the outer form's submission.

liferay-management-toolbar-search-container

SYSTEM DOCUMENTATION & REQUIREMENTS

Frequently Asked Questions about liferay-management-toolbar-search-container

Related Skills

liferay-osgi

wp-admin-list-table

keyword-library

liferay-custom-elements