No Code Attached Yet bug
avatar pelikanekcz
pelikanekcz
29 Jun 2026

What happened?

  1. After upgrading and reinstalling Joomla 6.1.1, the update finished with:

Error on updating manifest cache: (type, element, folder, client) = (library, phpass, phpass, 0)

After correcting that issue, the same error occurred for:

Error on updating manifest cache: (plugin, eos, plg_quickicon_eos, 0)

Both core extensions had state = -1 in the #__extensions table. After changing state to 0 for both extensions, reinstalling Joomla 6.1.1 completed without any warnings or errors.

Version

6.1

Expected result

Reinstalling or updating Joomla should complete without errors. Core extensions should not cause updateManifestCaches() to fail because of an invalid state value in the #__extensions table.

Actual result

The update completed with warnings and errors:

Error on updating manifest cache:
(type, element, folder, client) = (library, phpass, phpass, 0)

After fixing that extension, the same error occurred for:

Error on updating manifest cache:
(type, element, folder, client) = (plugin, eos, plg_quickicon_eos, 0)

Both core extensions had state = -1 in the #__extensions table. After changing state to 0, the errors disappeared and reinstalling Joomla 6.1.1 completed successfully.

System Information

Joomla version: 6.1.1
PHP version: 8.3.x
Database: MySQL (or MariaDB) xx.x
Web server: Apache
Installation type: Upgraded installation (not a fresh install)

Migration history:
Joomla 3.x → Joomla 4.x → Joomla 5.x → Joomla 6.1.1

Problem observed during:

  • Joomla update
  • Joomla 6.1.1 reinstall (Upload & Update)

Additional Comments

Investigation showed that the affected core extensions (phpass and plg_quickicon_eos) had state = -1 in the #__extensions table.

After changing state to 0 and reinstalling Joomla 6.1.1, the update completed successfully without any manifest cache errors.

avatar pelikanekcz pelikanekcz - open - 29 Jun 2026
avatar pelikanekcz pelikanekcz - change - 29 Jun 2026
Labels Added: No Code Attached Yet bug
avatar pelikanekcz pelikanekcz - labeled - 29 Jun 2026
avatar joomla-cms-bot joomla-cms-bot - labeled - 29 Jun 2026
avatar richard67
richard67 - comment - 13 Sep 2026

A state of -1 is set for extensions in the discover methods of the diverse installer adapters, e.g. for components here: https://github.com/joomla/joomla-cms/blob/5.4-dev/libraries/src/Installer/Adapter/ComponentAdapter.php#L1279

Later, when installing the discovered extensions, the state is set to zero before trying to store the database record in the extensions table in methods prepareDiscoverInstall of the installer adapters, e.g. for components here: https://github.com/joomla/joomla-cms/blob/5.4-dev/libraries/src/Installer/Adapter/ComponentAdapter.php#L639

So a state of -1 happens for old core extensions which were not properly uninstalled during a previous core update, or they have been properly uninstalled but later an old backup was restored where the files still were present, so the extension discovery has found them.

Hard to say now what went wrong at which point in the migration history.

It could have been fixed by using the discovery installation to install these extensions so you can properly uninstall them after that in the extensions manager.

Add a Comment

Login with GitHub to post a comment