Skip Navigation

[Resolved] Sort block showing as shortcode if moved inside WordPress Archive Search

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 2 replies, has 2 voices.

Last updated by Alok Sharma 1 year, 6 months ago.

Assigned support staff: Waqar.



I moved the Sort block inside the WordPress Archive Search to make it appear next to the search bar. The preview in the back-end shows fine, but when previewed on the front-end, the Sort block is showing the short code inside the list box.

Also, the Sort block is showing the following message, so I assume it should work properly if placed inside the WordPress Archive Search:

This block must be placed inside WordPress Archive Output, WordPress Archive Search but not inside WordPress Archive Loop

And when I moved the Sort block back to its original location, i.e., inside the WordPress Archive Output, the Sort block shows fine on the front-end.

Please refer to the attached screenshots.




Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)


Thank you for contacting us and I'd be happy to assist.

Your observation is correct and this limitation is already highlighted.
( it also happens when using a blocks-based view block )

I'm afraid, I don't have a time estimate for a fix, but to show the search form and the sorting controls next to each other, you can include some custom CSS code, in the archive:
( screenshot: hidden link )

.wpv-filter-form > div {
	width: 48%;
	float: left;

.wpv-sorting-block {
	display: block;
	width: 48%;
	float: right;

.js-wpv-loop-wrapper {
	display: block;
	clear: both;
	float: none;



My issue is resolved now. Thank you!