UPSTREAM FIX

magento2-38883: GraphQL route query erroring for a disabled CMS page

Community fix magento2-38883 merged into magento/magento2 on 2025-08-28, released in 2.4.9; applies cleanly to 17 releases from 2.4.7 to 2.4.8-p5.

Fixes the GraphQL route query erroring for a disabled CMS page edited

Pull request title: graphql (magento 2.4.6-p4 ) - error when try to get cms page with not active status
Pull request: magento/magento2#38883
Issues: #38877 human
Author: @digitalrisedorset
Merged: 2025-08-28
Fixed in: 2.4.9
Reported on: 2.4.6-p4
Categories: Content, GraphQL
Components: magento/module-url-rewrite-graph-ql

Labels

Area: Content / CMS
Component: GraphQL
Priority: P2
Severity: —
Reported on (labels): 2.4.6-p4

Issue

Title and steps come from the upstream issue and pull request.

Description

Actual response

{
  "errors": [
    {
      "message": "Internal server error",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "route"
      ]
    }
  ],
  "data": {
    "route": null
  }
}

Steps to reproduce

1. Install fresh magento 2.4.6-p4 with sample data.
2. go to magento admin - Content - Pages
3. edit "About us" page - set status "Disabled"
4. send this graphQl query

{
  route(url: "about-us") {
    redirect_code
    relative_url
    type
  }
}

Expected result

Expected response

{
  "data": {
    "route": null
  }
}

Actual result

Actual response

{
  "errors": [
    {
      "message": "Internal server error",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "route"
      ]
    }
  ],
  "data": {
    "route": null
  }
}

Taken from the upstream issue.

Error signatures

{"exception":"[object] (GraphQL\\Error\\Error(code: 0): No such entity. at )
[previous exception] [object] (Magento\\Framework\\Exception\\NoSuchEntityException(code: 0): No such entity. at )"} []

Code match per tag

Each tag was checked with git apply --check against that tag's files. A clean match means the change applies; it is not a test result. Tags that already contain the fix are marked.

Line	Code match per tag	Tests
2.4.6	2.4.6 conflict 2.4.6-p1 conflict 2.4.6-p2 conflict 2.4.6-p3 conflict 2.4.6-p4 conflict 2.4.6-p5 conflict 2.4.6-p6 conflict 2.4.6-p7 conflict 2.4.6-p8 conflict 2.4.6-p9 conflict 2.4.6-p10 conflict 2.4.6-p11 conflict 2.4.6-p12 conflict 2.4.6-p13 conflict 2.4.6-p14 conflict 2.4.6-p15 conflict	2.4.6: no test data 2.4.6-p1: no test data 2.4.6-p2: no test data 2.4.6-p3: no test data 2.4.6-p4: no test data 2.4.6-p5: no test data 2.4.6-p6: no test data 2.4.6-p7: no test data 2.4.6-p8: no test data 2.4.6-p9: no test data 2.4.6-p10: no test data 2.4.6-p11: no test data 2.4.6-p12: no test data 2.4.6-p13: no test data 2.4.6-p14: no test data 2.4.6-p15: no test data
2.4.7	2.4.7 clean 2.4.7-p1 clean 2.4.7-p2 clean 2.4.7-p3 clean 2.4.7-p4 clean 2.4.7-p5 clean 2.4.7-p6 clean 2.4.7-p7 clean 2.4.7-p8 clean 2.4.7-p9 clean 2.4.7-p10 clean	2.4.7: no test data 2.4.7-p1: no test data 2.4.7-p2: no test data 2.4.7-p3: no test data 2.4.7-p4: no test data 2.4.7-p5: no test data 2.4.7-p6: no test data 2.4.7-p7: no test data 2.4.7-p8: no test data 2.4.7-p9: no test data 2.4.7-p10: no test data
2.4.8	2.4.8 clean 2.4.8-p1 clean 2.4.8-p2 clean 2.4.8-p3 clean 2.4.8-p4 clean 2.4.8-p5 clean	2.4.8: no test data 2.4.8-p1: no test data 2.4.8-p2: no test data 2.4.8-p3: no test data 2.4.8-p4: no test data 2.4.8-p5: no test data
2.4.9	2.4.9 conflictcontains the fix	2.4.9: no test data

Triage

Model @cf/cloudflare/clef. Probability this is a bug fix: 97.8%. Probability it is security relevant: 0.7%.

Show the model's answers and probabilities

Question	Answer	Probabilities	Confidence
Change kind	bugfix	bugfix 94.9%, refactor 2.4%, feature 0.8%, tests_only 0.8%, dependency 0.6%, docs_only 0.6%	88.2%
Area	graphql_api	graphql_api 95.9%, other 0.9%, framework 0.8%	90.9%
Reported version	2.4.6-p4	2.4.6-p4 65.8%, 2.4.6 3.1%, 2.4.6-p5 1.2%	42.8%
Scope	0.89 of 2	1 54.0%, 0 28.4%, 2 17.6%	10.5%
Risk	0.19 of 2	0 83.2%, 1 14.7%, 2 2.1%	57.1%
Worth backporting	1.62 of 2	2 70.0%, 1 22.2%, 0 7.9%	31.7%

Download

For cweagans/composer-patches, choose a version below and download the bundle. Copy its magento2-38883/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Test files are always removed; paths are relative to each package root, using the default -p1 level.

Bundle README (what the ZIP ships)

# magento2-38883

Community fix merged upstream into magento/magento2, adapted by magento.watch.
This is not a patch published by Adobe.

Pull request: https://github.com/magento/magento2/pull/38883
Issue: https://github.com/magento/magento2/issues/38877
Author: @digitalrisedorset
Source commit: b1febc640961bd0aadcf50dbd32afa15e451d8ee
Modifications: test files and documentation removed, paths rewritten relative to each Composer package.
Licence: OSL-3.0 / AFL-3.0, as the original Magento Open Source code.
Maintainer: Łukasz Bajsarowicz (@lbajsarowicz)

Licence: Magento Open Source code under OSL-3.0 and AFL-3.0. The bundle carries the original author, source commit and the list of modifications.