Reply To: ajax request result versus widget result & foreach error

Author Replies
traversal # Posted on November 7, 2014 at 10:28 am

Hey there. Yeah, I suspect this doesn’t work because there’s no notion of the “current post” or the current query when using the AJAX filters, so the call to $wf->the, or $wf->loop fails. I suspect you’d have to pass the post ID you’re looking for. $wf->loop will only work when you’ve got a global query object representing the current query for an archive page. If you’re trying to loop over the posts for a specific custom post type, you’d need to use:

foreach ($wf->type(“custom_post_type”)->posts as $post)

which should still work in an AJAX handler, as it doesn’t reply on global state. You can also shorten this and use:

foreach ($wf->custom_post_types as $post)

which will look for a post type based on the singular form of “custom_post_types”. That actually returns a WOOF_PostType object, not a collection, but WOOF_PostType implements the Iterator interface, and will return a collection of posts in that type when used in conjunction with foreach.

Latest From the Blog

MasterPress 1.4.1 is now available

27th May 2024

This update addresses backwards compatibility issues that were introduced in the previous update. There were some edge cases where PHP 7 had issues and it didn’t work at all on PHP 5.6. We have now changed it so that the PHP 8 compatibility changes will now only affect PHP 8 and will be more thorough… 

Plugin Requirements

MasterPress requires a minimum of WordPress version 4.9, MySQL 5.6, and PHP version 5.6.20.

We also recommend that PHP is configured to use a memory limit of 64MB per request (128MB may be required for sites with higher complexity).

This plug-in is not compatible with the hosted service.

Three AM