Hey, philbee, can you confirm what version of WordPress and this plugin you’re running? We’ll investigate!
Hey,
sure, I tried on two local sites (running on Valet NGiNX), both with WordPress 6.5.3 and QLPS 1.0.1.
CPTs tested were two of my own (one created in CPTUI, one in ACF Pro) as well as WooCommerce products.
<!-- wp:query {"queryId":0,"query":{"perPage":"1","pages":0,"offset":0,"postType":"fp_produkt","order":"desc","orderBy":"date","author":"","search":"","exclude":[],"sticky":"","inherit":false,"qlpspSelectivePosts":[{"title":"Tisch Edition 60","id":11665}],"parents":[]}} -->
Doesn’t matter what id is defined for qlpspSelectivePosts, the query loop block will always display the first post it comes across.
Thanks a lot!
Thanks so much for the details @philbee! We are releasing an update today; we found an issue where the editor wouldn’t show the correct query for custom post types, but the front-end would. This was due to post types being registered later via CPT UI (or any other plugin).
Hey, perfect, 1.0.2 seems to solve this little problem – meaning I now can use the default Query Loop block instead of Advanced Query Loop.
Thanks a bunch for a great small plugin 😎 !
