Progress Report: February 2025

Wow, another month - February truly is a short one, isn't it?! This month we've still focused on the next version of Backpack... but we...

Cristian Tabacitu
Cristian Tabacitu
Share:

Wow, another month - February truly is a short one, isn't it?! This month we've still focused on the next version of Backpack... but we've also spent quite a bit of time maintaining and improving the current version. Let's get into it!

Maintenance

Pedro has pushed some fixes to our packages. I keep saying this every month, but it's perfectly true - our software is more stable than ever. We've had 13 bug fixed in CRUD and a few other fixes to our other free packages.

Support

Jorge and Karan have been monitoring the discussions and helping our community figure stuff out, along with our AI. We're looking for feedback on our support. Had a recent experience with our support - good or bad? Let us know in the comments below!

Articles

Karan has written 3 new articles on our blog this month:

If you haven't already, subscribe to our blog article digest to get these articles as soon as they're out. We're active on Twitter too - follow us for a daily dose of Laravel and PHP tips & tricks.

Backpack v6 now supports Laravel 12

Pedro has been on a roll, adding support for Laravel v12 to all our packages (and quite a few of our dependencies). We can proudly say we've added L12 support as soon as it was out this year.

If you're starting a new project TODAY, we heavily recommend you start with Laravel 12 and Backpack v6.

Should you upgrade your existing projects to L12? Yes, of course. But personally, I'm going to wait a few weeks - it's always been a good decision, to avoid the frustration of the first few bugs, and discovering there's that one dependency in my chain that doesn't support L12 yet. But to be clear... I heavily heavily recommend you upgrade to Laravel 12 soon - in fact, you should save time in March to do just that. That's what I'm doing.

Backpack v7 is coming soon. With price bumps.

As mentioned in our previous monthly updates, we have started working on Backpack v7 a while back, and are happy with the progress. Now that Laravel 12 is out, the new version will become our focus - so expect great things to be launched soon. We're still in v7-alpha at the moment, but we should be in beta by the end of March, and launch soon after.

For full transparency, we want to also announce a few pricing changes that will happen along with the v7 launch. We're always trying to keep our software as affordable as possible, to get to as many developers as possible. But when the economy changes... we need to adapt. But don't worry - the price bumps aren't huge, and even with the new pricing, Backpack is incredibly affordable. The amount of value we deliver is counted in 100s, 1000s and 10.000s of hours of development saved, so an extra +20 EUR or +100 EUR shouldn't affect your project profitability much.

We have just updated our pricing page to show the upcoming prices, so there's no surprises. To be clear, here are the changes:

  • Single-Project PRO price will increase by 20 EUR;
  • our Everything Bundle price will increase by 100 EUR;
  • we have stopped selling licenses for Backpack v4;

We plan to keep all other prices the same (for individual add-ons and services).

Considering the fact that a v6 purchase provides access to v7 as well, this is an excellent time to buy Backpack v6 & v7 in one go, at a discount. If you've been waiting for a sign... this is that sign - buy now! You can even buy multiple years of updates at this great price - just increase the number of years in the shopping cart.

In terms of features for v7, we are working on some cool things... but we want to hear what you want! Please comment on this article, telling us what's ONE thing you wish Backpack v7 brings.

Thanks for using Backpack. We love doing this for you.

Want to receive more articles like this?

Subscribe to our "Article Digest". We'll send you a list of the new articles, every week, month or quarter - your choice.

Reactions & Comments

What do you think about this?

I want to be able to use Laravel Backpack fields in CRUD forms outside of Backpack. There are so many niceties around repeaters, ajax loading of models, etc that I have to re-implement on my front end even though the forms go to the same model.
Noted! Thanks for the feedback, Steve!
I want to be able to use tables and fields wherever I want. I hope that a fundamental change in the layout of crud pages will be made. The page can be made multi-column , sections , tabs and ... . The show crud operation can be designed properly and not a simple table. Instead of using repeated fields in forms, tables same list operation can be used.

Latest Articles

Wondering what our community has been up to?