try clearing your cache. And double check that blogsearch is selected as the destination page.

Also, it's possible that your theme is overriding the addons code.

ChadStrat

Thanks for the quick reply.
Cache is disabled (during development).
Yes, I am pointing to blogsearch in the prolog settings.
blogsearch is a page that I created and has standard search block on it (correct?).

If the theme is overriding things, what files to do I have to move around to make this work - ie, moving into my theme folder etc.
Thanks
Steve

no. that's incorrect.

It should have been set by default and created on install as a single_page (application page)

Delete your blogsearch page. uninstall / reinstall.

Then confirm that the page is set in the settings and that it indeed was created on install.

ChadStrat

ok. I've got the blogsearch page back after reinstalling.
now on a tag search I go tohttp://my-law.ca/blogsearch/competition/... and the page says no results found...
for category search I gethttp://my-law.ca/blogsearch/categories/trends/... and no results found.
What am I missing? Thanks. Steve

You need to edit the search block on the blog search page to search appropriate place.

Sent from my iPhone

> On Oct 3, 2013, at 9:55 AM, concrete5 Community <discussions@concretecms.com> wrote:

I have them pointing to search another page below the blog page.
Is this correct?

I would just set it to search everywhere to make life easier.

ChadStrat

I did that. Still the same result.
Any other thoughts?
Is the URL being passed correctly?
http://my-law.ca/blogsearch/categories/trends/...
http://my-law.ca/blogsearch/competition/...

It's the correct URL, but your search block is not receiving any parameters / search query.

Meaning, that your site is not seeing the /blogsearch as a single page , thus ignoring it's controller file.

The root issue here is that Blogsearch is a ProBlog exclusive single page with a special controller file that handles SEO friendly urls with tags/categories. If you look at the standard tag view you find included with the standard C5 search block, you will notice the urls generated are ugly. (yoursite.com/search?search=1&akID[#][atSelectOption]=32)

So PB installs this single page that has a special controller file to serve as a "handler" . It receives a /tag or /category, then goes and finds the correct C5 ugly URL, and then passes that as a parameter to the search block on the forwarded page.

Yours is not doing this. Meaning only one thing...it's not seeing that controller file.

Does your theme include a blogsearch.php file? if so, remove/rename it.

Do you have a root level override of the blogsearch.php single page? if so, remove/rename it.

You need that page to see the /packages/problog/controllers/blogsearch.php file.

There is a reason it's not seeing that, and I am %100 certain that reason has nothing to do with something the package is doing. It's not possible.

Thousands of people using this, only you reporting it. Something's up with the way you have your site set up. Root override, theme.....ect

ChadStrat

there are two blogsearch.php files on the site.
- packages/problog/single_pages
- packages/problog/controllers
is this the correct configuration?
Steve

That is correct. But if you go to your dashboard -> pages & themes -> single_pages area, does it show the "blogsearch" page as belonging to ProBlog?

ChadStrat