• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Joomla Toolkit - Scan fails

Peter_S

New Pleskian
Server operating system version
Ubuntu 24.04.4 LTS
Plesk version and microupdate number
Plesk Obsidian Version 18.0.79 Update #7
I I have several Joomla instances on my server. When I search for instances, I get the following message:
Die Aufgabe "ext-joomla-toolkit-task\scan" ist fehlgeschlagen. filemng: Failed to change directory to '/var/www/vhosts/xxx.xx/httpdocs/joomla': No such file or directory System error 2: No such file or directory

The directory no longer exists; it was deleted earlier. Is there a cache or something else causing this? What can I do?
 
I solved it. The instance was "disconnected" in Joomla Toolkit. I activated it and restored the Joomla folders and database. Now the scan produce following message:
Die Aufgabe "ext-joomla-toolkit-task\scan" ist fehlgeschlagen.
  • PHP Warning: Undefined property: stdClass::$description in /opt/psa/admin/plib/modules/joomla-toolkit/vendor/joomlatools/console/src/Joomlatools/Console/Command/Site/Extensions.php on line 124
  • PHP Warning: Undefined property: stdClass::$description in /opt/psa/admin/plib/modules/joomla-toolkit/vendor/joomlatools/console/src/Joomlatools/Console/Command/Site/Extensions.php on line 124
 
Hi, @Peter_S . There is a registered bug EXTPLESK-14115 with similar symptoms, which should be fixed in Plesk Obsidian 18.0.80. The issue is caused by an extension registered in the Joomla site's database (jos_extensions / #__extensions table), which has an invalid manifest_cache value (e.g. the literal string false instead of valid JSON), and no matching extension files remain on disk.

Could you please try querying the DB to confirm if that's also the issue in your case:

Code:
mysql -h localhost -u <db_user> -p'<db_password>' <db_name> -e "
SELECT extension_id, name, type, element, manifest_cache
FROM jos_extensions
WHERE manifest_cache = ''
  OR manifest_cache IS NULL
  OR manifest_cache NOT LIKE '%\"description\"%';
"
 
Back
Top