We have this habit of sending an email every month to our users, detailing what's happened in Backpack in the past month. It keep us accountable. We've just published the Newsletter for July 2018. Check it out to see the many many improvements we've done to CRUD this past month.
Read MoreIf you’ve been dying to go to Laracon US 2018 and don’t have a ticket yet, well... it has been sold out for a while now. But we have good news - we have a ticket, can’t come, and will be giving it away, for free. So if you can be in Chicago between 25-25 July 2018 and want to join the fun & learning, you’re in luck. This is probably the last chance to get a seat at Laracon US 2018. We don’t li...
Read MoreStarting today, we're using a bunch of Github Probots, to help with issue & PR management. Here's a list of all the the features we now have, from our friendly backpack robot (I called him Justin Case... get it? just. in. case... pff, never mind). auto-reply to a user’s first issue, to double-check it's a bug and not a support request; auto-reply to a user’s first PR, to let him know it might...
Read MoreIf you haven't had time to go through all Backpack features yet, we've just launched something you might like: a free 5-day email course, which will take you through everything Backpack. In just 5 minutes a day, for the next 5 days, you'll get to know everything you need to know to build admin panels faster and better. I heavily recommend subscribing for the Getting Started emails to everybody who...
Read MoreAfter a lot of work, Backpack\CRUD has finally reached the 3.3 milestone. There have been A LOT of changes, but we've managed to keep it as backwards-compatible as possible. We won't mention the countless bug fixes here, just the new stuff you should know you can now do with Backpack. Requirements PHP 7.0+ Laravel 5.5+ New Features - Backpack/Base 0.8.1 Logged in users can change their personal...
Read MoreSometimes you'll have one resource that depends on another one. For example, you might have: a Post model; a User model; The admins could see all posts, of course. But if you might want to see only one user's posts. Sometimes, you don't want to be using a filter. You just want to go from a User to that User's posts. In this case, you can create a nested resource. Basically you'd be creating a th...
Read More
