Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
At the moment theme registry cache built has been limited for GET requests only because for some reason we don't allow setting theme registry persistable on POST requests.
Proposed resolution
Make theme registry persistable on POST request.
Remaining tasks
-Write tests
-Write patch fixing the problem
User interface changes
-
API changes
-
Comments
Comment #1
pfrenssenThis seems more like a bug to me.
Comment #2
lauriiiPostponing till #2472285: Make theme registry cache collector lazyload gets in
Comment #3
joelpittetKind of sounds like a feature request... @lauriii could you flush out the issue summary a bit further to explain why you need this? Also if it's a feature request bump it to 8.1.x or 9.x please
Comment #4
joelpittet@lauriii do you mean "between POST requests" instead of "on POST request"? I'm not following where it's persistable, where is this in the code?
Comment #6
xjmAdding this functionality would definitely be a minor version target, so moving to 8.2.x.
Comment #7
lauriiiThe core committers (@xjm, @alexpott, @catch, @effulgentsia, @Cottser) and theme maintainers (@lauriii, @joelpittet) discussed this issue today and agreed that this issue should be marked as a duplicate for #2472285: Make theme registry cache collector lazyload.
This was originally created because it might make sense to change this assumption in some use cases where there is a lot of rendering is done on the POST requests. That is not possible because of #2472285: Make theme registry cache collector lazyload unless one overrides the
__construct
method to change it's behavior.We agreed that we don't have to change this assumption by default, but we should instead fix the duplicated issue to allow module developers easily change the behavior.