drupal_render() should check #cache after #type and #pre_render so that elements can set default cache behaviour

Created on 20 July 2013, almost 12 years ago
Updated 12 June 2025, 12 days ago

At the moment it is impossible for elements with a #type to set default cache behaviour because #cache is checked before element_info() is called.

This is obviously for speed, we could check #cache a second time after #pre_render, in the same way that we check #printed a second time.

This would allow elements with #type to define default render cache behaviour.

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

render system

Created by

πŸ‡¦πŸ‡ΊAustralia thedavidmeister

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

    It affects performance. It is often combined with the Needs profiling tag.

  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

  • 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