• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Latest update on "Laravel Toolkit" causes Errors

Küpfer

New Pleskian
Server operating system version
CentOS
Plesk version and microupdate number
18.0.48
The latest update which enables queues causes errors in applications which do not have the package "plesk/ext-laravel-integration" installed.

Instead of simply executing a command in the "plesk-ext-laravel" namespace, the "Laravel Toolkit" should first check if the package is installed.

Error:
[2023-01-26T13:21:00.443049+00:00] production.ERROR: There are no commands defined in the "plesk-ext-laravel" namespace. {"exception":"[object] (Symfony\Component\Console\Exception\NamespaceNotFoundException(code: 0): There are no commands defined in the "plesk-ext-laravel" namespace. at /var/www/vhosts/***redacted***/application/vendor/symfony/console/Application.php:632)"} []

Example-Check: array_key_exists('plesk-ext-laravel:list-env', \Artisan::all())
 
Seeing exactly the same issue - we have automated error reporting sending emails to us, and we receive multiple emails detailing this error whenever we navigate to the Laravel extension page.
 
Seeing exactly the same issue - we have automated error reporting sending emails to us, and we receive multiple emails detailing this error whenever we navigate to the Laravel extension page.
Do you have plesk/ext-laravel-integration installed?
 
Do you have plesk/ext-laravel-integration installed?
Hi @Peter Debik the problem is if you don't have the extension installed you get the error and if you have any kind of error reports you get a lot notified.
The problem is not the package, but the Laravel Toolkit in Plesk is trying to run commands for a non-existent package. It should first check if the package is installed.
In my case, I get notified by Microsoft Teams when an error occurs in one of my applications. So after integration of "queue" into the Laravel toolkit, I was notified that ALL my applications had a problem. I "fixed" it by adding the package to all applications (updates to live applications, during business hours, YAY!).
 
Back
Top