• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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