I set up a search by page environment at a specific URL (search_site) and when I search for any word, no results come up (see attached). But, when I search from the tabbed search page (search/search_by_page), I get plenty of results. I went through the readme file, but can't figure it out. Am I missing a step?

CommentFileSizeAuthor
ScreenShot027.png4.78 KBhillaryneaf

Comments

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

Hmm, that's odd... I don't know what to tell you.

How are you accessing the search on the search_site URL -- maybe the search keywords are not coming through to the page correctly? They should be showing up in the keywords box on the page.

It could also be a theme problem -- try switching to Garland and see if it works then.

hillaryneaf’s picture

hillaryneaf commented

Oh, sorry the search box isn't in the screenshot. It is there- it's just off the page due to styling. The word I searched for "test" is also in the box and it is in the URL: /search_site/test. When I searched in the tabbed page, I get a lot of results.

Switching to garland produces the same result.

I'll set up a bare drupal 6 site and follow the same steps and see if I can get it to work.

hillaryneaf’s picture

hillaryneaf commented

It works fine on a bare drupal 6 site. I'll try to figure out which module is conflicting with it. I have some custom modules that could be causing it.

hillaryneaf’s picture

hillaryneaf commented

It conflicts with Custom Search module.

I use that module to provide a drop down with custom search paths in it. Just putting the module into the clean drupal site and turning it on is enough to make the Search by Page functionality break as described above.

Not sure where the two clash, but they serve different purposes...

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

Try a different URL for the Search by Page environment -- will that remove the conflict?

hillaryneaf’s picture

hillaryneaf commented

Changed the URL to "testing" instead of "search_site". That didn't fix it.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented
Title: Search by Page tabbed page works, but environment URL does not » Search by Page environment page does not work with Custom Search module

Well, it was worth testing...

OK. Well it will take some investigating to figure out what the conflict is between these two modules. I'm not familiar with the Custom Search module so I'm not sure what it might be doing that interferes with Search by Page... You might try posting a support request on that module's issue queue to figure it out (or move this support request to that project). I probably can't make time to investigate this any time soon. Sorry!

hillaryneaf’s picture

hillaryneaf commented
Title: Search by Page environment page does not work with Custom Search module » Search by Page tabbed page works, but environment URL does not

Maybe this will help... after a search returns nothing, if I clear caches from admin menu while on the page, the results show up. But if I press the search button again (with the keyword in the field), it goes blank again.

hillaryneaf’s picture

hillaryneaf commented
Title: Search by Page tabbed page works, but environment URL does not » Search by Page environment page does not work with Custom Search module

Oops didn't mean to change the title back on you

hillaryneaf’s picture

hillaryneaf commented
Project: Search by Page » Custom Search
Version: 6.x-1.15 » 6.x-1.9
Component: Main Search by Page module » Code

Moving this to Custom Search module queue per jhodgdon's recommendation

lane.angelique’s picture

lane.angelique commented

I am having the same issue. Search by Page was working just fine until I installed and enabled Custom Search. I wonder if the issue described here: http://drupal.org/node/1274296 is the problem?

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented
Category: support » bug

I took a look at the Custom Search module (version 6.x-1.x in the Git repository viewer) today, and I think I have found the problem.

It is in the custom_search_db_rewrite_sql() function. This function is an implementation of hook_db_rewrite_sql().

That hook is invoked whenever any Drupal module wants to create a listing of nodes. But the implementation function custom_search_db_rewrite_sql() appears to be assuming that it's only being invoked by Custom Searches, and it's adding a WHERE clause to the query that it shouldn't be for queries that are not Custom Searches.

The function needs to be rewritten so that it detects whether or not a Custom Search is actually being used, and only alters those queries. Or better yet, a different mechanism other than using that hook should be used to exclude node types from the Custom Search query. As it is, that function is capable of screwing up other node listings, such as Views, by excluding content types from them that it shouldn't be, and it looks like it would be excluding content types based on whatever the last Custom Search that was run (because the module uses a variable_set() mechanism to remember what is being done).

This is definitely a bug.

loon’s picture

loon commented
Issue summary: View changes
Status: Active » Closed (outdated)

D6 reached its EOL, and there is no active release for D6 for this module anymore.
Development or support is not planned for D6. All D6-related issues are marked as outdated in a bunch.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.