Evaluate and document each use of base: in core

Created on 31 January 2015, over 10 years ago
Updated 2 July 2025, about 17 hours ago

Problem/Motivation

The base: scheme is specifically intended for internal, base-relative, non-routed URLs used in code, e.g. base:robots.txt. There are 70-80 non-documentation uses in core. In some of these cases, it's unclear why base: is used (vs. a route, entity:, user-path:, etc.)

Proposed resolution

Review all the uses. In each case, evaluate whether it actually must be base:, and if so, document why.

Beta phase evaluation

<!--Uncomment the relevant rows for the issue. -->

Remaining tasks

For each use:

  • Review it and determine if a route, entity URI, or user-entered URI is appropriate instead, or if there's a different usecase.
  • If it should indeed be base:, document why.
  • If it should be something, else, file a separate issue to fix it.

User interface changes

None.

API changes

None.

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

routing system

Created by

πŸ‡ΊπŸ‡ΈUnited States xjm

Live updates comments and jobs are added and updated live.
  • Documentation

    Primarily changes documentation, not code. For Drupal core issues, select the Documentation component instead of using this tag. In general, component selection is preferred over tag selection.

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024