majecdad

Crap. Haste makes waste. Was in a hurry, entered it wrong. My bad.

Meant: http://clarkcountylive.com/category/blog/rss

In testing with a new post today, the one new post came in correctly. I am going to continue to monitor as the earlier error was intermittent.

I’ll update as I know more.

Thanks.

I updated to 1.0.1, but this issue remains.

This error in Console:

Uncaught TypeError: Cannot read property ‘split’ of undefined /wp-content/plugins/widget-context/js/widget-context.js?ver=4.0-beta1-20140714:35

and links to this:

var get_query_arg_val = function( query, key ) {
var vars = query.split(‘&’);

Slider dev says: The plugin (Widget Context) contains a function that runs every time AJAX requests run in a page, and this function fails for GET requests.

He also gives more info, including suggested fix, if you’d like.

Thanks.

Excellent. I’ll look for it.

WRT the second usage, that was only in testing to see if one worked vs. the other. I’ll pull the wop version.

Thanks for the timely support. Now back to look at the goodness in that Pro version.

Thanks for that info. And huge +1 for the timely support.

When I last looked at this, you were just getting the sales site up and trying to get indexing into 1.0. Lots of progress made.

Going to look deeper into your Pro version. Love the map feature. Will likely have questions there and will hit you with them at the site.

Keep up the good work.

Appreciate the timely support reply.

Application is in a locked down sandbox environment, so can’t send link. I double checked and the Search Shortcode Content option is enabled. Also I placed the shortcode to output on a page and widget to check both.

Is there a certain amount of time that needs to pass for indexing to occur? Is there an ability to reindex the content? Does that matter?

I’ll keep tweaking it to figure out what it might be, as I really like the plugin and direction you seem to be headed in.

Re: the dev version. That’s a cool layout. I would just add that having an ‘include’ by taxonomy as opposed to only ‘exclude’ would be great, and the ability to do so on a non-global basis is really important (so your shortcode override is helpful). FWIW, rationale is that if we want to use multiple search boxes that pull from only certain taxonomy each.

Lastly, is there a way to have the search results render in a different page vs. in the sidebar below the widget?

Thanks, you’ve got a great feature set here, especially for so early in the dev process.