Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Not sure if this is user error or a problem with the module. When I enter overrides into the "Labels and String Overrides" section of the configuration form nothing changes on the search form. For example, setting the Keywords label to "Keywords" still results in "Enter your keywords" on the form. Setting the "Submit button" to "Submit" still results in "Search" on the form. Am I missing something?
Comment | File | Size | Author |
---|---|---|---|
#7 | search_config_settings_labels.jpg | 137.61 KB | hermes14 |
Comments
Comment #1
Alan D. CreditAttribution: Alan D. commentedGoing to check one thing before looking into this: Are you using user 1 to test? This is a built-in setting from D6 that allows this user to bypass the search overrides which is also implemented in D7.
Comment #2
hermes14 CreditAttribution: hermes14 commentedSame issue here, logged as regular user. I switched to dev version since I noticed this bug in stable.
Actually none of the overrides seems to work. For instance, hiding a content type has no effects at all - the form remains unaltered. The same happens for all of the fields.
If you need more info just let me know, I'll be glad to provide them.
Comment #3
Alan D. CreditAttribution: Alan D. commentedI just tested the submit button string override using 7.x-1.1-beta1 and it worked for me. Is this bug only appearing in 7.x-1.0?
Comment #4
hermes14 CreditAttribution: hermes14 commentedSorry for the delay. Both 7.x-1.0 and 7.x-1.x-dev show this issue. If 7.x-1.x-dev is actually 7.x-1.1-beta1, then no, it appears also in beta version.
If it works in your installation but not in ours, it may depend on some other modules which probably interfere with it. If so, guessing the right one could be tricky... I'll try with a fresh install and see what happens.
Comment #5
hermes14 CreditAttribution: hermes14 commentedI also tried the 7.x-1.1-beta1 version, which looks pretty much the same as the dev version, if not exactly the same.
Don't know if relevant, but I noticed that the search_config_exclude table remains empty, no matter what I do with the search configuration options. Maybe a clue?
Comment #6
Alan D. CreditAttribution: Alan D. commentedCould you do a screenshot of your search configuration settings for me so that I can replicate these and test? Only the bottom fieldset with the labels section expanded.
Comment #7
hermes14 CreditAttribution: hermes14 commentedHope this is what you need. Some parts are translated into italian, sorry...
BTW, I didn't touch anything there, these are the default settings.
Comment #8
Alan D. CreditAttribution: Alan D. commentedIt is strange that these do not show (note, you need to have the advance form present before the string alters are added). I've never been overly happy with the complexity of the code here, so it will be a good chance to refactor and enforce the string overrides separately. It is near the top of my todo list.
Comment #9
mxhany news on this? having the same issue with all versions of this module. installed D7.12.
Comment #10
Alan D. CreditAttribution: Alan D. commentedYep, done :) Committed into 7.x-1.1-beta2.
Comment #11
mxhAlan D., you rock! Many thanks. I will test it next free time and give feedback. Greetings!
Edit: How to setup the module that the settings take effect? Unfortunately, there are still no changes when setting up like "hide this field".
Comment #12
Alan D. CreditAttribution: Alan D. commentedAre you using user 1 to test? This bypasses the settings. It is a safety fallback from the D6 version in case the module broke something. Find the setting "'Admin bypass (primary user with id 1)" and uncheck this to force the module to skip this check.
Otherwise, if the module is working, fields should be hidden if there is an advanced search form present. Hopefully, I haven't introduced a new bug with the changes.... Which field?
Comment #13
mxhsorry for the very late post, but I can report you that it now works. I think there was a settings override problem somewhere with an other module, unfortunately I'm not able to give the exact reason why it didn't work first. Anyway...
Thank your very much for support and for this very useful module!
Greetings