Can this module search within CCK Blocks? Using this module, I ran a search query for something like this: $ARTICLE-HEADER$. Perhaps the dollar sign is tripping it up (incidentally that's left over from the Replacement Tags which I'm trying to phase out)?

Search And Replace claimed to have found six instances of that string, but not only was this number too low, it also wasn't reporting where those instances were exactly. So I didn't allow it to proceed with replacements.

Using Drupal 6.6, CCK 6.x-2.0 and CCK Blocks 6.x-1.1 here. I only decided to replace Replacement Tags because module maintainer seems to be having a hard time keeping it compatible with CCK and/or CCK Blocks (calls CCK a moving target) and I decided I would have to ditch Reptags. Unfortunately, I'm using it somewhat pervasively. Thinking Search and Replace would be a good candidate, I installed it without errors, but it can't seem to find my tags.

Comments

btopro’s picture

if the tags are in CCK values then this won't work (atm) as it only searches body content and title fields. I'd accept a patch but I probably won't be able to get to anything until early next year (porting our infrastructure to D6 and currently upgrading the outline designer module).

silurius’s picture

Exactly. I'd misspoken - I'm not actually searching within CCK Blocks but CCK Fields. I'll find another way. Thanks for the quick response! It was very helpful to know for sure today.

btopro’s picture

Status: Active » Closed (fixed)
TimG1’s picture

Category: bug » feature

Just changing to feature request. Can't wait to see this too! =)

-Tim

btopro’s picture

Just as an update... the module needs a lot of work. I found regex issues with my replacement algorithm in using it internally. Work's been crazy but after a few meetings and the development of a new module (think self-generating multi-site configurations) then I'll be going back through and patching / doing bug fixes on all my modules. This one is first priority so I'll look into what it would take to do a replacement on CCK fields. I don't think it would be too difficult to do an array search / replacement so as long as the fields would travel along w/ a node_load() I should be able to modify any / all values and then save it back (similar to how I do now but just generically search the array).

Look for progress to start being made on this and other projects in the next 2-3 weeks. Sorry for the delay, semester starts swamp me.