- Issue created by @Anybody
- π©πͺGermany Anybody Porta Westfalica
π Uncaught ReferenceError: loadjs is not defined after drupal core upgrade 9.5.1 Needs work seems related
- Status changed to Closed: cannot reproduce
over 1 year ago 4:30pm 8 March 2023 - πΊπΈUnited States pookmish
Maintainers do not support or troubleshoot any injected code.
- Status changed to Active
over 1 year ago 4:48pm 8 March 2023 - π©πͺGermany Anybody Porta Westfalica
lol, this isn't injected code. The injected code is
console.log('X');
You don't need to troubleshoot that, thanks - Status changed to Closed: won't fix
over 1 year ago 4:49pm 8 March 2023 - πΊπΈUnited States pookmish
Then this isn't an issue with this module.
- π©πͺGermany Anybody Porta Westfalica
Okay then for others here, not the maintainer:
The issue definitely starts to appear with this module in the combination described above.I guess the module directly or indirectly creates a situation where π Uncaught ReferenceError: loadjs is not defined after drupal core upgrade 9.5.1 Needs work is caused.
- πΊπΈUnited States pookmish
For those who observe the JS in this module more closely, this module provides no actual javascript in the module beyond the asset form page itself. Any javascript errors on any other pages are either related to other modules or the injected JS itself and will not be debugged as part of this module.
- π©πͺGermany Anybody Porta Westfalica
Thanks @pookmish and sorry, I was a bit disappointed by your reaction, because 100% sure it appears with this module, and in my case only with this module. I ensured, it's not unrelated. Still I agree the root cause seems to be in core. Still this module starts the chain, so it shouldn't be treated as if it was totally unrelated and that was what your response appeared to me.
Let's close this and focus on fixing the issue. Perhaps this one helps other users of asset_injector to find the core issue more easily.