qhoxie

Hi Scott,

Thanks for reaching out. You can definitely modify things on a per-search box basis. The best way to do this would be to just add a hidden input in the search form. Then, in the backend you can use the swiftype_search_params filter to check that parameter and filter as necessary. You can read more here: https://swiftype.com/documentation/tutorials/customizing_wordpress_search

Best,
Quin

Hello,

Thanks for bringing this to our attention. We just released a new version (1.1.31) that should fix this issue for you.

Best,
Quin

Hello,

This is definitely doable by using our developer API in conjunction with the WP plugin. You will need to add a location field and then apply a geospatial filter. Here are relevant guides:

– https://swiftype.com/documentation/searching#filters
– https://swiftype.com/documentation/tutorials/customizing_wordpress_search

Best,
Quin

Yes, but you would potentially need to index some custom fields, depending on how the captions are added. You could also use our crawler solution instead of the WP plugin, which would work out of the box on this.

Best,
Quin

You should be able to use the following in any template to add a search box that will work with Swiftype.

<input type="text" value="' . get_search_query() . '" name="s" id="s" />

Hi, As we mentioned via our support system, this appears to be an issue with the actual files on your host. As such, there unfortunately isn’t much we can do to help aside from give guidance. Please let us know if the situation changes.

Best,
Quin
Founder, Swiftype

We’re happy to help you get this resolved. Can you send us an email to [email protected] or through your dashboard? We will need your account information to help look into your issue.

I think for now removing that is the best approach. The issue is that we need to manage clicks on search results in order to track analytics for you. By removing this, your new window plugin will work, but it will not track clickthroughs in your Swiftype analytics.

Hello,

I’m sorry to hear you were not pleased with your experience using Swiftype. We make no attempt to hide the fact that we are a freemium service, but I can understand where the confusion comes from. Our pricing is displayed prominently on our primary site, which users are required to visit to get an account: https://swiftype.com/pricing. I’m sure we can do better to communicate this in other flows, so I’ll pass this feedback along to the team.

Best,
Quin Hoxie
Founder, Swiftype

Hello,

Our plugin works by indexing entities/content from the posts table in WordPress. This includes custom post types, pages, and regular posts. Anything that is dynamically generated like a category page is not indexed at this time, though we would like to in the future.

Best,
Quin

Hello,

I can’t imagine how there would be a conflict. We don’t make any changes to how things render in our plugin – only to how the backend of search works. Please let me know if you have further details.

Best,
Quin

Hello,

The plugin should work fine with 3.6.1 – have you seen any issues?

1. Yes this is doable. You can find a guide here: https://swiftype.com/documentation/tutorials/customizing_wordpress_search

2 & 3. We completely defer rendering of results to your theme. Any of this is possible, it just needs to be done at the theme level.

Best,
Quin

Hello,

Thanks for reaching out.

We’ve had a lot of requests for WooCommerce integration with Swiftype, but right now it does not index most of the product data that WooCommerce adds to WordPress, hence the poor results you’re seeing.

Since we’ve had requests to add WooCommerce, we are putting it on our roadmap and planning to have something available soon.

Best,
Quin

Take a look at the “Modifying autocomplete results” section here: https://swiftype.com/documentation/tutorials/customizing_wordpress_search

In that same swiftypeConfig object, you will need to set disableAutocomplete to true. Here is an example:

var swiftypeConfig = {
    disableAutocomplete: true
};

Best,
Quin

Hi Angus,

I’m sorry to hear you are seeing issues. We have done some testing internally and have not been able to reproduce this. Which version did you have prior to 1.1.24? I ask because the changes from 1.1.23 are very minimal and should not affect the edit view at all.

Best,
Quin