All Low add-ons are now owned by EEHarbor. Read the blog post.

Support archive

Find and Replace missing fields

travisb 15 Oct 2014 15:56 question, complete

In find and replace in low search, I'm not seeing fields show up for a particular field group that's used in multiple channels. There are plenty of text input fields in that group, but only "title" and one text input field are listed under the channels sharing that field group.

(EE 2.9.2 and Low Search 3.2.0 in local dev.)

Thanks!

Replies

  1. Low 15 Oct 2014 16:00

    LS only supports certain field types for Find & Replace. Which types are you missing?

  2. travisb 15 Oct 2014 16:16

    There are about 59 fields in the group, and of the one's supported most are Text Input, with a couple Grid and Editor. Of those, only 1 text input is showing in LS.

    The only thing really different in this field group I can think of is that it has a Store Product Details field type.

    travisb 15 Oct 2014 16:22

    Don't think the Store field type is a problem, since it didn't affect another test channel's find/replace.

  3. travisb 15 Oct 2014 17:02

    Ok, I think I've found out what it is. Where you eliminate the fields in publish layouts that are hidden, there is no way to distinguish between a field that's hidden in 1 channel but showing in another (around 1373+ in mcp.low_search.php) .

    So in my case that explains the one field that shows up, because it wasn't hidden in all channels using that product group.

    I'm no sql guru, but it seems the solution would have to be per channel subqueries for "Get list of channels and fields for selection", or as many queries as channels. Like I said, no guru....

    Anyway, something fun for someday :)

  4. Low 15 Oct 2014 18:06

    Does that mean you've got it sorted for now?

  5. travisb 15 Oct 2014 18:15

    It won't work completely for me in this case. A field visible in one channel that's also hidden in another channel won't show up in the Find & Replace Channel list.

    So, if you end up with a workaround or update for that someday that would be great. Thanks.

  6. Low 15 Oct 2014 18:18

    Okay, I'll look into it.