Wrong Package - akeeba/onthos GitHub Wiki

A package claims to have installed this third-party extension, but the database does not have that information. These extensions will always appear as “Incompatible” whenever you try to update Joomla! to a new version.

Why is it a problem?

This issue is similar to an Orphaned extension, but instead of missing the parent package ID completely the extension lists the wrong package ID as its parent. Meanwhile, Onthos has determined that a different package knows about this extension, but it's not set as its parent.

Since the package ID mentioned as the extension's parent does not know about this extension, when you try to upgrade Joomla to a new minor or major version this extension will appear as “Incompatible”.

Suggested fix

Onthos lets the package on your site which claims that this extension belongs to it “adopt” the extension. That is to say, the extension's parent package ID will be set to the (correct) package's extension ID.

Notes

We have seen this problem occurring only as a result of manual editing of the database. However, there are cases where manual transfer of #__extensions table records from one version of the site to another may indeed cause this problem if the package IDs for the same-named package do not coincide in the two sites. This is a concern when using third party tools to synchronise a development site with a live site. We recommend using Akeeba Backup to take a full backup of a development site and restore it on the live site, using Kickstart's option to delete all existing files and folders before extracting the backup archive to ensure a clean transfer.