Posted by stuckagain on September 25, 2009 at 11:11pm
| Project: | Search and Replace Scanner |
| Version: | 6.x-1.0 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
when i search for < !--break- >, search & replace reports it in multiple (possible all) nodes. however when I open the node it is not there. Please note, I had to omit a hyphen from the break tag in order that it displays in this message.
Comments
#1
Hmmm, I just tested this and did not see any false positives.
I tested by configuring Search & Replace to only search the body field of Page nodes. Then I created two Page nodes -- one with the
<!--break-->tag in it and one without. When I search for<!--break-->, I get back one result -- the node with the tag in it.This happens whether or not I have regular expression search enabled.
Can you provide some more information on how you have Scanner configured and what your search options are when you run into this problem?
Thanks
#2
Please see the attached screen prints.
#3
Hi stuckagain, what do your search results look like? (They're cut off at the bottom of the PNG you attached.) The results should show the
<!--break-->and the surrounding text. Does that not match the HTML in your nodes?The results should also tell you what fields the search terms were found in. It's possible that you're getting more than one result for a given node because you are searching body, title, and teaser.
#4
Actually, ignore my previous message. I see the issue. The
<!--break-->comment is a special comment that allows you to manually tell Drupal where to split your nodes into teaser and body. The comment is automatically stripped out when the node is viewed -- which is why you can't see it when you inspect the nodes in the search results.If you edit any of the nodes that turn up in your search results, you'll see that the body is split into teaser and body, right? If so, this is not a bug in Search & Replace.
#5
Noted. But my thinking is that this is Drupal 5 functionality. I am currently rebuilding a transferring a corrupted D5 database to a virgin D6 database. I am doing my best to strip out these breaks as I go, but have missed quite a lot. I am not entirely sure if and how D6 respects this depricated tag, and was thinking of using Search and Replace to get rid of them all in one go.