Skip to content

[DEFECT] api/v1/content/search not working with block editor fields #34151

@jdcmsd

Description

@jdcmsd

Problem Statement

It seems the api/v1/content/search endpoint breaks when calling upon Block Editor fields via searchableFieldsByContentType.

Quick example:

curl -X POST "https://demo.dotcms.com/api/v1/content/search" \
  -H "Authorization: Basic YWRtaW5AZG90Y21zLmNvbTphZG1pbg==" \
  -H "Content-Type: application/json" \
  -d '{
    "searchableFieldsByContentType": {
      "Blog": {
        "title": "snow"
      }
    },
    "orderBy": "modDate desc",
    "page": 1,
    "perPage": 20
}'

There are two demo blog posts with "snow" in their title. This call grabs both of them. So far so good. Now, let's add a tag:

curl -X POST "https://demo.dotcms.com/api/v1/content/search" \
  -H "Authorization: Basic YWRtaW5AZG90Y21zLmNvbTphZG1pbg==" \
  -H "Content-Type: application/json" \
  -d '{
    "searchableFieldsByContentType": {
      "Blog": {
        "title": "snow",
        "tags": "iceboating"
      }
    },
    "orderBy": "modDate desc",
    "page": 1,
    "perPage": 20
}'

Since only one of the two blogs has the iceboating tag, it'll only grab that one — the one about different snow sports to try. Looks good. But NOW, let's try to look within the Block Editor blogContent field:

curl -X POST "https://demo.dotcms.com/api/v1/content/search" \
  -H "Authorization: Basic YWRtaW5AZG90Y21zLmNvbTphZG1pbg==" \
  -H "Content-Type: application/json" \
  -d '{
    "searchableFieldsByContentType": {
      "Blog": {
        "title": "snow",
        "blogContent": "tricks"
      }
    },
    "orderBy": "modDate desc",
    "page": 1,
    "perPage": 20
}'

This one SHOULD grab the other "snow" article (the one on snowboard tricks) only. Instead it returns a completely empty object. No Block Editor search seems to succeed.

Steps to Reproduce

Acceptance Criteria

Block Editor fields should be searchable by this endpoint.

dotCMS Version

dotcms-core 25.12.16-01 (December 16, 2025 9:57 PM)

Severity

Medium - Some functionality impacted

Metadata

Metadata

Type

Projects

Status

Next 2-4 Sprints

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions