Can't open Search and Replace - Link in Site configuration doesn't work
krabbe - March 21, 2009 - 01:26
| Project: | Search and Replace |
| Version: | 6.x-1.1-beta3 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Installed beta3-version on a multilingual drupal 6.10 site.
When I go to Administer > Site configuration > Search and Replace the browser is loading the admin/settings page again. The address-field of the browser shows the url admin/settings/search_and_replace.
cheers,
krabbe

#1
I'm getting exactly the same result. I have a uni-lingual 6.10 site (so the multi-lingual has nothing to do with it). I've never used Search and Replace before. As above, when I go to admin/settings and click on Search and Replace, the address field shows admin/settings/search_and_replace, but it still just shows the admin/settings screen.
#2
I just tried what seems to be a similar module, Search and Replace Scanner ( http://drupal.org/project/scanner ). It seems to work fine with the same configuration. I haven't used either of these modules before, is there any special reason why I should use one or the other?
#3
I too cannot access this module once it is installed. Kinda hard to evaluate it- any help?
#4
I still don't really know what the differences are between Search and Replace and Search and Replace Scanner, but I've installed Scanner on my site and it seems to work quite nicely.
#5
scanner goes through at a database level and makes the changes globally for the term / phrase. This can be dangerous because it removes the ability to go back and undo things in the revision history (it changes them historically).
#6
I also noticed this recently (error w/ the module). Not having changed anything this is very odd, I'll look into it
#7
Wow, beta3 and I can't even see the configuration menu like the others say. This is one big bug for sure.
#8
Sorry about that, try beta 4. There was a CVS mix up and 5's code got committed to the 6 branch.
#9
Automatically closed -- issue fixed for 2 weeks with no activity.