Upgrade to 3.0 failed with multiple problems

[dejaya]

Hey @pixelstuff …

@pixelstuff

Also figured out PHP 8.0 is keeping the package manager and resource tree from loading. Dropping down to 7.4 fixed those.

If returning to PHP 8.0 still leaves you with a broken package manager - in my experience, this will likely be caused by an extra which doesn’t play well with PHP 8.0 and / or MODX 3.x.

findParent and Batcher are examples of extras which have caused this behaviour in the package manager for me in 3.x. getDate has caused this issue for others. There will be other offenders.

My original solution was to remove the extra from the modx_transport_packages table - but @halftrainedharry provided a simpler solution: change the value of the column “provider” to 0 for the offending row in the database table modx_transport_packages (instead of deleting the whole row).

It may take some trial and error but you should be able to find the culprit this way.

Look out for older extras and you can also check this Sitedash list for non-modx3-compatible extras.

Hope that helps.

Some other discussions around this issue:

Installing Modx 3.0 alpha-2

Thanks for all your troubleshooting on this guys - I’ve referred back to this thread on a few occasions now as I’ve had the erroring Dashboard problem and the non-functional Package Manager problem on several occasion after upgrades to MODX 3.x. The Updates dashboard widget definitely seems to cause problems on some sites but not others. Removing it from the Dashboard seems to fix it. In my latest site with the Package Manager problem, deleting the extra, findParent from the modx_transport_pac…

Package Manager crashed by loading getDate (MODX 3.0.1-pl)

Hi @videoschlumpf I’ve had this issue a few times and the only solution I’ve found is to remove the offending extra from the modx_transport_packages table in the database. You may want to backup your database, or at least that table, first.