Try to make the comment form cacheable.

Created on 3 August 2015, almost 10 years ago
Updated 26 June 2025, about 1 month ago

Problem/Motivation

I'm curious, could this username display be a placeholder for itself so most of the form could be cached? Is there an issue for that?

#18: I've considered that too, and even tried it a long time ago (>1 year ago). It doesn't work because Form API tracks which fields exist in a given built form, for validation/security purposes. We cannot just add a form field at a later time.

I think the problem is due to the usage of type #item instead of just #markup ... we should not use that value for authenticated users ... so #markup should be enough.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

comment.module

Created by

πŸ‡©πŸ‡ͺGermany dawehner

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

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

  • 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.

Production build 0.71.5 2024