After enabling the module, invalid urls are mapping to the node.

For instance:

  • Before enabling the module
    • A node has path content/my-node
    • Path triggers 404 content/my-node/this/does-not/exist
  • After enabling the module
    • A node has path content/my-node
    • Path no longer triggers 404 content/my-node/this/does-not/exist

Issue might be located at path_alias_xt_url_inbound_alter.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

alemadlei created an issue. See original summary.

alemadlei’s picture

Title: Invalid urls are displaying base node. » Invalid urls are not triggering 404
alemadlei’s picture

Attached is a patch that works for several tests I did using different sub pages on node paths and user paths. No other paths should be affected though.

alemadlei’s picture

Assigned: Unassigned » alemadlei