# Blade @php now REQUIRES @endphp, when it didn't before? Is this a bug?

**URL:** https://discourse.roots.io/t/blade-php-now-requires-endphp-when-it-didnt-before-is-this-a-bug/13060
**Category:** sage
**Tags:** blade
**Created:** 2018-07-27T16:47:34Z
**Posts:** 3

## Post 1 by @Matt_Tanner1 — 2018-07-27T16:47:34Z

In previous themes I was able to write php on a single line like so:

`@php(do_the_thing())`

But now if I do that, it breaks the page and gives php errors. I have to do it like this:

`@php do_the_thing(); @endphp`

I’ve done a lot of searching with a couple results, but no real answer… Was this single line feature removed? Is it a bug? Doing it the second way feels so klunky when it’s just a single line of php… I am typing more than if I were to just use regular php.

---

## Post 2 by @mmirus — 2018-07-27T16:52:59Z

This was changed in Laravel 5.5, which Sage updated to. It’s a little chunkier, but you’ll need to include both the opening and closing expressions now.

---

## Post 3 by @alwaysblank — 2018-07-27T16:54:11Z

See:

> <https://github.com/roots/sage/issues/2012>

> <https://github.com/roots/sage/pull/2060>

“I am typing more than if I were to just use regular php.” Generally the intent of Blade is that you are not writing PHP in it: Any logic should be handled at the controller level (i.e. with soberwp/controller or Sage’s filters).
