Laravel is full of hidden gems, undocumented or less-known features, functions parameters and "hacks". While finding them in work of my team, I decided to compile them into an e-book.
By default, Laravel Eloquent models assume your table has timestamp fields - created_at and updated_at. But there's plenty of things you can...
I've been listening to Laravel Snippet podcast by Taylor Otwell, and heard some news about upcoming Laravel 7, which I think is pretty important for blog readers to know. So, changes are coming to Auth scaffolding.
Quick example of a code I had to write recently. Task is simple - upload CSV and parse it. Also save that file and the record, which user uploaded it. Let's take a look.
Quite often in e-shops you can see many level of categories and subcategories, sometimes even unlimited. This article will show you how...
I confess - during five years of working with Laravel, I've been fascinated by its "magic" and how little code is needed to actually make things work. But recently, as my projects grew in size, that "magic" started to become a problem. One of the typical example is Eloquent Accessors, so in this article I will put an argument against using them, and what to do instead.
There are situations where you need to get array of IDs for some records in collection/table. I will show you two quick ways to do it - one is pretty popular, and another is a function which I found out only today.
Default belongsToMany relationship in Laravel works really well - you can easily attach, detach or sync records. But what if you want to order pivot records by newest or oldest? This article will show you how.
Nowadays, we have a lot of Laravel tutorial about some syntax or package, but I think there's not enough written with real-life mini-projects, close to real demands of the clients. So will try to write more of these, and this is one of them: imagine a project where you need to have two-step registration process, with some optional fields in the second step. Let's build it in Laravel.
Quite often, especially in e-shop projects, you can see a page to login or register before finishing the purchase. But Laravel has these two routes as separate login and register pages. So how to merge them together and avoid conflicts?