v0.9.5 does not work with Concrete CMS v8.5.7
Permalink Browser Info Environment
I attempted to update my current site with the newest version of the package but when I do it gives me this error in the Console when I try to add a Login Redirect
If v0.9.5 is only supposed to be used on v9 sites I would recommend that you change the $appVersionRequired in the controller.
Uncaught TypeError: Cannot read properties of undefined (reading 'activateContext') at HTMLDocument.<anonymous> (add:1009) at i (jquery.js?ccm_nocache=1a72ca0f3692b16db9673a9a89faff0649086c52:2) at Object.fireWith [as resolveWith] (jquery.js?ccm_nocache=1a72ca0f3692b16db9673a9a89faff0649086c52:2) at Function.ready (jquery.js?ccm_nocache=1a72ca0f3692b16db9673a9a89faff0649086c52:2) at HTMLDocument.K (jquery.js?ccm_nocache=1a72ca0f3692b16db9673a9a89faff0649086c52:2)
If v0.9.5 is only supposed to be used on v9 sites I would recommend that you change the $appVersionRequired in the controller.
Type: | Ticket |
---|---|
Status: | Resolved |
0.9.5 is for 9.0+. The compatibility for 8.5 is set to 0.9.4. Not sure why Concrete is serving that version to you. Try downgrading / replacing with 0.9.4 for now.
Thanks, that's what I was assuming after it happened, I was surprised the CMS even let me install it.
I don't use the Projects stuff in the community because it's down so often, so it wouldn't "serve" me a certain version, I just download them and manage the versions myself. Would be nice if there was something in the Version History or the Changelog that said "This version is for v9 ONLY".
I don't use the Projects stuff in the community because it's down so often, so it wouldn't "serve" me a certain version, I just download them and manage the versions myself. Would be nice if there was something in the Version History or the Changelog that said "This version is for v9 ONLY".
I'll try and throw something in there. Thanks for the report!
I went ahead and updated the version history and also restricted the installation to v9. Should be good for the future. Closing this issue now.