By popular demand, this plugin now supports URLs like this:
- http://example.com/?s=word&meta_key=meta_value
- http://example.com/?cat=1&mood=Happy
The template tags were updated to reflect this posibility. Also, an extra template tag was added:
all_meta_info() displays all available data for the current post.
PHP5 is required.
Great plugin! I added a release announcement here:
http://www.opensourcereleasefeed.com/release/show/wordpress-custom-field-taxonomies-plugin-expanded-url-support
Feel free to add all future releases there as well.
Erm…thanks?
I am using:
Search Custom Fields Beta2
http://guff.szub.net/source/search-custom.php
and Search Unleashed:
http://urbangiraffe.com/plugins/search-unleashed/
Along with Wp Drop Down Metas:
http://wordpress.org/extend/plugins/wp-dropdown-metas/
I am able to place drop-down selects of each key name, with each value linking to a query of that value on that field.
The only shortcoming is being able to run multiple key names simultaneously for the one query – and having a navigator box that previewed a complete query before running it.
It would be cool if your plugin combined
You mean like ?meta1=valA&meta2=valB ?
This part I don’t understand. Preview as in AJAX? An example or something?
that is correct. having querystring that allowed you to run a search on more than one key name. But, the question then is how to construct that query, ie what user interface would enable such a query to be constructed.
—
For example, a widget could be in place where the admin can pre-select any number of key names for the user to select values. Once one value is selected by the user, it is copied to the bottom of the widget and shown to be locked-in. Then, the other field name values adjust to show only values that can co-exist with the just selected value to yield results in a resultset (each value can show also the number of posts to which selecting that value will limit the result set to). This way, when the query is run, their is guaranteed output.
This select>lock-in can occur many times in the ajax widget before a query is actually run, and an ajax generated preview of the results can be shown below the widget: either the names of the posts to be shown, or the number.
The admin can create have multiple widget to display, each using different field names. Check out my site for ideas: http://tr.im/9iaq
just activated but getting the following errors upon activation at top of plugins screen:
Warning: array_keys() [function.array-keys]: The first argument should be an array in /home/launchpa/public_html/clean/d/wp-content/plugins/custom-field-taxonomies/main.php on line 51
Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/launchpa/public_html/clean/d/wp-content/plugins/custom-field-taxonomies/main.php on line 54
To get rid of that, just register a meta taxonomy. Fixed in version 0.6.2. Thanks for letting me know.
problem when plugin activated, no results for:
http://mysite.com/?s=thermal&searchsubmit=Find
when deactivated, I get many results.
I have deactivated all cache and search plugins, it is an issue relevant to this plugin.
This is how the plugin works:
Is ’searchsubmit’ a registered taxonomy?
No? Let WordPress do it’s thing.
Yes? Find all posts that match the search for ‘thermal’ AND have a custom field searchsubmit => Find.
Now put yourself in the plugin’s shoes and see if you can find any posts.
the plugin is activated, and this yields no results:
http://mysite.com/?s=thermal
I’ll see if there are other plugins are interfering…
Unless you have ’s’ as a meta taxonomy (which you shouldn’t!), the plugin shouldn’t interfere.
I haven’t added any taxonomies in the admin. Just activated the plugin, and the basic search functionality has knocked out.
Try deactivating ALL plugins, except this one.
Did that on another 2.7 blog of mine.
To no avail:
http://tr.im/faue
Hm…if you could create a temporary admin user for me, I could debug it for you. If you agree, send the wpurl, user and pass to scribu AT gmail.com
Can you send me the instructions instead?
If it were that simple, I would. I can’t send you instructions because I don’t know what to check until I see the backend with my own eyes.
I’ve done debugging for other people and nothing bad happened to their site and I was usually able to fix the problem quickly.
It turns out that he just had to register a taxonomy.