• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/

Issue Bug Report: Laravel Toolkit 1.5.4 fails during "laraveldeployskeletontask" on a clean install (Composer 2.9.2)

emretunahan

New Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
18.0.74.3
Merhaba,

Laravel Toolkit extension during a fresh application installation. Even on a brand new, empty domain, the "Create Laravel skeleton" task fails at the "Installing Composer dependencies" step.

Environment Information:

  • Laravel Toolkit Version: 1.5.4-4319
  • Composer Version: 2.9.2 (2025-11-19)
  • PHP Version: 8.3.28 (cli)
  • Server OS: Linux (Plesk environment)
Problem Description:When attempting a clean installation via the Laravel Toolkit GUI, the process consistently fails during dependency installation. Although it is a fresh install on an empty directory, Composer attempts "35 removals" which triggers a prePackageUninstall event.

This leads to a fatal error because the script tries to include files that are being removed or are missing from the newly created skeleton. Specifically:Message: PHP Warning: include(.../vendor/composer/../sebastian/version/src/Version.php): Failed to open stream: No such file or directory.

Key Observations:

  1. This is happening on a clean domain with no existing files.
  2. 2.8.12 would resolve this, but I am using 2.9.2 and the issue still persists.
  3. The toolkit version is the latest available (1.5.4).
It seems the deployment task ext-laravel-task\laraveldeployskeletontask has an inherent conflict in how it handles the initial composer install command for the skeleton app.

Please investigate why the skeleton deployment is failing despite having the most up-to-date environment.

Best regards.
 

Attachments

  • fbc8150d-d8c3-4d98-84fe-89278c658d5a.png
    fbc8150d-d8c3-4d98-84fe-89278c658d5a.png
    91.3 KB · Views: 2
Thank you for the report, @emretunahan . An internal task for further investigation is open. Our team will review and address the behavior soon. I will follow-up with more details as soon as possible. Thank you for your patience in the meantime.
 
Back
Top