You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When registering a variation for the Query block, it is possible to define the perPage, offset, and pages attributes so that they are prefilled with the variant is added. In some cases, this is a specific variation in which these attributes should not change. Currently, it is possible to immediately change these attributes through the "Display settings" dropdown in the toolbar.
What is your proposed solution?
It would be great if the individual attributes—perPage, offset, and pages—could be removed through the allowedControls property. It could also be useful to allow for the entire removal of the "Display settings" dropdown itself.
The text was updated successfully, but these errors were encountered:
I wish to do the same with my fork of @ryanwelcher|s Advanced query block plugin, where some of the (native & extended) controls do not fit my use-case of a contextual query block.
Without looking into the code, but shouldn’t it be possible to have all the controls placed within a slot and then unregister specific fills, when not needed?
What problem does this address?
When registering a variation for the Query block, it is possible to define the
perPage
,offset
, andpages
attributes so that they are prefilled with the variant is added. In some cases, this is a specific variation in which these attributes should not change. Currently, it is possible to immediately change these attributes through the "Display settings" dropdown in the toolbar.What is your proposed solution?
It would be great if the individual attributes—
perPage
,offset
, andpages
—could be removed through theallowedControls
property. It could also be useful to allow for the entire removal of the "Display settings" dropdown itself.The text was updated successfully, but these errors were encountered: