benito64

Please pardon my ignorance: though I used WP a lot in the past (developing plugins, themes, etc.), I’m getting back to it after a long hiatus.

I’m just getting started with Gutenberg, and though it probably still has problems, I don’t see how in the world the classic editor would be faster than Gutenberg. From what I see, WordPress still saves posts to the database in good old HTML. So as far as retrieving posts is concerned, there shouldn’t be any drawback in using Gutenberg.

I haven’t run benchmarks myself, but would be curious, if you have any input on the matter.

• This reply was modified 3 years, 8 months ago by benito64. Reason: being notified of replies

Thank you sooo much. I had this issue on my wpsandbox.local virtual host. Tricky one indeed!

Oops… there was something wrong in my code, that was pretty tricky indeed, but WP was not involved. Sorry.

Hi,

I’m pretty curious about this topic too.
I can’t get post__in and post__not_in to work with custom post types.
The example below works fine with the ‘post_type’ line commented (standard post query).
Here’s what happens if I uncomment this line in order to query custom posts : using post__in, I get no posts at all, and using post__not_in I get all the posts including the ones I want to exclude.

Any clue ? (I’m using WP 3.1.3 by the way)
Thanks

$custom_query = new WP_Query(array(
//	'post_type'=>'header_images',
	'posts_per_page' => -1,
	'post__in' => array(234),
	'orderby' => 'menu_order',
	'order' => 'ASC'
));