Answered Upgrade Modx Now Got Missing Extra in Manager Toolbar Menu

UpgradeMODX 2.0.2

On second thought, that file shouldn't exist.

Looking at your error messages again, the path to each processor looks incomplete. There should be something between processors/ and getlist.php, for example. It should look like one of these:



Unfortunately, I can't think of a cause for that. Maybe someone else can.

Let me ask again, which version of UpgradeMODX did you use? It's important because I just released a new version and I need to know if there may be a problem with it.

OK. Did you use the dashboard widget or the UpgradeMODX resource?

You might try clearing the browser cache and cookies. A leftover cookie or cache file can mess up the Manager. Around the time of your upgraded versions, MODX changed the strategy for calling processors, so a cached MODX connectors file or a cookie could explain what's happening.

UpgradeMODX 2.0.2 - I used this in the dashboard widget

I did not clear the core/cache before the upgrade, I have cleared it several times since the upgrade

These 2 files do not exist:



The nearest names to those 2 files are these:

I was referring to your browser cache and cookies. Try that first and clear the MODX cache files again before continuing.

If you didn't clear the core/cache/logs directory, you can look at the setup log (install.config...), and the UpgradeModx log (upgrademodx.log). That may indicate whether any files failed to copy.

FYI, if you use the current version of the CacheClear extra to clear the cache files, it will leave the log files alone but clear everything else.

It doesn't appear that you are missing any files. Whatever is calling the processors (possibly MIGX) is not using the correct path to them.

It's possible that there's a conflict between UGM and MIGX. Try removing UpgradeMODX from the dashboard in System (gear icon) -> Dashboards. Right click on the default dashboard and select "Update Dashboard," then, right-click on UpgradeMODX and select "Remove Widget from Dashboard" (you can always add it back later). Then clear the cache files again. If that fixes the problem, it's probably a conflict. Let me know.

Hi Bob, I tried that to no avail.

I cleared my browser cache and cookies then cleared the core/cache.

Next I removed the upgrade MODX widget from the dashboard and cleared the cache. It did not fix the problem so probably not a conflict there.

I kinda think this statement is the the most probable cause:

It doesn't appear that you are missing any files. Whatever is calling the processors (possibly MIGX) is not using the correct path to them

Unsure how to investigate that.

Here's what I'd suggest. Re-attach UGM to the dashboard. Set your settings_version System Setting back to version 2.3.9-pl. Then use UGM to "upgrade" to version 2.4.0 -- the version you already have. That will put all new files in place.

Then look at the upgrademodx log and the setup log I mentioned earlier to see if there are reports of files that couldn't be copied.

Hi Bob,

I tried your suggestion but the upgrade did not succeed, after click to start I did not get to the second screen.
I got the following message in the widget:



When I opened the upgrademodx log there was the following:



In the error log there of core/cache/logs was this:



There was no set up log file in core/cache/logs .... Presumably because the upgrade cycle did not complete

btw.... the upgrademodx log file is in the exact directory that the path is pointing to.

[ed. note: jimmyjazz last edited this post 7 years, 10 months ago.]

Weird. You didn't have that file open in an editor by any chance?

If not, check the permissions on the core/cache directory and on the UGM log file.

Quote from: BobRay at Oct 30, 2018, 09:30 AM

Weird. You didn't have that file open in an editor by any chance?

I can confirm it was not open in an editor

Quote from: BobRay at Oct 30, 2018, 09:30 AM

If not, check the permissions on the core/cache directory and on the UGM log file.

Core: 755
Cache: 755
Logs: 755
Upgrademodx log: 644