laravel-5.3

I've just caught a crash reported on sentry, I am trying to debug and see the root cause for the problem. Luckily, in the cookies panel, I can see the laravel_session value that was used while crash happened. The question, is, how can decrypt the cookie? You can decrypt the cookie with the following code: $cookie = 'eyJpdiI6ImFUQ0FvMWFSVlNvTmhlQjdLWGw1Z1E9PSIsInZhbHVlIjoicFh6Q09iTDl0K0huWU1Nc1NYVmxSY2hPRGU5Vk85dDJyYUpRbUVjRWg5R0JxYkVobkF3YkZVcVQrakFFUmxaVnZrTjFST3F3RTZ4akpDZEpvUFJiQXc9PSIsIm1hYyI6IjlhYmJhMTY3MWMxYWI3YjJmNmFjMmNkZWE0MWZmMmVhNTNiMjI5ZWY3NzUwNzQ0ZjAzMGQ1ZGU0YzVhNjJmZGYifQ==';

I would like to disable error reporting entirely on production, because we have some very old code we still need to fix but for now does work (yes I don't like it either). We cannot fix everything in a few days, so we need to just supress the warnings and exceptions like we always did. The real problem is that it already throws an exception on a simple lazy bug like (because var is not defined) if(!$var) { // do whatever } tried APP_DEBUG=false APP_LOG_LEVEL=emergency display_errors(false); set_error_handler(null); set_exception_handler(null); But it still shows an ErrorException Undefined

We can override this property to redirect users after login in LoginController: protected $redirectTo = '/home'; And here is the statement from documentation: If the redirect path needs custom generation logic you may define a redirectTo method instead of a redirectTo property: protected function redirectTo() { // } But it always redirects to '/home'; whatever the condition is. protected function redirectTo() { if (Auth::user()->role==0) { return '/volunteer'; } else { return '/donor'; } } If a method exists it'll use it, otherwise the property will be used. But it looks like property is being

I do everything by-the-book: Installed fresh Laravel 5.3.9 app (all my non-fresh apps produce the same error) run php artisan make:auth create migrations for a new table `php artisan make:migration create_quotations_table --create=quotations Schema::create('quotations', function (Blueprint $table) { $table->increments('id'); $table->string('text'); // my problem persists even with the below two columns commented out $table->integer('creator_id')->unsigned()->index('creator_id'); $table->integer('updater_id')->unsigned()->index('updater_id'); $table->softDeletes(); $table->timestamps(); });

I am a little confused about whether to use Laravel's Notification or Mailable class. From what I understand, Mailables are used to send only emails whereas Notifications can be used to send emails and sms. In my application, I dont have plans to send sms notifications for now, so I am confused if I should just use the Mailable class in this case. My questions are: If I am only going to be sending emails notifications, is it better for me to use Mailables instead of Notifications? If each emails have different html layout, then would Mailable be the better option? Even if all emails are

After hearing a lot about laravel passport, i thought of implementing it into my new project where my requirement is to create an API that'll be used in a mobile app. So my mobile app is a client , which will further have its users. I followed the steps mentioned by Taylor and also read about it here . In a nutshell I followed these steps: Installed laravel/passport . Created a website user. Generated passport keys php artisan passport:install Generated client_id and client_secret using php artisan passport:client Added redirection and callback routes in web.php Authorized the user and got the