Deprecate $variables['page'] in taxonomy term templates

Created on 11 July 2025, 2 months ago

Problem/Motivation

Taxonomy module copies the same $variables['page'] pattern from node module for terms, see 📌 Deprecate $variables['page'] for node.html.twig Active for details. Once that issue is committed or RTBC, we can do a similar deprecation here and rely on the 'full' view mode.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

📌 Task
Status

Postponed

Version

11.0 🔥

Component

taxonomy.module

Created by

🇬🇧United Kingdom catch

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

Merge Requests

Comments & Activities

  • Issue created by @catch
  • 🇦🇺Australia acbramley

    blocker is in

  • Pipeline finished with Failed
    20 days ago
    Total: 218s
    #578796
  • Pipeline finished with Failed
    20 days ago
    Total: 731s
    #578797
  • Pipeline finished with Success
    20 days ago
    Total: 569s
    #578811
  • 🇦🇺Australia acbramley

    The views changes for the test point out there may be some BC issues here (assuming the same for the node change) but I suppose rendering either in views using the full view mode should be somewhat rare?

  • Pipeline finished with Success
    17 days ago
    #580473
  • 🇨🇭Switzerland berdir Switzerland

    The node issue was deprecated for D13, we should probably do the same here.

  • 🇦🇺Australia acbramley

    The one deprecation message with removal D12 was accidental, have fixed that.

  • Pipeline finished with Success
    16 days ago
    Total: 5024s
    #581510
  • 🇨🇭Switzerland berdir Switzerland

    Checked all deprecations, looks good now. Added one suggestion to remove an extra space.

  • Pipeline finished with Success
    15 days ago
    Total: 735s
    #582456
    • catch committed efb07fa9 on 11.x
      Issue #3535439 by acbramley, berdir, catch: Deprecate $variables['page...
  • 🇬🇧United Kingdom catch

    Committed/pushed to 11.x, thanks!

  • 🇳🇿New Zealand quietone

    The change record should say what to use instead of the deprecated function template_preprocess_taxonomy_term.

  • 🇨🇭Switzerland berdir Switzerland

    We deprecated dozens of template_preprocess functions without specific change records/instructions, see all the issues in 📌 [pp-1] Convert Template Preprocess hooks to OOP equivalent Postponed: needs info .

    I don't think we'd strictly need to provide BC for them at all, and you're not supposed to call it directly at all, it's a more a hook (of which we removed thousands without BC) than an API function. When I started in theme.inc with those deprecations, there were a handful that were extending from each other, so I started to add BC and we kept up with that pattern. But that's mostly for generic things like table (where field_ui has a special kind of table and called template_preprocess_table() from it's own template_preprocess.

  • 🇬🇧United Kingdom catch

    Yes agreed with @berdir here - there is a theoretical possibility that someone calls preprocess hooks directly so we add best effort bc just in case, but they're considered @internal and no-one should call them, so we shouldn't tell people how to do that in a 'new' way.

  • Status changed to Fixed about 20 hours ago
Production build 0.71.5 2024