Laravel-debugbar: [Laravel 5.6][Docker] Debugbar not visible

Created on 28 Mar 2018  路  10Comments  路  Source: barryvdh/laravel-debugbar

Hello. I can't setup debugbar as visible in my Laravel 5.6 project, hosted on Docker container.
config/app.php
'debug' => env('APP_DEBUG', false),
Barryvdh\Debugbar\ServiceProvider::class,
'Debugbar' => Barryvdh\Debugbar\Facade::class,

.env
APP_ENV=local APP_DEBUG=true

laravel.log
local.ERROR: Debugbar exception: Undefined index: guards

Bar is not injected in blade body. I did php artisan route:clear few times.

stale

Most helpful comment

Workaround

config/debugbar.php
Collectors [
'auth => false'
]

But I still don't know why it crashes with auth enabled.

All 10 comments

Workaround

config/debugbar.php
Collectors [
'auth => false'
]

But I still don't know why it crashes with auth enabled.

Before your fix was the debugbar showing on your login screen but then disappeared once you logged in?

error + 1

Before your fix was the debugbar showing on your login screen but then disappeared once you logged in?

Nah, it was not visible at all.

it was not visible at all

  1. try to do a vendor:publish and set in your .env DEBUGBAR_ENABLED=true

  2. clear you cache even with the debugbar cache

  3. and no matter if you have the auto discover active, register at service provider and alliases the debugbar

i had the same issue and i did those 3 thing and now it's working (remember to give the right permissions at storage/ and bootstrap/storage)

let me know if help you.

Thank you, but still error

error+1
with message:
Debugbar exception: Method Illuminate\Database\Query\Builder::getLoginAttribute does not exist.

the Workaround solve it:
config/debugbar.php
Collectors [
'auth => false'
]

@zmarwa That worked for me.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If this issue is still present on the latest version of this library on supported Laravel versions, please let us know by replying to this issue so we can investigate further.
Thank you for your contribution! Apologies for any delayed response on our side.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

lozadaOmr picture lozadaOmr  路  6Comments

truongthaison picture truongthaison  路  4Comments

hookover picture hookover  路  4Comments

beneverard picture beneverard  路  6Comments

damienfern picture damienfern  路  4Comments