daggerhart / query-wrangler

A Query page and widget creator for Wordpress. Based on Drupal Views

Query Wrangler

Query Wrangler is a WordPress plugin that provides an intuitive interface for creating complex WP queries as shortcodes and widgets. UI based on Drupal Views.

This plugin lets you create new WP queries as widgets, and use shortcodes for to show queries in your content. Additionally, it allows you to override the way category and tag pages display without editing tempalte files.

Supports:

• Most post data, including meta fields
• Taxonomy data
• Advanced Custom Fields
• Custom Content Type Manager
• Some exposed filters

Some examples of how you would use this plugin include:

• Create a list posts with featured images
• Create a list of pages or posts within a specific category or tag
• Create an image gallery
• Modify the way your category pages look

Frequently Asked Questions

How do I use query shortcodes?

Easy, the code you're looking for is like this. [query id=2] , where the number 2 is the query id. When viewing the list of queries each one will have 2 options for shortcode. One that uses the query's id, and the other using the query's slug. I recommend using the query's slug for future maintainability.

• By id: [query id=2]
• By slug: [query slug="my-query"]
• Customize WP_Query arguments: [query id=2 args="posts_per_page=1&post_type=page"]
• Customize WP_Query arguments with contextual data: [query id=1 args="author={{post:post_author}}&post_type={{post:post_type}}"]

What are overrides and how do I use them?

Overrides allow you to alter the display and information given on category and tag archive pages.

For a simple example, add a new query and chose the type override. Choose how you want the content to display, then examine the Overrides box in the center column. From there you can add taxonomies and terms this query will override.

Other

• Meta Field Display Handler: Advanced Custom Fields
• Sort by Meta value
• Meta Field Display Handler: Custom Content Type Manager
• Custom field example
• Field callback usage: wp_get_attachment_url
• Field callback usage: the_tags
• Filter callback usage:
• Query Slideshow - Example of creating a custom style. Turn your queries into slideshows using jquery.cycle

query-wrangler's Issues

Support for preg_replace `e` modifier removed in PHP 7

Request: https://wordpress.org/support/topic/update-to-php-7/

Offender: https://github.com/daggerhart/query-wrangler/blob/master/includes/query.php#L380

This was put in a long time ago because of various issues around extra quotation marks being added to fields during the save process, then later being unable to unserialize those fields.

TODO: Determine if there is still a need for this; if so find another solution, if not remove it.

Does `qw_get_meta_keys` need to be called on the frontend?

Hello,

I have a question:

Does qw_get_meta_keys need to be called on the frontend? I am asking because this query is taking ~2 seconds to load (due to filter qw_fields). I had to add caching to it since it's so slow. I'll provide that here too (sorry, no PR for this). I am thinking of increasing the cache lifetime to 24 hours since this doesn't change unless I am importing new content.

I currently have 1,864,773 records in the postmeta table. This query is single-handedly causing my site to load ~2 seconds longer.

I also don't see why this is being loaded on the frontend. Perhaps this is due to using views? I am not using views and only use the query building part, as the heart of another system I built.

I'm just trying to figure out if this is actually necessary to be loaded on the frontend or is this only needed on the backend.

For now, I have wrapped the filter qw_fields in a is_admin() check in both meta_value.php and meta_value_new.php (seems like this is for the backend, not the fronend). I don't have any issues... yet.

From a performance perspective, fetching the meta keys on every page load is not ideal at all. The table can get extremely bloated with data so I wouldn't recommend doing this on the frontend. The backend makes sense as it's necessary but definitely not on the frontend.

Thanks!

---

Cache for qw_get_meta_keys:

function qw_get_meta_keys() {
	global $wpdb;
	$keys = get_transient('qw_meta_keys');
	if (false === $keys) {
		$keys = $wpdb->get_col("
			SELECT meta_key
			FROM $wpdb->postmeta
			GROUP BY meta_key
			ORDER BY meta_key");
		set_transient('qw_meta_keys', $keys, 900);
	}
	return $keys;
}

Problem with `category__and` operator

https://wordpress.org/support/topic/category_and-seemingly-ignored

Feature Requests

Hi,
First off - this is truly an amazing plugin; has some incredible potential and have been very excited to test this out! I made a forum post that had a few questions on (some of which the dev version with exposed filters seems to partly solve), but wanted to post it here in-case this was the more appropriate area for it: http://www.widgetwrangler.com/forum/query-wrangler/general/intro-query-wrangler#comment-5

Again - thank you very much for making this. I'll be willing to test anything you can throw at me! :)

Options override does not work as expected

In query.php line 78 you are using array_merge_recursive. This is the incorrect method and should be using array_replace_recursive instead. The issue is that values are stacked instead of replaced.

e.g posts_per_page will become an array with two values instead of using the override value.

Support for custom post categories?

I have custom post types with their own categories. These categories do not seem to be available to the Query Wrangler category filter.

Using simple text meta tag as field results in output: 'Array'

I've added a custom field using a post meta. In the database this meta has a plain text value but the output results in 'Array'.
Im using row style 'fields'.
Seems like the issue is somewhere within the qw_make_fields_rows(). Would it be possible to keep the raw php data of the result? This would be really good for theming.

Stacking filters

Hello,

Very nice this plugin! I am especially happy about the ability to stack filters:

• post-type = my-custom-post-type
• search = value1
• meta-query : my-key1 LIKE meta-value-1

However It would be nice if can stack another meta-query, like

• meta-query : my-key1 LIKE meta-value1
• meta-query : my-key2 LIKE meta-value2

The UI seems to allow it, but the whenever I hit save , only the bottom meta-query is kept, with the other one gone. Is this a bug?

Another question : Is it possible to combine (nested) boolean AND / OR expressions ?