Bryce Corkins

That was going to be my suggestion too. Some themes (a lot, apparently) set a z-index on inputs. We’ll work on overriding this in a future version.

Ah, I’m sorry, there was a bug when I committed it that caused it not to go out. Had to increment to 1.6.3 to make it work. You should see it now.

Sorry about that. I just released v1.6.1 which should fix this issue. You should see the update become available shortly.

Unfortunately MapPress uses its own custom database tables for storing its data, which is not the standard way of storing custom data with WordPress, and so it’s not going to be searchable by most search plugins. We’d recommend taking a look at Advanced Custom Fields and their Google Map field, which is fully supported by WPUS, and stores its data in a standard way so that other search plugins can access it too. You’d have to find a way to migrate your MapPress data, which I’m not sure how to do, but maybe someone’s written a guide. Good luck!

Thanks!

You can’t run two instances of the search bar on the same page.. since they’ll get confused about which area to return the results to. Try using a plugin like “widget context” (or there are many others) to hide the sidebar widget on pages where you have the search bar already in place.

To change the names of the labels, and have access to different taxonomies, you’ll need to upgrade to the pro version of the plugin. More information about this can be found at https://mindsharelabs.com/downloads/wp-ultimate-search-pro/

Yes, and I’m sorry.. we knew it would be inconvenient for people, so we put it off for several months. Unfortunately our old method was significantly slower and less flexible in terms of what search parameters could be handled. The new search code offers a lot more flexibility.

It may be possible that having two instances of the plugin installed are causing conflicts with eachother, I’m not sure. The one in the footer seems to be partially working. If I select a tag from the dropdown, I’m redirected to the results page with the proper search results for that tag. It’s only if I type in text that the text isn’t getting passed through to the results page. If you want to send me an admin login and FTP login for your site to [email protected], I’d be happy to log in and see if I can fix it.

The matching key words will be highlighted on the search results page, if those words appear.. but once you click through to another page, words will no longer be highlighted.

For information on customizing the results template, see this page on our knowledgebase: https://mindsharelabs.com/kb/how-do-i-customize-the-search-results-template/

If you were already using a custom results template, take a look at wp-ultimate-search/views/wpus-results-template.php to see how it’s changed. Basically you’ll want to change <?php if ($results): ?> to <?php if ( $wpus_results->have_posts() ) : ?>, delete the lines <?php global $post; ?> and <?php setup_postdata($post); ?>, and replace <?php foreach ($results as $post): ?> with <?php while ( $wpus_results->have_posts() ) : $wpus_results->the_post(); ?>. Then towards the bottom, change the <?php endforeach; ?> to <?php endwhile; ?>.

Beautiful, thank you. I’ll give it a try.

We haven’t tested this, but since it uses a WP_Query to return results, it should only show results for the currently selected language.

Can you send us a link to the site in question?

Were you using a custom results template (a wpus-results-template.php file in your theme directory)? The syntax for this file changed in the last update, and there are a few lines of code that need to be updated. See the release notes for details. If you need help fixing this file, let me know.

If you weren’t using a custom results template, try going into the settings page for WPUS and saving the settings once.. sometimes this will fix any bugs that are introduced between versions.

It was tagged as a long term goal since nobody had asked for it, but I can bump it up to try and include in v1.6 or 1.7. Probably two – three months at the rate we’re going, but could be less if I can find some spare time.

It used to, but it was slowing down searches too much. It’s something that we plan to bring back in a future release.

Looks like a bug got introduced in our last release. I’ve fixed it and pushed out version 1.5.1.. you should see the update appear in your dashboard shortly.

You’re also going to run into problems trying to run two instances of the search bar on the same page.. one of them won’t work. I’d recommend removing the footer search widget on the page you’re using for the main search.