Closed (works as designed)
Project:
Custom Search
Version:
6.x-1.9
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
15 Sep 2011 at 16:06 UTC
Updated:
22 Feb 2015 at 06:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jdanthinne commentedI can't reproduce this bug… and Custom Search doesn't set any page title.
Can you tell me a way to reproduce this bug (from a clean install)?
Comment #2
majdi commentedI have the same problem
Comment #3
sshakir commentedTo reproduce the bug simply search for something and on the results page it has "Home" as the title above "Enter your keywords:". This is happening when I search from the search form placed in a block. See attached screenshot.
Comment #4
jdanthinne commentedI still can't reproduce that, using a default basic install of Drupal, and Custom Search.
Can you try with a basic install? And then with the latest DEV, just to be sure…
Perhaps another module is causing that behaviour.
Comment #5
sshakir commented@jdanthinne I did not get the "error" using a fresh install with the latest DEV. Maybe it is another module that is conflicting. I'll keep researching.
Comment #6
JCB commentedI can confirm that I am experiencing the same issue
Comment #7
Vincent Verheyen commentedI am experiencing the same "issue". It would be nice to be able to change this.
This is what happens after hitting search, since (I guess) the Custom Search Block automatically redirects (after hitting search) to the default search page (default, as in specified via Home » Administration » Configuration » Search settings?
And all of these default search pages have "Home" as a page title.
Would it perhaps be possible to tweak around this and stay on the actual page where the Custom Search-block is implemented, even after hitting search? Or, perhaps to redirect, but to redirect to a page specific for the Custom Search-block, and thus to not also display the default search module (as specified in Home » Administration » Configuration » Search settings)? Perhaps it might be nice to add an option to be able to choose the Custom Search module as an Active search modules and a Default search module over there as well?
Comment #8
jdanthinne commentedIs your search url /search/node ? Custom Search doesn't modify any title by itself…
Comment #9
Vincent Verheyen commentedWell, I now have the default search module "Display suite Search" set up as a standard, and I provided a custom URL "
/search/article_titles/", but indeed, if one chooses "Node" as the default search module, the default search URL would be "/search/node/".I understand that Custom Search doesn't modify any title by itself. However, I suspect the original poser was referring to "Home" title which appears on the top of any search page by default (when showing the results, independent of the chosen default search module; unless when not having clicked "search" yet and specifically on a custom page with a Custom Search Block, but this page normally redirects after clicking "search", thus losing control over the page's title).
The reason why he mentions this here is, I think, because the Custom Search Block redirects to the page specified as default search module after hitting "search", to view the results; and thus we see the title "Home" appear.
I don't know of any way to change this WYSIWYG, but would be very interested in this as well. @jdanthinne - Can you reproduce this behavior?
Comment #10
jdanthinne commentedIf you disable Display Suite, does the title still is Home ?
Comment #11
Vincent Verheyen commentedDo you mean, when inactivating "Display Suite Search" inside Home » Administration » Configuration » Search settings, and choosing e.g. "Node" as a default search module? In that case: yes, then the title stays Home.
In case you mean uninstalling / disabling the module Display Suite all together, in Home » Administration » Modules, I have checked some things on a ± fresh control website ...
These are the things I noticed:
The most important finding, in regard to the issue however, is perhaps:
So, well, I can't really say if disabling / installing the main-Display Suite all together would fix the issue. I would rather not test it out on my issue site, in the fear of losing some information ...
Also: enabling or disabling the Custom Search-module on the "issue"-site, doesn't seem to make a difference. This doesn't seems to be a Custom Search-specific issue.
Comment #12
jdanthinne commentedWell, if the issue is not on the fresh website, the bug must be coming from another module or theme. Try enabling on this fresh site all the modules and themes you're using on the "issue" one until the bug happens.
Comment #13
Vincent Verheyen commented@jdanthinne - I just installed and enabled all modules that are enabled on the "issue"-site, onto the fresh site. Even after installing the same custom sub-theme; the buggy behavior didn't appear on the fresh site ...
Comment #14
jdanthinne commentedEven Custom Search ?
Comment #15
Vincent Verheyen commented@jdanthinne - Yes, Custom Search enabled and installed, as well as Custom Search Blocks.
Comment #16
jdanthinne commentedThen, and sorry to say that, but the problem is coming from somewhere else...