In-depth Laravel tutorials covering advanced topics, real-world examples, and best practices.
Let's imagine a scenario where you have an old database and re-writing codebase to Laravel. Database structure may not follow Laravel standards - created_at and updated_at fields are named differently. How can you "tell it to Laravel"?
Not Laravel related, but today encountered the situation, so sharing with you. You probably know Datatables, right? It allows to quickly search and filter the table of data. But what if user then navigates away (for Edit, for example) and then wants to go back and have the same search parameters he had before? Easy.
Laravel is a back-end framework, but most web-projects still require a front-end theme. And there are no sites with "Laravel themes", all front-end themes are mostly based on WordPress CMS. But it shouldn't be a problem - we can easily transform a WP theme to Laravel Blade. We often do that for our clients, so I will show you a simple example.
Laracasts is the no.1 place to learn Laravel, no doubt. But if you don't want to pay for subscription or just like to use YouTube, there are people who can teach you there. I've searched through YouTube and picked the best ones, in my opinion.
I've recently found out about a feature in Laravel relationship which changed the way I write code. So sharing with you.
A few days ago I started a survey about the tools that Laravel people use. I've spread the word on Twitter, and asked some people via Direct Messages, so got 52 responses. Here are the answers to 5 questions I asked.
Resource controllers are great for CRUDs, but if we use them for APIs, there are two unnecessary methods - create() and edit(), cause there are no visual forms for it. So how to remove them from routes? There are two ways.
Resource controllers are amazing tool to work with CRUD functions in Laravel. But what if their default functionality isn't 100% suitable and you want to override some defaults? Let's see what you can do.
A quick tip for the case if you need to add additional GET parameters to your route URL, but don't want to specify them in Routes file. Apparently, there's a simple way.
