Extension Manager Critical Failure

xiaoxiaobai5724

Recently, I've noticed that Extension Manager has a chance of deleting autoload.php and a bunch of files in the Composer folder when installing extensions. Even after I restored them, the logs still showed numerous errors. Online sources say the only fix is to reinstall dependencies via Composer commands—but the most frustrating part is I don't even have SSH access. Does this mean I have to start from scratch? (I can keep the database, but manually re-enabling each extension is a nightmare.)

I really hope the official team fixes Extension Manager soon. The older version worked flawlessly—it never deleted files and was rock-solid. Sure, it was slow to access from China, but I could live with that. Now? It behaves like malware, ruthlessly wiping out critical files.

xiaoxiaobai5724

This issue seems to have surfaced a long time ago. At that time, I hadn’t enabled PHP’s display_errors, so all I got was an HTTP 500 error.

Here are the exact versions I’m running:

Extension Manager: v1.0.7
Flarum: 1.8.10
PHP: 8.3

I hope the developers can finally patch this once and for all.

clarkwinkelmann

We would need to see the error message that got thrown while the extension manager was working on its last task. It should be in the storage/logs files. I believe a separate file gets created specifically for the extension manager logs.

It's expected that Composer will delete those files and replace them with the new version. This should be the very last thing Composer does, so it's unlikely Composer intentionally stops execution.

Some possible causes:

Your hosting might not be providing enough RAM or execution time and the extension manager gets killed right before the end of the process.
Your filesystem permissions prevent Composer from re-creating the files it just deleted.
You're out of disk space (always worth checking).
Unlikely in your situation would be that you have a Composer plugin installed manually or by another extension and that plugin interferes with the end of the process.

If the problem is a filesystem permission, it's possible that the same issue prevents Flarum from creating log files! Check the file permissions and try reproducing in debug mode to see the error on screen.

xiaoxiaobai5724

Composer:

    0 [>---------------------------]    0 [->--------------------------]
<warning>Package swiftmailer/swiftmailer is abandoned, you should avoid using it. Use symfony/mailer instead.</warning>
Generating autoload files

In Filesystem.php line 913:
                                                                               
  file_put_contents(/home/vol14_4/hstn.me/mseet_39377687/htdocs/forum/temp-ve  
  ndor/composer/platform_check.php): Failed to open stream: Disk quota exceed  
  ed                                                                           
                                                                               

require [--dev] [--dry-run] [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--fixed] [--no-suggest] [--no-progress] [--no-update] [--no-install] [--no-audit] [--audit-format AUDIT-FORMAT] [--update-no-dev] [-w|--update-with-dependencies] [-W|--update-with-all-dependencies] [--with-dependencies] [--with-all-dependencies] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [-m|--minimal-changes] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--] [<packages>...]

Flarum:
https://shafu.zya.me/forum/Flarum.txt

Relic System

xiaoxiaobai5724 Failed to open stream: Disk quota exceeded

This suggests you have run out of disk space on your hosting, thus the file cannot be written.