I’m finding some issues with my upgrade to 3.0.1.
On my local php 8.1 system, 3.0.1 (advanced cli installed) the resources > web shows the pages fine, but on the live site, php 7.4, it never loads, and shows this error in debugger of Chrome:
VM1591:1 Uncaught SyntaxError: Unexpected token '<'
at doDecode (ext-all.js:21:49686)
at Object.decode (ext-all.js:21:51149)
at MODx.tree.TreeLoader.processResponse (modx.tree.treeloader.js?mv=301pl:24:24)
at MODx.tree.TreeLoader.handleResponse (ext-all.js:21:474445)
at Ext.data.Connection.handleResponse (ext-all.js:21:47767)
at f (ext-base.js:21:17840)
at m (ext-base.js:21:18302)
at ext-base.js:21:8604
That’s in manager/assets/ext3/ext-all.js
Since the javascript is condensed and impossible to read, I can’t even locate where the error is occuring, but I’ve tried uploading the same file from my working local dev system and it doesn’t change anything, so it’s not something wrong in the file.
I assume there’s some subtle difference, or maybe some file is shooting bad data to the ext-all-js file, I don’t know.
It would have been nice, to put it mildly, if the upgrade instruction page for 3.0 had made it crystal clear that some key extensions won’t work, like Quip, I read through everything before doing the upgrade and was fairly unhappy to discover that quip is broken again on 3.0 due to the changes in the function/class naming etc.
I thought by waiting a few months to upgrade these types of weak spots would have been ironed out, but unfortunately that was not the case.
Using this page, which I discovered too late on another modx forum post about web resources failing to load, I got this information about our extensions:
Breadcrumbs: ?
CacheMaster: ?
getPage: yes
getResources: yes
Quip: no
RecaptchaV2: ?
Wayfinder: yes
As you can see, that page was pretty much completely useless since it didn’t even list Recaptcha2 as tested and working (it works, just fyi, so you can update that). Breadcrumbs and cachemaster I think also are working fine.
However, given the web resources tree loads fine on php 8.1 system, I assume there is some other code interfering somewhere.
Given the unclear status of extensions, even core ones like quip, I clearly made a mistake not waiting about 1 year to update to 3.0.x, and to make sure all extensions that needed upgrades had a new version before doing the upgrade. When I tried as a test to downgrade to 2.8.4 that didn’t work at all, and our site pages failed to load, so I had to go back to the not yet ready for gold release 3.0.1 version, which is really not good as a strategy in my opinion.
Should have been an extension tester or something that warned it was not compatible, but hopefully this is the only breaking update we’ll have to deal with before we all quit this project and move on with life, 10 years or so, that is, so I’ll consider my lesson learned and never do another major version upgrade.
There is one difference I just remembered, the dev site doesn’t block core/ since it doesn’t matter locally, but the live site has it blocked in .htaccess per the instructions.