Laravel Auth: After-Registration Redirect to Previous (Intended) Page
In-depth Laravel tutorials covering advanced topics, real-world examples, and best practices.
If you're building a Laravel project with both Web and API sides, you need to customize error messages for each of them separately. In web-view there should be error pages, and API exceptions should return JSON with status codes. How to handle it? I will show you an example with case of Model Not Found 404.
In typical project with list and pagination, you should have a choice to select, how many entries you want to see per page - 10, 25, 50, 100 etc. That setting probably refreshes the table or the whole page, but how to save it for the next time that user logs in, or visits the page in a week?
I was listening to recent podcast by Taylor Otwell, Laravel Snippet episode 11, where he touched on the debate in Laravel community on where you should put your code logic - in Controllers, Models, or Services. Here's what he said.
Quite often I get a question from junior developers like "how to get better at Laravel", and there's so much to study potentially that I decided to gather the topics and classify them somehow. Let's begin. **Notice**: this is kind of a follow-up on my article [How to Test Junior Laravel Developer Skills](https://laraveldaily.com/post/test-junior-laravel-developer-sample-project?mtm_campaign=post-internal-advanced-laravel-topics).
Really popular Laravel Media Library package has one less-known feature - image resizing. The best part is that it's really simple to add, let me show you how.
One of the most common performance issues I've seen in Laravel is using Eloquent methods and relationships from Blade, creating unnecessary extra loops and queries. In this article, I will show different scenarios and how to handle them effectively.
This week I've launched a new online course called Datatables in Laravel, and want to invite you to enroll. Here's what you will get inside.
One of the new features in Laravel 5.8 allows you to not register your policies in AuthServiceProvider, they will be "guessed" automatically. Here's how it works.
There is one change in Laravel 5.8 that is not mentioned in the official Upgrade Guide but caused me problems - I couldn't create a foreign key migration, and spent half-hour until found out the reasons. So I want to share, maybe you will encounter the same thing.