Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Rather than having a custom template for the debugging data, I think it would be good to output headers for the debugging data, much like using http.response.debug_cacheability_headers: true.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 3007089-debugging-headers.patch | 8.84 KB | dave reid |
| #6 | 3007089-debugging-headers.patch | 5.17 KB | dave reid |
| #2 | 3007089-debugging-headers.patch | 5.17 KB | dave reid |
Comments
Comment #2
dave reidComment #3
dave reidComment #4
dave reidShould this rely on the
http.response.debug_cacheability_headers: trueparameter instead of this setting?Comment #5
dave reidhttps://www.drupal.org/project/xmlsitemap/issues/2810833#comment-12834311 is another example of why I think this is good to do, a user had the developer settings enabled and thought the module was broken because they were seeing the debugging output instead of the headers.
Comment #6
dave reidComment #7
dave reidFixed a couple values.
Comment #9
dave reidCommitted #7 to 8.x-1.x. Moving to 7.x-2.x for consideration.