Extension Manager Stable Release & Install Flarum Via ZIP File

SychO How to use and configure it?

chrisc297 Anyone??

chrisc297 check the storage/logs directory. There should be a file specifically for the extension manager.

What will the authentication section be like?

serdo it allows you to set up your install for premium extensions for instance, see https://docs.flarum.org/extensions#adding-a-composer-repository

Can this be installed despite lots of other extensions already being installed? Thank you

Jbugy yes

luceos thank you

composer update flarum/extension-manager

Do not run Composer as root/super user! See https://getcomposer.org/root for details
Continue as root/super user [yes]? yes
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Installing dependencies from lock file (including require-dev)
Nothing to install, update or remove
Package nunomaduro/larastan is abandoned, you should avoid using it. Use larastan/larastan instead.
Package php-http/message-factory is abandoned, you should avoid using it. Use psr/http-factory instead.
Package swiftmailer/swiftmailer is abandoned, you should avoid using it. Use symfony/mailer instead.
Generating autoload files
212 packages you are using are looking for funding.
Use the composer fund command to find out more!
Found 3 security vulnerability advisories affecting 1 package.
Run "composer audit" for a full list of advisories.

Not Working Update 1.0.2 -> 1.0.3

luceos

`[root@ServiceData html]# composer show flarum/extension-manager
Do not run Composer as root/super user! See https://getcomposer.org/root for details
Continue as root/super user [yes]?
name : flarum/extension-manager
descrip. : An extension manager to install, update and remove extension packages from the interface (Wrapper around composer).
keywords : composer, extensions, manager, packages, updater
versions : * v1.0.2
released : 2024-02-04, 4 months ago
type : flarum-extension
license : MIT License (MIT) (OSI approved) https://spdx.org/licenses/MIT.html#licenseText
homepage :
source : [git] flarum/extension-manager.git 4393278faa2362f64aeca07b96f565a19c1ad04a
dist : [zip] https://api.github.com/repos/flarum/extension-manager/zipball/4393278faa2362f64aeca07b96f565a19c1ad04a 4393278faa2362f64aeca07b96f565a19c1ad04a
path : /...../khatvongsong.vn/html/vendor/flarum/extension-manager
names : flarum/extension-manager

support
issues : flarum/frameworkissues
source : flarum/extension-manager

autoload
psr-4
Flarum\ExtensionManager\ => src/

requires
composer/composer ².3
flarum/core ¹.8

requires (dev)
flarum/tags *
flarum/testing ¹.0.0`

And

[root@ServiceData html]# composer why-not flarum/extension-manager 1.0.3
Do not run Composer as root/super user! See https://getcomposer.org/root for details
Continue as root/super user [yes]?
flarum/extension-manager v1.0.3 requires composer/composer (^2.7)
flarum/flarum - does not require composer/composer (but 2.6.6 is installed)
Not finding what you were looking for? Try callingcomposer require "flarum/extension-manager:1.0.3" --dry-runto get another view on the problem.

Litalino have you tried running composer update -W?

Darkle Well, that's interesting. I just install the Flarum (with no public zip) and extension manager just looks like fakruzaruret 's screenshot.

Installed the extension, works fine, then I did a global update and I got an error saying vendor/autoload.php is missing, so I did composer install, and now I got the following error:

`Warning: Undefined array key "data" in example.com/vendor/flarum/core/src/Frontend/Content/CorePayload.php on line 57

Fatal error: Uncaught Laminas\HttpHandlerRunner\Exception\EmitterException: Output has been emitted previously; cannot emit response in example.com/vendor/laminas/laminas-httphandlerrunner/src/Exception/EmitterException.php:20 Stack trace: #0 example.com/vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitterTrait.php(42): Laminas\HttpHandlerRunner\Exception\EmitterException::forOutputSent() #1 example.com/vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitter.php(21): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->assertNoPreviousOutput() #2example.com/vendor/laminas/laminas-httphandlerrunner/src/RequestHandlerRunner.php(75): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->emit() #3 example.com/vendor/flarum/core/src/Http/Server.php(45): Laminas\HttpHandlerRunner\RequestHandlerRunner->run() #4 example.com/public/index.php(26): Flarum\Http\Server->listen() #5 {main} thrown in example.com/vendor/laminas/laminas-httphandlerrunner/src/Exception/EmitterException.php on line 20`

luceos

/api/discussions returns 500 error unknow, I've tried to set permission 755 to all but that doesn't fix the problem. I've reinstalled flarum and decided not to use this plugin, as there are around 130 plugins I've installed and it's a headache to set them up again. I will try to produce the same error on a clean install of flarum later if I could.

Mikenthuzi soft means composer update <extension> hard means composer require <extension>. The difference lies in update trying to update based on the current constraint, whereas hard means it will install the latest compatible version anew. We usually recommend using a wildcard constraint for your extensions * anyway, so a hard update will be as safe as using soft updates on the majority (if not all) extensions. A hard update however, will guarantee you will have the latest version, with the soft update it depends on the constraint.