Replies: 9 comments 2 replies
-
Does this issue persist in newer versions of Laravel? There wouldn't be any patches made to 9.x as it's 3 releases behind the current version. |
Beta Was this translation helpful? Give feedback.
-
I'll test it in new fresh laravel app and revert to u with the details ! |
Beta Was this translation helpful? Give feedback.
-
@atefBB you can confirm if it is a parse issue by checking the "cached/parsed" view after you run artisan view:cache |
Beta Was this translation helpful? Give feedback.
-
@macropay-solutions |
Beta Was this translation helpful? Give feedback.
-
storage/framework/views/e9611916152482e3ccf40e803ae4e3a63562cb54.php |
Beta Was this translation helpful? Give feedback.
-
it show the same output from the blade file, see attch. picture. (this is the cached version of the view) ![]() laravel blade traits it as plain HTML text ! |
Beta Was this translation helpful? Give feedback.
-
Does it still fail if you change it to:
|
Beta Was this translation helpful? Give feedback.
-
if there's no syntax error (like yr pseudo-code); it doesn't fail ! |
Beta Was this translation helpful? Give feedback.
-
@atefBB This could be considered a normal thing. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Laravel Version
9.52.20
PHP Version
8.3.12
Database Driver & Version
mariadb on docker
Description
I and my team struggle to debug a bug in blade view that was caused by that if
@if/elseif
statement has a syntax error the blade just display it as a plain text in html, for example, this code:will display something like the attached pict in the HTML output, which is a weird thing! It suppose to throw a syntax error.
Steps To Reproduce
copy/paste the pseudo code in any blade view file in fresh new laravel 9.x app and notice the result in the desired route.
Beta Was this translation helpful? Give feedback.
All reactions