-
☆ A M B ☆
- 1,780 Posts
You might try uploading the packages manually. You should be able to see all the versions in the packages folder. If the newest version is within, the update button should light up.
Versions remain in the packages folder (core/packages) when upgrading via package management. Download the package at the repository
http://modx.com/extras/, unzip, then upload the transport.zip file to core/packages. The update should light up. It also might be another separate entry in packages so look for it.
I can't answer why... but there's a work around with manual uploading.
I asked about notification in manager for new packages versions in repository.
Updated first message. English is not my native language =)
-
☆ A M B ☆
- 3,141 Posts
It looks like you say it it compatible up to 2.2, I would suggest not setting that. I'm not up to speed on the exact inner workings of the MODX transport provider, but I think it may be interpreting it differently than you and I.
Now i cant change this. If i leave it field blank - after saving it set to MODX 2.2
But in GetResources it is blank. I will try again on next package update.
Did you manage to resolve this?
Even clicking 'Check for Updates' I get 'Your package is already up-to-date at...' even though the Package Manager has a more recent version available.
No.
I think this is problem of repository, not packages.
I have a similar problem. Two separate MODx sites - both running 2.2.5. One of them, the Ace package is v 1.3, however, the second one is 1.2.1 rc2. This second site is not seeing an update to 1.3. and even clicking on Check Updates, it says my package is already up to date at 1.2.1 rc2.
Any idea what can cause this?
I know this happened with another addon and I simply removed it from the list of Packages and redownloaded the latest version but its a little bit of a pain if no updates show up for the packages that are installed, and I have to manually check version numbers.
John
Same problem here! Currently the Ace package doesn't update.