Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

accent-interactive's avatar

Not having a way to use cascading config files is very inconvenient. Some things are just so much more conveniently set in a cascading config file, like for local

'providers' => append_config([
                                     'Way\Generators\GeneratorsServiceProvider',
                                     'Barryvdh\LaravelIdeHelper\IdeHelperServiceProvider',
                                     'Barryvdh\Debugbar\ServiceProvider',
                                 ]),

    // Local aliases
    'aliases'   => append_config([
                                     'Debugbar' => 'Barryvdh\Debugbar\Facade',
                                 ]),
jurosh's avatar

Hi guys, just want to post something what can help people migrating from 4.2 to 5. I had this error: Notice: date_default_timezone_set(): Timezone ID '' is invalid in ..... .... Fatal error: Call to undefined method Illuminate\Foundation\Bootstrap\ConfigureLogging::configureHandler()

it was not because timezone problem, but because I put old configurations from L4.2 into config folder, eg. config/_4.2_config/*.php... Laravel automatically parsed this and then shows this strange error. So simple solution for me was to remove all unnecessary stuff in config folder. Cheers.

jekinney's avatar

Or set your composer to

"laravel/framework": "5.0.7"

instead of

"laravel/framework": "5.0.*"

The update is 5.0.8

1 like
ValsiS's avatar

I have the same problem, even when i made a fresh install

5.0.7 doesn't have that problem, but 5.0.9 have it

Any suggestion ?

RomainLanz's avatar

@ValsiS No, he revert my PR right now, because its broke other component on Laravel. We need to wait.

Previous

Please or to participate in this conversation.