I am cloning this issue, as it is persisting in 2.0.0-beta4. I have reverted to 2.0.0-beta1 for the time being.

Problem/Motivation

I noticed that the dev version of the Search and Replace Scanner module stopped returning results when scanning fields of type “Text (formatted, long)”.

I tested the same case with version 2.0.0-beta1, and it works correctly, the issue only occurs in the latest dev release.

Steps to reproduce

1. Install the latest dev version of the module.
2. Create a content type with a field of type Text (formatted, long).
3. Add content that includes a searchable string.
4. Run a scan for that string.

Proposed resolution

Adjust the field scanning logic in the development branch so that it correctly handles fields of type Text (formatted, long).

Comments

joakland created an issue. See original summary.

smustgrave’s picture

smustgrave commented
Priority: Major » Normal
smustgrave’s picture

smustgrave commented
Status: Active » Postponed (maintainer needs more info)

Sorry need a little more information because we have tests for this that show it's working so there's a step we must be missing.

joakland’s picture

joakland commented

I have to confess, I don't have a ton of additional information. I upgraded the module on my site from 2.0.0-beta1 to 2.0.0-beta4, and this is when the problem began. When 2.0.0-beta1 is installed, searches produce results from body fields, i.e. Text (formatted, long). After upgrading, results from the body fields do not appear.

The confusion is compounded by the fact that on another site I run, upgrading to 2.0.0-beta4 does not produce the same problem. I have checked the logs on the site on which the failure is occurring, but there are no errors appearing there.

smustgrave’s picture

smustgrave commented

Dumb questions but just have to ask.

Are the fields regular or on paragraphs by chance?

Configuration has them still listed to be scanned?

joakland’s picture

joakland commented

Not dumb questions at all . . . and they were the first questions I asked myself! Yes, the fields are configured to be scanned. Some of the disappearing fields are in fact paragraph fields, but some are the out-of-the-box body field.

joakland’s picture

joakland commented

This issue has been resolved with the 2.0.0-beta5 release.

smustgrave’s picture

smustgrave commented

Really? That’s good to hear but surprised