Package built using packman can't check if updates available from MODX repository

Hi all,

pretty much as the title suggests. I'm not sure if it's a bug or I've missed something packaging my extra up. When I release a new version of my extra sites I already have it installed on don't show that an update is available, even if I force it to check. I get this error every time:



How do I rectify this so my package can be kept up to date?

Thanks

Packages are only recognized for update if they are downloaded through Package Manager. If you put the code in core/packages and search locally for packages, there's no "provider" and no updates, and when you check, the package isn't in the MODX repository so the check fails.

Did you submit the package at http://modx.com/extras?


You might also be interested in MyComponent if you're going to be updating the package. It's a pain to keep recreating it through PackMan and MyComponent will probably help you create a more complete package. http://bobsguides.com/mycomponent-tutorial.html

Hi BobRay,

Thanks for the reply. Yeah I figured about the local packaging not checking for updates, which is no big deal while I'm testing packages out. Mine is on the repo and has been for quite a while. Every site I've used it on so far doesn't seem to let me know when there's an update to it though.

http://modx.com/extras/package/jsonderulo

When I've got more time I'll take a look through that documentation for MyCOmponent and maybe give it a whirl. PackMan is excellent but it's definitely painful to keep manually having to recreate it every time I want to make a new transport package! [ed. note: markh last edited this post 13 years, 8 months ago.]

I've changed the package key in the MODX.com side of the repository to "jsonderulo" instead of "jsonderulo23" which sorted out the updates. I'm not sure what caused that, but I managed to update JSONDerulo on my site now.

The downside is that the link http://modx.com/extras/package/jsonderulo23 is now invalid (it is now http://modx.com/extras/package/jsonderulo), and I can't seem to redirect package urls, so you'll have to update the link where ever you keep it..

That's excellent news Mark, thanks ever so much for sorting that out for me!
Should no package have numbers after the package name in the URL?

No problems about the link, I'll update the link from the GitHub repo and put out a new link on Twitter, etc

ummm... your link in your post above is also bad now.

Quote from: sottwell at Jan 12, 2013, 06:56 PM

ummm... your link in your post above is also bad now.

This problem seems to have cropped up again. I've noticed it on versions 1.7.0 and above. I've installed 1.7.3 on a site and it tells me there is an upgrade to 1.7.1!!

Can anyone check/sort this please?