Crud: [4.0][Bug] "The command "elfinder:publish" does not exist"

Created on 8 Mar 2020  Â·  14Comments  Â·  Source: Laravel-Backpack/CRUD

Bug report

What I did

php artisan backpack:install --elfinder yes

What I expected to happen

Backpack to be installed.

What happened

"The command "elfinder:publish" does not exist."
image

What I've already tried to fix it

Re-run the command fixed the issue.

Backpack, Laravel, PHP, DB version

Windows, Wamp, Backpack 4.0, Laravel 6.0, PHP 7.4

Bug urgent

Most helpful comment

Thank you for feedback. I am thrilled it worked.

On Mon, Mar 9, 2020 at 7:42 PM Cristian Tabacitu notifications@github.com
wrote:

Done! I've just merged Pedro's PR #2528
https://github.com/Laravel-Backpack/CRUD/pull/2528 which should fix this
issue
. Thanks again for reporting this @mamprogr
https://github.com/mamprogr, and for pitching with screenshots and
solutions @nickyskills https://github.com/nickyskills & @danielbriffa
https://github.com/danielbriffa . They really did help a lot.

Anybody getting "The command "elfinder:publish" does not exist" when
installing Backpack 4.0.50 or lower, please do a composer update to get
4.0.51, then run php artisan backpack:install again - it should work just
fine.

If anybody's still getting this error on 4.0.51 or higher, please post
here and let us know. I'll leave this issue open for a few days, just in
case.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Laravel-Backpack/CRUD/issues/2517?email_source=notifications&email_token=AOXDM2OEHD4WBFU3FJ5I66TRGUMATA5CNFSM4LDYG77KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOIAYJQ#issuecomment-596642854,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOXDM2JZFD7JHVPTYLKNYLTRGUMATANCNFSM4LDYG77A
.

All 14 comments

Hello there! Thanks for opening your first issue on this repo!

Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps _a lot_ in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.

Backpack communication mediums:

  • Bug Reports, Feature Requests - Github Issues (here);
  • Quick help (_How do I do X_) - Gitter Chatroom;
  • Long questions (_I have done X and Y and it won't do Z wtf_) - Stackoverflow, using the backpack-for-laravel tag;

Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome _awesome_ community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.

Thank you!

--
Justin Case
The Backpack Robot

Thank you for raising this @mamprogr ! We need the exact version of Laravel and Backpack you are using to debug this. I know you haven't been able to get them because php artisan backpack:version was broken (thanks for that too). But a composer update should get you 4.0.49 now, that has that fixed.

Let me know the output of php artisan backpack:version after a composer update please. Cheers!

Laravel: 7.0.7 (sorry, it was wrong in my first comment)
Backpack version is 4.0.48

After composer update:

PHP VERSION:

PHP 7.4.0 (cli) (built: Nov 27 2019 10:14:18) ( ZTS Visual C++ 2017 x64 )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies

LARAVEL VERSION:

v7.0.7@5c3b3d9c77560b249305cbc42d0aa0a16f9e80f9

BACKPACK VERSION:

4.0.49@986f5e69593eab33e567787e0c28efb6747cd7b5

Hmm and php artisan backpack:install still fails, after the update to 4.0.49? I was expecting 4.0.49 to fix that too...

php artisan backpack:install still fails, check this: https://github.com/Laravel-Backpack/CRUD/issues/2416

php artisan backpack:install --elfinder yes also still fails, please check:

image

I checked with Laravel 7.0 and i encounter the same issue
That -> The command "elfinder:publish" does not exist.

Solution measure i took

  • Open elFinder Package for Laravel 5.

  • Require this package with Composer

composer require barryvdh/laravel-elfinder

  • Add the ServiceProvider to the providers array in app/config/app.php

    Barryvdh\Elfinder\ElfinderServiceProvider::class

    • You need to copy the assets to the public folder, using the following artisan command:

    php artisan elfinder:publish

  • After installing this you may now re-run

    php artisan backpack:install --elfinder yes


I wonder which Laravel package you are using

Hmmm that's so weird. I've just tried it using the same version as you: Laravel 7, PHP 7.4, Backpack 4.0.49, and it worked fine:

Screenshot 2020-03-08 at 15 33 44

I'm wondering if it's not a OS difference. I see you're running Windows, I can only try on Mac OS.

@pxpm can you please run php artisan backpack:install on 4.0.49, PHP 7, Laravel 7, and share how that goes for you?

Have the same issue, on a windows machine. Running laravel 7 & PHP 7

image

Executing the command again fixed the issue.

I can confirm that some weird error is occuring.

error

From my understanding when we call elfinder:publish in install script I think the package is not loaded yet. Because after the script fails, you run php artisan elfinder:publish and it works normal.

What you think @tabacitu

Until we get to the bottom of this, if anybody gets this error, please complete the installation manually by running:

php artisan elfinder:publish
php artisan vendor:publish --provider=Backpack\CRUD\BackpackServiceProvider --tag=elfinder
php artisan backpack:add-sidebar-content "<li class='nav-item'><a class='nav-link' href='{{ backpack_url('elfinder') }}'><i class='nav-icon fa fa-files-o'></i> {{ trans('backpack::crud.file_manager') }}</a></li>"

@pxpm - pff... no idea why this might be happening... And it's especially difficult to debug because it works for me... Maybe the elfinder:publish command gets run before the composer install barryvdh/laravel-elfinder command gets completed, and Laravel doesn't have the chance to run its autodiscovery feature? We could test for this by delaying it a little bit:

            if (isset($createUploadDirectoryCommand)) {
                $this->executeProcess($createUploadDirectoryCommand);
            }

+           sleep(10); // wait 10s before running the next command
            $this->line(' Publishing elFinder assets');
            $this->executeArtisanProcess('elfinder:publish');

Does this work @pxpm or @mamprogr ?

Also, after a composer update you should be able to do php artisan backpack:install --debug and copy-paste the output here - it could provide some valuable info to debug this...

On it!

Done! I've just merged Pedro's PR #2528 which should fix this issue. Thanks again for reporting this @mamprogr, and for pitching with screenshots and solutions @nickyskills & @danielbriffa . They really did help a lot.

Anybody getting "_The command "elfinder:publish" does not exist_" when installing Backpack 4.0.50 or lower, please do a composer update to get 4.0.51, then run php artisan backpack:install again - it should work just fine.

If anybody's still getting this error on 4.0.51 or higher, please post here and let us know. I'll leave this issue open for a few days, just in case.

Thank you for feedback. I am thrilled it worked.

On Mon, Mar 9, 2020 at 7:42 PM Cristian Tabacitu notifications@github.com
wrote:

Done! I've just merged Pedro's PR #2528
https://github.com/Laravel-Backpack/CRUD/pull/2528 which should fix this
issue
. Thanks again for reporting this @mamprogr
https://github.com/mamprogr, and for pitching with screenshots and
solutions @nickyskills https://github.com/nickyskills & @danielbriffa
https://github.com/danielbriffa . They really did help a lot.

Anybody getting "The command "elfinder:publish" does not exist" when
installing Backpack 4.0.50 or lower, please do a composer update to get
4.0.51, then run php artisan backpack:install again - it should work just
fine.

If anybody's still getting this error on 4.0.51 or higher, please post
here and let us know. I'll leave this issue open for a few days, just in
case.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Laravel-Backpack/CRUD/issues/2517?email_source=notifications&email_token=AOXDM2OEHD4WBFU3FJ5I66TRGUMATA5CNFSM4LDYG77KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOIAYJQ#issuecomment-596642854,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOXDM2JZFD7JHVPTYLKNYLTRGUMATANCNFSM4LDYG77A
.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

abewartech picture abewartech  Â·  3Comments

packytagliaferro picture packytagliaferro  Â·  3Comments

M0H3N picture M0H3N  Â·  3Comments

gotrecillo picture gotrecillo  Â·  3Comments

sokvebolkol picture sokvebolkol  Â·  3Comments