LoopSort FAQ and limitations

Answers to the most common questions about LoopSort and LoopSort Pro: Elementor versions, empty fields, archive templates, privacy and support.

Does LoopSort work with the new Atomic Loop (Editor V4)?

Not yet. Elementor doesn’t offer a public way to extend the Atomic Loop’s query or settings. The classic Loop Grid (and, with Pro, Loop Carousel) works on any page, including pages built with atomic elements.

Does LoopSort work without Elementor Pro?

No. The Loop Grid widget is part of Elementor Pro, so LoopSort needs Elementor Pro 4.2 or later.

Will posts without the field disappear?

No. They’re shown first or last, as you choose. Only LoopSort Pro’s filters remove posts, and only when you add them.

Can visitors see drafts or private posts because of LoopSort?

No. LoopSort only changes the order of what the grid already shows, and the Sort Control renders only published, visible content.

Can I sort an archive template (“Current Query”)?

Not yet; the LoopSort section is hidden for that source.

Can I sort by a repeater or multi-select field?

No. Those hold several values per post, so there’s no single value to sort by.

Can I sort WooCommerce products by price, stock or rating?

Yes, with LoopSort Pro: choose WooCommerce product data as the field source to sort or filter by current, regular or sale price, stock quantity, total sales, average rating or review count. The free plugin can sort by public WooCommerce meta keys such as _price typed as a meta key.

Does LoopSort collect data or call external services?

The free plugin makes no external requests, collects no data and sets no cookies. LoopSort Pro sets one small session cookie, loopsort_device (desktop, tablet or mobile), only on pages that have a Sort Control or a grid with responsive posts per page, so Taxonomy Filter refreshes keep the right posts-per-page count. It holds no personal data. Licence activation talks to Freemius, our licensing partner.

How do I report a security issue?

Please don’t post it in a public forum. Email the security contact listed in the plugin’s readme; reports are acknowledged within 72 hours.