Closed (works as designed)
Project:
Search 404
Version:
6.x-1.7
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
19 Nov 2009 at 05:00 UTC
Updated:
15 Apr 2011 at 01:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
OneTwoTait commentedFurther use shows this error on many pages, not just pages related to Node Reference URL. It usually, but not always, shows up on pages that involve adding a comment with Node Comment, or while creating a referencing node with Node Reference URL.
Comment #2
bmasters commentedI'm seeing something similar, however I'm not running the Node Reference URL module or Node Comment module. I am running CCK's Node Reference module, however, which is required by Node Reference URL, so my guess is the issue is related to CCK Node Reference??
See attached screenshot of error message.
Has any progress been made on this issue?
Comment #3
zyxware commented@bmasters - When google CSE is enabled the module only displays the said error and redirects the user to the Google CSE results page - search/google/search-string-here. Try typing in this URL into the address bar and see what happens
Comment #4
bmasters commented@zyxware -
Thanks for your response. I can confirm that the Google CSE and Search 404 modules work together correctly on my site for the most part. That is, if I browse to www.mysite.com/some-page-that-does-not-exist I get redirected to the Google CSE results and see an error message generated by the Search 404 module that reads: "The page you requested does not exist. For your convenience, a google search was performed using the query some page that does not exist." This is the expected behavior.
My issue is that sometimes the Search 404 error message appears on pages where it should not. It doesn't happen very often, but I've seen it more than once. The screen shot that I attached in my previous post captures what I've seen before. In that case, I've browsed to a valid URL yet the Search 404 module has injected an error message anyway. The module did not invoke Google CSE in any meaningful way. And you can tell by the error message that it has picked up something from the HTML and reprinted it. In this case, the error message contains a string of text describing an image that appears on an entirely different page.
BTW, I'm using version 6.x-1.8.
I hope that clarifies my issue.
Comment #5
zyxware commented@bmasters - I think I can imagine a situation where you can get this. In drupal messages don't necessarily get displayed on the page that results in the message. They are stored in a session variable. So if you have a page where you send simultaneous results of which one results in a 404 while the other results in the actual page. If the 404 page is because of, say a missing image, you could end up with the message on the page while the missing image request gets transparently processed.
I am marking this issue as closed as this does not look like a search404 issue.