r/PHP • • 6h ago

AI models hate Python and love PHP: we asked 12 of them 1,200 times

Thumbnail blog.jetbrains.com
23 Upvotes

r/PHP • • 10h ago

Automattic now owns the .php TLD

0 Upvotes

Matt just announced it on his blog: https://ma.tt/2026/11/new-tlds/

Considering that WordPress is the biggest ambassador for PHP out there and Automattic is already one of the major sponsors of The PHP Foundation with representation on its board having them manage ".php" feels like a very natural next step for the language's branding and governance.

Do you think this will finally unite the PHP and WordPress ecosystems?
Are you planning to register any ".php" domains once they open up?
Will this be good for the PHP community as a whole?


r/PHP • • 5h ago

PHP on Your Mac — Without Installing PHP

Thumbnail kinetis.dev
0 Upvotes

r/PHP • • 3h ago

I built an open-source PHP plugin to diagnose GLPI environments — now compatible with GLPI 10, 11 and 12

2 Upvotes

Hi everyone!

I'd like to share a PHP project I've been working on: GLPI Health Check, an open-source plugin designed to help system administrators identify potential issues in their GLPI environments.

The idea came from a practical need: having a way to run preventive checks and get a clearer picture of an installation's health without manually inspecting every component.

The plugin includes checks related to:

  • Security and configuration
  • Database health
  • Cron tasks and automated jobs
  • Email configuration
  • Installed plugins
  • Diagnostic history and result comparison
  • Reports in PDF, JSON and CSV

One of the challenges was maintaining compatibility across different GLPI generations. The plugin has now been tested and validated with GLPI 10, 11 and 12.

This project has also been a great opportunity to work with PHP in a real-world application, deal with platform compatibility, and think about maintainability and practical tooling.

The project is open source, and I'd appreciate feedback from other PHP developers, especially regarding code quality, architecture, and possible improvements.

GitHub: https://github.com/JoaoPauloSCosta/glpi-health-check

Thanks for taking a look!


r/PHP • • 7h ago

Two new nginx exploits (CVE-2026-123007 and CVE-2026-123633)

Thumbnail prostack.uk
44 Upvotes

Here's our writeup of the Nginx vulnerabilities. Hope it's useful- if your host runs nginx, ask them to disable HTTP/2 until patches are out.


r/PHP • • 15h ago

Laravel question [AI-use of my developer]

0 Upvotes

Non-dev here, so go easy on me 😅

I run a small agency. We build custom tools on Laravel + Angular. Our lead dev is the one who knows the code inside out.

My wish: every bug report and every feature request goes straight to Claude Code. Claude picks it up, builds it and opens a PR. Our dev reviews it and merges it.

His answer: for bugs, yes. For features, no.

His reasoning: with a bug all the constraints are known. You know what's broken, the existing code shows how it should work, and you know when it's fixed. With a feature the AI has to make the decisions itself: database design, where the logic lives, edge cases. In his experience that's where it keeps going wrong. Wrong tables, ignored architecture, every time a slightly different approach.

What I've read so far:

1) Laravel Boost gives the agent the database schema, the routes and the docs, so it doesn't have to guess.

2) A CLAUDE.md / guidelines file with your own architecture rules.

3) Pest arch tests that fail when the agent breaks a rule.

4) Plan mode: the agent writes a plan first (which tables, which files, open questions), a human approves it, then it builds.

My idea: for a feature, step 1 is Claude writing the plan and the open questions instead of the code. The dev answers them in 5 minutes. Then Claude builds, and the feature is as well-defined as a bug.

Questions for people who do this in production:

1) Does this hold up on a real, larger codebase, or does it fall apart after a few weeks?

2) Where do you draw the line? What do you let the agent do on its own, and what never?

3) Is reviewing a PR afterwards a win for your senior devs, or does it cost them as much time as writing it themselves?

4) What does your setup look like? Boost, custom guidelines, arch tests, CI checks?

Not trying to replace anyone. Our dev stays the one who decides what ships.

I'd like to know if what I want is realistic, or if he's right and I should stop pushing lol.


r/PHP • • 15h ago

Almost 8 months since I decided started my own LSP project

12 Upvotes

I didn't like exactly how any LSP behaves on VSCode and Zed (which is the IDE I've been trying for years and is my preferred one for now), tried a lot of them from paid ones to freemium to open source

Therefore I started 8 months ago with a project that I've been thinking years of making on a language I'm still learning today and the help of AI tools like Claude Code (which made this possible)

My scope with this is to help me within my own agency company do the few edits on WordPress websites and mostly Symfony/Laravel work (I'm way more experienced into Laravel but had a few Symfony work, mostly within open source not the framework itself). The idea is to this is to simplify all the harder parts I found with all different IDEs and LSPs within the massive PHP ecosystem that we've today (and hopefully maintaining some of what I call "legacy" stuff like WordPress, etc)

The Zed extension still waits the IDE team to accept my PR to their extensions repo (seems to be there for months anyway...) but you guys can build it from the source repository (sorry). The VSCode one has been published since this LSP started tho.

Anyway, a brief on priorities and features that are already implemented:

  • QoL (Quality of Life): Symbol scope order on all autocompletion for variables, classes, namespaces (including autoloaded with PSR-4)... Refactor tools like moving files to different folders does rewrite the namespace, composer.json file hover cards on dependencies, etc
  • Blade support as well as .phtml and PHP within HTML code on .php files (WordPress templates)
  • Laravel "magic" support (models, config, localisation)
  • Container support (dependency injection)
  • Core language support including some PHP extensions (from PHP 7.4 to 8.5)
  • Coverage support (VSCode mostly, Zed doesn't provide support within the IDE as VSCode so it does show coverage when within hover on symbols)
  • Speed and memory overhead while maintaining a feature-rich LSP
  • Portable: Web assembly so this LSP can be run within vscode.dev (on the web, as a worker, sadly with limitations...)
  • Generics and array shapes support (tailored from PHPStan)
  • Built-in diagnostics complemented with PHPStan ones (if installed as composer dependency on the project)

btw this post isn't AI generated, I just wanted to publish this here to hear about user feedback which to me seems more valuable than just adding features because of yes, any help is very welcome

Repo: https://github.com/Tusk-PHP/lsp


r/PHP • • 7h ago

News PHP security release on the 19th November between 14:00 and 14:30 UTC

190 Upvotes

I can't see this reported on the PHP website, but the Laravel team have just sent out this email:

You may have seen an announcement from the PHP Foundation disclosing a planned security release coming on Thursday, 19 November, between 14:00 and 14:30 UTC.

We are fortunate to have had a heads-up, and so our team is already on it. We're working on a plan to keep all your applications safe.

For now, there's no action needed on your side. The fixed versions will only be available once PHP releases them, and as soon as they're out, we'll check the details against our products and let you know what it means for you, including whether we'll take care of it on our side or if there's something you'll need to update yourself.

We'll be in touch closer to the release time with our planned approach and any steps you need to take (if any) to ensure everything is secure. You'll also be able to find the latest updates on our status page as and when updates occur.

Presumably releasing at the same time as PHP 8.6.

EDIT: Here's the official announcement. Emphasis mine.

The PHP security team announces upcoming security releases scheduled for Thursday, 19 November 2026, between 14:00 and 14:30 UTC.

These releases are part of PHP’s regular four-week release cycle and will address security vulnerabilities affecting all supported PHP versions. The highest severity is CRITICAL.

The issues rated CRITICAL require either non-default configuration or uncommon setups.

Users are strongly encouraged to prepare to upgrade promptly once the releases become available. Technical details and fixed version numbers will be published alongside the releases.

Thank you for helping us keep PHP secure.