Udated Favorites don't seem to be shown as needing update in main update precedure

Community Feedback
1

Hi,

We just noticed that we had several updated favorites (plugins and theme) but when checking the standard updates pages for plugins and themes, those updates were not shown as needed/available?

Examples:
Astra Pro 4.11.12 → 4.13.4
SEOpress Pro 9.5 → 9.9.2

However, these updates did not show.

Are favorites ignored for that? (which would be surprising and undesired)
And if not, how can we fix them being ignored at this time?

With thanks and kind regards

2

Hey @SuppY

Just to make sure I’m reading this correctly, are Astra Pro and SEOPress Pro installed on your child sites, but the available updates are not showing under the regular MainWP Dashboard’s Updates page?

If yes, the fact that you installed these plugins via Favorites extension is not involved in that available update detection in any way.

Please check on one of the involved child sites if the available update is detected:

  1. Log in to the child site’s WP Admin.
  2. Go to Dashboard > Updates.
  3. Confirm whether Astra Pro / SEOPress Pro updates are shown there.
  4. Also confirm the plugin/theme license is active on that child site.
  5. Then sync that child site from MainWP and check the MainWP Updates page again.

If the update does not show on the child site’s own Dashboard > Updates page, MainWP will not be able to detect it either.

If the update does show on the child site’s standard WordPress Updates page, but still does not show in MainWP after syncing, let us know and we can look further into whether a premium-plugin/theme compatibility filter is needed.

3

Yes, but it seems that also custom-made plugins, for example, that we have uploaded the new version to the correct directory, are not taken into account. (so, as an example, plugin X v1.1.0 is installed on child sites and as favorite, v1.1.1 is uploaded and the favorites version correctly updates to v1.1.1 but the update is not seen in the normal general update pages and therefore not performed).
We’re looking into this further as someone, regrettably, updated all manually a few days ago …
I’ll get back to you asap.

4

Uploading a new version of the custom plugin to the Favorites add-on, will not automatically install that new version to Child sites, or make the Dashboard report an available update for that plugin on the Updates page.

This was never the case with our Favorites add-on.

So, it is necessary to once more repeat the process of installing that plugin from the Plugins > Install Plugins > Install from Favorites page

5

It’s not about automatic installation, we never want that but it doesn’t even show up as ‘update available’ on the normal updates available page.
I’m sure that is meant to work as what is the use of adding it to favorites and especially the updating their version numbers otherwise? Admin may still not realise that an update has been uplaoded and is available …

Otherwise, this would be a very unexpected and undesirable issue and may be a (partial) show stopper. We have about 100 items in favorites (in subsets) of which quite a few custom made :frowning:

PS and I find it rather confusing, why get version updates there …and then not get used to define what needs updating?)

6

As I mentioned above, Favorites does not act as an update source for the regular MainWP Updates page.

Updating the item in Favorites only updates the stored ZIP/version there, so it can be installed again from: Plugins > Install Plugins > Install from Favorites

The regular Updates page only shows updates detected by the child site’s own WordPress update system after sync.

So this is expected behavior, not a bug. If you’d like Favorites to work as a custom update repository, please submit that as a feature request at voice.mainwp.com so other users can vote on it.