Answered Package Updates Not Working in 2.4.0 Updated Installation

Clicking the "Check for updates" button on any of the 22 packages in this 2.4.0 installation updated from 2.3.6 results in an Error alert box. The error message: "provider_err_nf". The "Check for updates" function had been working normally under 2.3.6. Does anyone know what "provider_err_nf" means and what to do about it?

Sounds like the provider was offline at the time, which happens from time to time, or perhaps the link to the provider got corrupted. Check the database, the transport_providers table, and make sure that the service_url for the modx.com provider is http://rest.modx.com/extras/

This is presuming that the extra you checked was from the MODX repository.

Quote from: sottwell at Sep 05, 2015, 10:38 AM

Sounds like the provider was offline at the time, which happens from time to time, or perhaps the link to the provider got corrupted. Check the database, the transport_providers table, and make sure that the service_url for the modx.com provider is http://rest.modx.com/extras/

This is presuming that the extra you checked was from the MODX repository.

I checked, and the service_url is correct. Tried again with the same result. Actually, it's not just one extra, it's 22 (and was 23 before I removed Captcha). I get the error message alert box on all of them.

Did you clear your browser cache and the MODX cache after the upgrade?

Quote from: sottwell at Sep 05, 2015, 12:29 PM

Did you clear your browser cache and the MODX cache after the upgrade?

Indeed. Plus I just tried deleting the entire contents of /core/cache, then logging in to the Manager, dumping my browser cache, and immediately trying the update buttons again. No difference -- still get the error message on every button.

This problem is getting stranger and stranger.

After removing Captcha to await the time when it and 2.4.x will become compatible, I had 22 packages installed. None of them can successfully check for the presence of an update. Clicking the button returns the error message "provider_err_nf." I have no idea what it means. I followed all of Susan's suggestions above, but sadly, none of them made any difference.

I then installed UpgradeMODX. Once it was properly installed (as evidenced by the presence of its widget in the Manager), I tested its update button, expecting the same response as the other packages. Big surprise -- this one works! I just got finished checking all 23 of them again. UpgradeMODX returns the correct string, "Your package is already up-to-date at: upgrademodx-1.2.1-rc", while all of the other 22 (including Bob Ray's SPForm) still return "provider_err_nf."

Does anybody have any idea what's going on here, and how to fix it? Bob Ray, what are you doing differently in UpgradeMODX to enable it to successfully check for updates when all the others, including another that you wrote, fail? Whatever it is, I think it could well point to the cause of this problem -- and its solution.

Am I the only one experiencing this problem? So far, no one else has mentioned it here.

I think I did have that problem briefly on one site. I think I cured it by reloading the page, but I'm not sure. I'm pretty sure there's nothing different about UpgradeMODX.

Quote from: BobRay at Sep 09, 2015, 10:13 PM

I think I did have that problem briefly on one site. I think I cured it by reloading the page, but I'm not sure. I'm pretty sure there's nothing different about UpgradeMODX.

Well, to quote Dave Barry, "I'm not making this up." I just checked again, and the situation is unchanged. So there has to be something different about UpgradeMODX.

The main point is, though, that until I upgraded this site to 2.4.0, there was no problem checking for updates on any of the packages, but now, the mechanism is broken on every package -- with one exception.

I wish I had a good answer for you. UpgradeMODX was created with the exact-same build script as my other extras, and I can't think of anything exotic about the package. It may be different only because it's the most recently installed package.

Is modx.com listed as the provider for the other packages (and for UpgradeMODX)?

Quote from: BobRay at Sep 10, 2015, 09:41 AM

I wish I had a good answer for you. UpgradeMODX was created with the exact-same build script as my other extras, and I can't think of anything exotic about the package. It may be different only because it's the most recently installed package.

Is modx.com listed as the provider for the other packages (and for UpgradeMODX)?

Bingo! Bob, I believe you hit on something there. modx.com is listed as the provider for UpgradeMODX only. On all the other packages, that column is blank -- including on some packages installed as long ago as April 2012, and which have never been uninstalled.

Does that give you any idea what's going on here? [ed. note: magoldberg last edited this post 8 years, 8 months ago.]