Gonzako wrote a reply+100 XP
10h ago
Yep, php artisan optimize:clear did the trick. Many thanks!
Gonzako liked a comment+100 XP
10h ago
First of all, try php artisan optimize:clear
Gonzako wrote a reply+100 XP
11h ago
Looking at the stacktraces \Illuminate\Database\Connection.php seems to be working as intended. It's just something breaking up in the render pipeline. This doesnt throw any error, it's just returning what I believe is the make-up of the components of a stacktrace.
Debugging there's gonna be a bitch.
Gonzako wrote a reply+100 XP
13h ago
Logs are being correctly written to in the 'logs/laravel.log' file. The error seems to be when looking to render the stacktrace.
Gonzako started a new conversation+100 XP
15h ago
Hi! I've been debugging my lastest application and after a 'composer update' and after an error happens the application simply returns
laravel-exceptions-renderer::components.navigation laravel-exceptions-renderer::components.card laravel-exceptions-renderer::components.trace-and-editor laravel-exceptions-renderer::components.context
instead of actually rendering said pages. How'd I go about fixing these? Should I downgrade my laravel version?