Laravel Nestedset: Effective tree structures for SQL databases

Version 7.1 of the aimeos/laravel-nestedset package for managing trees using nested sets is now available. It's an improved version of the popular kalnoy/nestedset package which, unfortunately, has been virtually abandoned by its owner.

Repo: [https://github.com/aimeos/laravel-nestedset](https://github.com/aimeos/laravel-nestedset)

The 7.1 release contains:

Support for Laravel 13
Implemented siblings relation
Delete descendants correctly
Fixed infinite recursion with serialization
Tests for all supported databases

To dig deeper into the package, please check:

https://laravel-nestedset.org

If you like our package, leave a star :-)

https://redd.it/1ryubp5
@r_php

Who's hiring/looking

This is a bi-monthly thread aimed to connect PHP companies and developers who are hiring or looking for a job.

Rules

No recruiters
Don't share any personal info like email addresses or phone numbers in this thread. Contact each other via DM to get in touch
If you're hiring: don't just link to an external website, take the time to describe what you're looking for in the thread.
If you're looking: feel free to share your portfolio, GitHub, … as well. Keep into account the personal information rule, so don't just share your CV and be done with it.

https://redd.it/1rxvavn
@r_php

What would you do if you had to quickly review the basics of Symfony?

I have an interview coming up, which will likely include a bunch of questions and coding in the context the Symfony framework.

I've been working with a piece of software written on top of Symfony for the past two years so I'm not starting from zero by any means. However, there are definitely subsets of Symfony that I've been exposed to more than others.

Ideally, I would want to have a good coverage of all underlying concepts that are actually relevant and being actively used in development, without having to read through the entire docs.

How would you approach a situation like this? Are there any good up-to-date study plans that cover all relevant aspects in a sufficient depth.

It's worth noting that I'm more or less fluent in php itself.

Any help is greatly appreciated.

Kind regards



https://redd.it/1rycbp5
@r_php

⚡ NativePHP for Mobile v3.1: The Biggest Performance Leap Yet
https://nativephp.com/blog/nativephp-v31-the-biggest-performance-leap-yet

https://redd.it/1ryy5jb
@r_php

Wondering if an AI agent such as Claude can help me update an older website

I'm helping a small company that has a heavily customized Opencart 2.0 site that won't run on anything beyond php 5.6.

I looked at the code thinking that maybe I could just upgrade it but it would be a monumental task given the extent of customizations.

I've always hand-coded everything I've built and never used an AI agent to help me with programming tasks. I was an old-school StackOverflow kind of person.

This is way too much for me, however.

Any thoughts on using an AI agent such as Claude (or others) to run through the code and make it compatible to run on php8+?

I appreciate any advice. Thanks in advance.

https://redd.it/1ryivrn
@r_php

Policies vs. Gates: When to Use Which
https://slicker.me/laravel/policies-vs-gates.html

https://redd.it/1rz6vmv
@r_php

Make your Domain speak the business language
https://medium.com/@dariuszgafka/make-your-domain-speak-the-business-language-cc8bd3acf4fc

https://redd.it/1rz9i3v
@r_php

Perfex CRM <=3.4.0 allows unauthenticated RCE via insecure deserialization
https://nullcathedral.com/posts/2026-03-16-perfex-crm-unauthenticated-rce-insecure-deserialization

https://redd.it/1rzfnk1
@r_php

What are your must-have composer plugins?

Just recently held the power of Composer plugins. Personally the Composer Upgrader to upgrade all libraries is a life saver, with Rector to upgrade the code and Mago for the rest.

https://redd.it/1rzizui
@r_php

I've been maintaining a small Forge app for 9 years. Here's what that's been like

I always wanted to be an indie developer. My first product was GitFTP Deploy, a tool for deploying via FTP released in 2015. It grew slowly. I got featured on CSS-Tricks which felt huge at the time, but it was a gradual thing: a sale here, a nice email there.

F-Bar was the complete opposite. While developing I posted a screen screenshot on Twitter late at night in February 2017, a trip to the bathroom, and when I came back my phone was buzzing. Taylor Otwell had retweeted it. Suddenly I had a buzz and traction even before it was released, I rushed to get the product out the door.

The early days were so much fun. Got some features on different Laravel outlets and I am greateful for this. Also, support emails started coming in and I would fix bugs the same evening, push an update, and get a thank you back within a couple of hours. I got a bit hooked on it, honestly. I learned more about building products in those first months than from any course or blog post.

I'm not naturally someone who puts himself out there. But getting something you made in front of people and having them actually care, that's hard to beat. I went to Laracon EU and people knew what F-Bar was. People came up and said they used it every day. For a solo developer from Sweden, that meant everything. People were very kind to me.

Over the years Laravel Forge evolved. Redesigns, new features, new hosting providers. The landscape around it changed too: more alternatives, serverless, new ways to deploy. Through all of it I kept adapting F-Bar.

I never made much money from it. It was a one-time purchase, and honestly most months I probably used it more than anyone. But I kept going because I use it every day and because people kept emailing me every now and then saying they relied on it.

It's a different kind of ownership than my day job. At work a bug is a ticket. With F-Bar, a nasty email hits different. When it's your product, your name on it, your decision to charge, it's personal in a way that employment never is.

I heard rumors that Forge had plans on retiring the old API, but I kept procrastinating until end of last year when I saw there was a hard date. No patching this time. I ended up rewriting large parts of it. Once I started, it just kept growing.

For the first time in nine years I moved to a subscription. That was not an easy decision. Some users were not happy. Existing users got grandfathered in, but a few still thought I was just slapping a paywall on the same app. I was so eager to ship that my communication was behind and the messaging didn't explain the why clearly enough.

I imagined this would be my living. It wasn't. But being in charge of the whole thing, the code, the design, the support, the decisions, there is nothing else like it.

Still here. Still using it every day.

https://redd.it/1rzlmrf
@r_php

I created a VSCode Extension

Hi people, just upload the first version, all is free - for now.

All the context from previous post: https://www.reddit.com/r/symfony/comments/1p8gzwg/i\_am\_creating\_a\_vscode\_symfony\_extension/

Search in vscode marketplace: `Symfonykd Extension`

https://redd.it/1rzp0wr
@r_php

Is Laravel Spark dead?

Does somebody know if support for Laravel Spark has been discontinued? It's not part of the list of packages in the Laravel docs anymore and the last update was in September 2025. So, also no Laravel 13 support.

https://redd.it/1rzsvbq
@r_php

Best way to integrate helpdesk/support ticket systems to Laravel projects

There are several options if a project needs a helpdesk:

* Build from scratch
* Use a third-party package
* Open-source
* Commercial
* Plugins

I’m keen to know how you would approach this, or how you’ve already done it. Are there any solid packages that come with a UI?

Would you use a feature-rich, modern Laravel helpdesk package if one were introduced?

https://redd.it/1s02zzd
@r_php