Why can I not update a package/extra?

With the improved update checks (requiring v1.8 of the SiteDash Client), we are now delegating responsibility of determining compatibility to the Package Provider that you downloaded and installed an extra from.

This means, for example, that in the case of extras installed from MODX.com, the developer of the extra flags if the extra supports MODX 2.x and/or 3.x, which the Package Provider checks when you check for updates from your MODX installation of a certain version.

For many older extras that are not actively maintained, our effort with help from the community to confirm the 3.x compatibility of extras have been reflected in the MODX repository.

For extras from modmore, it means the status of your license is checked as well. For example, if you are using Redactor v2 and have not purchased the v3 upgrade, you will no longer be offered the v3 upgrade from SiteDash for that site.

Other providers may have similar or different constraints they check for while updating, but the key change is that the providers themselves are responsible for what version(s) are offered as an upgrade target.

There are a few scenarios where an update is not available:

• You may see "No updates found" when we know of a newer release, but after checking the upgrade from your site, there are no valid upgrade targets found.

  
  

  This may happen if 1) the newer versions require a higher MODX version (e.g. if you are on 2.x but the newer versions are for 3.x only) or doesn't meet other requirements, 2) if you do not have a valid license, or 3) if the newer version is available on a different package provider only (e.g. Formalicious used to be available as a paid extra on modmore, but is now available as a free package from MODX).

  
  

  The key here is that we know a newer version exists, but after checking from your site if an update was available, it wasn't. Resolving this means looking into why the update isn't being offered.

• You may see "Up-to-date" or "Latest Release" if there is no known newer version of an extra, and as a result we did not run the upgrade check from within your site.

  The reason we only run checks when we know a newer version exists, is simple: we want to show you the available updates quickly, and we don't want to overwhelm package providers at the same time by sending massively increased traffic their way.

  We already check for new releases of extras every hour, and then run upgrade checks in the background spread out over time, so it never takes long for a new version to be available as an upgrade target.

  One scenario in which this may cause a problem, is if you're running a private package provider with your own custom extras. As those extras don't appear in our index, we never see your new versions and don't check for updates.

  To fix that, we can index your provider on your account. There is a one-time €100 fee for connecting custom package providers.

• You may see "Package not installed" if a package has been uninstalled, but still appears in the package manager of your site. We block installing updates for uninstalled extras as it is, in most cases, an indication you no longer use it.

  To fix this, login to your manager and either install a version of the extra, or remove it if you no longer use it.

• You may see "No provider associated with package" if a package is not assigned to a package provider. That means it is unsure what package provider it was installed from, and MODX is unable to check for updates in this case.

  To fix this, login to your manager, find the package in the installer, click on View Details, and assign it to a provider. Remember to save in the top right.

If you experience other issues with the package updates, please drop us an email with details and we're happy to take a closer look.