Upgraded to 3.0.1 and now Saving loop when I try and save a resource

Summary

Upgraded to 3.0.1 from previous latest version on 2 and now Saving loop when I try and save a resource

Step to reproduce

N/A

Observed behavior

Everything seemed to work perfectly after the upgrade. Went to add a new resource to a blog and got the Saving animation in a loop. If I hit the browser reload it sometimes saves.

Expected behavior

Click on Save and it works !

Environment

MODX version 3.0.1 , Apache: 2.4.39, MySQL: 5.6.25, PHP 7.3.11 , Chrome and Edge

If you open the “Network” tab of your browser’s developer tools, is there an error message in the response?

Any relevant errors in the MODX error log?

Developers tools ;

Uncaught SyntaxError: Invalid or unexpected token (at ?a=resource/update&id=75:455:53)

Error log ;

loads - all relate to xpdo/xpdo/src and a db table that doesn’t exist

Blockquote [2022-05-03 02:40:41] (ERROR @ /zzzzzz/html/core/vendor/xpdo/xpdo/src/xPDO/Om/xPDOObject.php : 1443) Error 42S02 executing statement:
INSERT INTO modx_deprecated_method (definition, since, recommendation) VALUES (‘modTemplateVar’, ‘3.0’, ‘Replace references to class modTemplateVar with MODX\Revolution\modTemplateVar to take advantage of PSR-4 autoloading.’)
Array
(
[0] => 42S02
[1] => 1146
[2] => Table ‘zzzz.modx_deprecated_method’ doesn’t exist
)

Is there more information where this “Uncaught SyntaxError” occurs (or did you copy the whole error message)?


modx_deprecated_method is a new db table in MODX3.

Did you update directly to 3.0.1 or did you install version 3.0.0 first?

that was the full message in the Developer / Network console - I am not an expert user though

i went straight to 3.0.1

I think reverting to whatever version you had before and installing 3.0.0 will solve your problem. Then you can upgrade to 3.0.1 again.

Another way to go would be to install 3.0.0 somewhere else, export the deprecation table and import it into your 3.0.1 site, but you might miss some other things that happened in the 3.0.0 Setup.

BTW, it might work to just turn off the log_deprecated System Setting, though again, you may be missing other things that happened in the 3.0.0 setup.

If you have the site backed up and feel like living dangerously, you can install the UpgradeMODX extra, set your settings_version System Setting to 2.8.4-pl, and use UpgradeMODX to “upgrade” to 3.0.0, then 3.0.1. I can’t guarantee the results, but it should work. Hint: Click on the MODX logo in the Manager to go back to the dashboard where you’ll see UpgradeMODX if it’s installed.

ummm tried to restore previous backup and the whole thing 503 errors and I can’t get in to the Manager - grrr

this is the error when I try to access the Manager ;

Fatal error : Uncaught Error: Class ‘modManagerRequest’ not found in /nfs/c04/h06/mnt/59294/domains/djcdesign.co.uk/html/core/src/Revolution/modX.php:1514 Stack trace: #0 /nfs/c04/h06/mnt/59294/domains/djcdesign.co.uk/html/manager/index.php(56): MODX\Revolution\modX->getRequest() #1 {main} thrown in /nfs/c04/h06/mnt/59294/domains/djcdesign.co.uk/html/core/src/Revolution/modX.php on line 1514

Did you try clearing your browser cache and cookies along with manually deleting all files in the core/cache directory?