Thread

I’ve been wracking my brain on this problem since yesterday, with no results. I have(had) three sites setup under MSM: Default Site, Site 2 and Site 3, let’s call them.

Search forms, results pages, et cetera function as expected on the Default Site (unchanged since original EE install).

However, no matter how I set up the forms, parameters, et cetera on either Site 2 or Site 3, search results just lands me back at the site index.

Site 3, btw, was an eeSiteKit setup. And Kurt D spent a few hours on this with me as well and could find no fault in code, et cetera. Even the two of us, together, could not get search to show results. I’ve since deleted Site 3 and have been trying to get search working on Site 2. No luck.

I’m not sure where to start troubleshooting on this. Did a search through the Forum, but could find nothing like this.

Any ideas? Anyone?

Currently, Search isn’t MSM aware. I don’t know if any third party dev has figured out a way around this, but I can move this to HowTo.

Currently, Search isn’t MSM aware. I don’t know if any third party dev has figured out a way around this, but I can move this to HowTo.

Can you be a bit more specific on this, Sue?

Are you saying that “Search” will not work at all under MSM, except on the “default” or first site?

If correct, then why is that? Is it because of template or template group names?

I’d like to know more…

The search module will search only the Site you are currently on. 

There are feature requests for this that you could add your voice to.  If you need an immediate solution, it may be best to look at something like Google.

Okay, Lisa. You’ve misunderstood my problem. I already know that Search will not work across sites. My problem is this:

Search is ONLY working on the first site (site id=“1”). It does not work within (not across) the additional sites under MSM. Am I making that understandable?

Ok, so if I am understanding, you have a Site with a weblog and search form, the search form is looking at the weblog on the same site and not pulling results, correct?

That should work, so please do confirm. There are areas we can look at here.

Yes, Lisa. That is exactly right. Search form is looking on the same site (not across sites) and not pulling results. (Works fine on the default site, though).

If I search for something valid (I know the result exists), search is not presenting anything at all. I am dropped off back at site index page. If I search for something INvalid (does NOT exist), then search reports appropriately that no results were found.

May I ask what version and build of both EE and the MSM you are on?

EE 1.6.7 20090320
MSM 1.1

R.BIRD,

Can you provide the actual search template code you are using?

If you view the source on your both your sites, what value is used for site_id in each

<input type="hidden" name="site_id" value="1" />

@John: all is as it should be with regard to site id. Values are correct.

Still getting nowhere on this issue.

I’ve checked system paths, templates, form parameters, etc.

Search on site id 2 just does not find the search/results page whatsoever. Every search, valid or invalid, dumps back to site index page.

I’ve turned on error reporting, too. Nothing reported.

I just don’t know where to look for trouble.

Thought I would chime in here.

I logged in to this site and set up a default simple search form right out of the docs and couldn’t get things to work.

I work with the simple search form on nearly every site I build and I’ve never had it do this before.

Its as if the page_results parameter is being totally ignored AND, not being replaced with the fail-safe of ‘search/results’ that will be used when a person hasn’t set the parameter.

I’m wondering what sorts of things might allow the site to work, and still prevent the simple search from accessing the correct path info, and/or processing the path info at all from the path.php file on the server (as that’s where this form still gets its info from).

Are you doing this logged in?  I’m curious if the search/results template is access protected.  This would certainly be symptomatic of such a setting.

Nope, should work for anyone.

Nothing tricky at all about this, that’s why its so strange.

The conversation started over here.