• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Joomla Toolkit - Scan fails (another one...)

ThiloS

Basic Pleskian
Server operating system version
Ubuntu 24.04.5
Plesk version and microupdate number
Plesk Obsidian 18.0.82 Update 2
I know the are several other post like that...
I have about 75 Joomla Sites managed on this server. (3 websites with the newest Joomla 5 - and Virtuemart / all other sites with Joomla 6.2)
In my case when scanning for new Joomla-Instances i get the following error:

Die Aufgabe "ext-joomla-toolkit-task\scan" ist fehlgeschlagen.
PHP Fatal error: Uncaught Error: Class "Version6af1a32b38890" not found in /opt/psa/admin/plib/modules/joomla-toolkit/vendor/joomlatools/console/src/Joomlatools/Console/Command/Site/Listing.php:114 Stack trace: #0 /opt/psa/admin/plib/modules/joomla-toolkit/vendor/joomlatools/console/src/Joomlatools/Console/Command/Site/Listing.php(189): Joomlatools\Console\Command\Site\Listing->scanDir()
#1 /opt/psa/admin/plib/modules/joomla-toolkit/vendor/joomlatools/console/src/Joomlatools/Console/Command/Site/Listing.php(190): Joomlatools\Console\Command\Site\Listing->scanDirDepth()
#2 /opt/psa/admin/plib/modules/joomla-toolkit/vendor/joomlatools/console/src/Joomlatools/Console/Command/Site/Listing.php(69): Joomlatools\Console\Command\Site\Listing->scanDirDepth()
#3 /opt/psa/admin/plib/modules/joomla-toolkit/vendor/symfony/console/Command/Command.php(259): Joomlatools\Console\Command\Site\Listing->execute()
#4 /opt/psa/admin/plib/modules/joomla-toolkit/vendor/symfony/console/Application.php(870): PleskJoomlaToolkit\Symfony\Component\Console\Command\Command->run()
#5 /opt/psa/admin/plib/modules/joomla-toolkit/vendor/symfony/console/Application.php(261): PleskJoomlaToolkit\Symfony\Component\Console\Application->doRunCommand()
#6 /opt/psa/admin/plib/modules/joomla-toolkit/vendor/symfony/console/Application.php(157): PleskJoomlaToolkit\Symfony\Component\Console\Application->doRun()
#7 /opt/psa/admin/plib/modules/joomla-toolkit/vendor/joomlatools/console/src/Joomlatools/Console/Application.php(83): PleskJoomlaToolkit\Symfony\Component\Console\Application->run()
#8 /opt/psa/admin/plib/modules/joomla-toolkit/vendor/joomlatools/console/bin/joomla(12): Joomlatools\Console\Application->run()
#9 {main} thrown in /opt/psa/admin/plib/modules/joomla-toolkit/vendor/joomlatools/console/src/Joomlatools/Console/Command/Site/Listing.php on line 114


Any ideas what to do? .. or is there an official support for this paid extension? (i can only find the Plesk Support - not a Joomla Toolkit Support...)

Greets,
Thilo
 
Just to make clear:
I edited ALL DB manually and corrected wrong "manifest_cache" settings. The error still persists.
 
Hi, @ThiloS . Does the scanner fail for all instances or only for specific websites/versions? Please run the following command for one of the instances that is failing:

Code:
  grep -n "class " /var/www/vhosts/domain.com/httpdocs/libraries/src/Version.php

or is there an official support for this paid extension? (i can only find the Plesk Support - not a Joomla Toolkit Support...)

There's no designated support team for the extension itself. Support access depends on the main Plesk license.
 
Hi Sebahat,

the scanner is meant to find new joomla-instances on the server. (in my case it's a J6.2 instance - but i don't think that the J-version matters...)
The scanner runs - but doesn't find the existing new website. And then i get the error-list in the first post.

i hope my provider can share the issue with the plesk support-team. I cannot drectly start a ticket, since i have some retail-id, which is not meant for direct support...
 
Back
Top