Error messaging when node in source path

Created on 30 August 2023, over 1 year ago
Updated 31 August 2023, over 1 year ago

Problem/Motivation

When you create a source path with "node" (node/999999999) in the path an error is generated that is not properly processed. It appears to be an issue with how the error is out put, and doesn't appear when other none existent paths (like "skdjhfsjdfhskjdhfkshf")

β€œAjaxError: An AJAX HTTP error occurred. HTTP Result Code: 404 Debugging information follows. Path: /admin/config/search/redirect/add?ajax_form=1 StatusText: error ResponseText: {"message":"The \u0022node\u0022 parameter was not converted for the path \u0022\/node\/{node}\u0022 (route name: \u0022entity.node.canonical\u0022)"}"

Steps to reproduce

Add a new redirect: /admin/config/search/redirect/add
Input the source for a non existent node (we need this after an old site migration): node/9999999999

Witness error appears to contain stacked errors.

Proposed resolution

I think that issue is either that the method for returning the error in "core/lib/Drupal/Core/ParamConverter/ParamConverterManager.php (102)" is improper, and should be handled at a higher level (maybe a AjaxParamNotConvertedError.php file) or else, the query to the Route checker needs to be handled different.

Not sure about proper approach / causal root issue

πŸ› Bug report
Status

Active

Version

1.9

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States will kirchheimer New Orleans

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024