- Issue created by @ELC
- πΊπΈUnited States jrb Raleigh-Durham Area, NC, USA
This looks to be due to this core change: π Use MessagesCommand in BigPipe to remove special casing of the messages placeholder Fixed .
- πΊπΈUnited States jrb Raleigh-Durham Area, NC, USA
The patch here is a workaround for this issue: #3456176-45: 10.3 upgrade now missing status-message theme suggestions β .
- π¦πΊAustralia ELC
Applying patch #3456176-45: 10.3 upgrade now missing status-message theme suggestions β allows ksm() to work again. Thank you!
This isn't a permanent solution as it removes the new functionality from bigpipe which will not be removed from core.
The bigpipe changes push status messages into ajax "MessageCommand". The Kint code then doesn't execute on the message as it's not rendered on page load, but sometime after.
As a fix to work with new core, how can the Kint javascript be configured to run after MessageCommand has been rendered into the page?
- πΊπΈUnited States jrb Raleigh-Durham Area, NC, USA
This is not really a problem with this module (devel_kint_extras)-- it's a problem with Devel itself and its implementation of
ksm()
. However, the Devel module don't use the issue tracker here on d.o. Instead, it uses GitLab.There's an issue for this problem here that includes two possible solutions:
https://gitlab.com/drupalspoons/devel/-/issues/525#note_1988672373
- Status changed to Closed: won't fix
2 months ago 7:28am 9 July 2024