mudasir
mudasir

I think we should create a wrapper(plugin) which will compile blade syntax to twig. This will help blade developers to write blade syntax and plugin will take care of everything.

andrewfenn23143
andrewfenn23143

Pretty upset and frustrated about this. The main page says it's a "platform based on the Laravel PHP Framework". Yet here I am, hours and hours spent, only to find out that you don't even support the default template engine in Laravel. So you've basically tricked me into wasting a whole bunch of time and effort on this assuming I could paste over all my blade template code.

You should change your main page and state what you're not compatible with in Laravel upfront so you don't waste others time like you did mine.

mike.reacher9531204
Briddle
Briddle

andrewfenn23143 said:

Pretty upset and frustrated about this. The main page says it's a "platform based on the Laravel PHP Framework". Yet here I am, hours and hours spent, only to find out that you don't even support the default template engine in Laravel. So you've basically tricked me into wasting a whole bunch of time and effort on this assuming I could paste over all my blade template code.

You should change your main page and state what you're not compatible with in Laravel upfront so you don't waste others time like you did mine.

Hmmmm.... Kerosine is based on oil. So is Nylon. Yet, planes do not fly on nylon T-shirts. Nobody was tricked here, this is no conspiracy. The fact that you did not do your homework and wasted your time can hardly be blamed on anyone but yourself. Like they say, "Assuming is the mother of all f***ups"

Ompmega
Ompmega

Laravel uses Symfony behind the scenes, and it comes with the Twig templating engine, so it makes sense that October uses Twig for templating. Also note that Blade requires file suffix .blade.php and that is a security issue because of .php file extension. October uses .htm and runs the markup through Twig, along with Yaml syntax that is placed on top of CMS pages. Twig is much safer for backend file editing, while Blade is NOT. Blade was not meant to be edited on an interface.

vedmant51911
vedmant51911

Yeah, I'm also frustrated about not supporting blade as well. Blade templates is one of the reasons I like Laravel.

It is important that a single templating language is used on the front-end, otherwise Themes and Plugins would not be compatible with each other.

This doesn't make sense to me, why to force plugins to use any specific front end approach at all. It's Vue.js / React era right now, jQuery and Twig JS are outdated things.

Briddle
Briddle

vedmant51911 said:.

This doesn't make sense to me, why to force plugins to use any specific front end approach at all. It's Vue.js / React era right now, jQuery and Twig JS are outdated things.

You are confusing a templating language like Twig or Blade with a frontend framework like Vue or React. These are two completely different things.

There are valid reasons to prefer Twig as a templating language and there are valid reasons to prefer Blade.

Views of plugins and themes should use the same templating engine as they are used on the same page. October opted for Twig. That is a perfectly valid choice and one that cannot be changed now. Besides, changing it would not offer any benefit other than personal preference.

Twig is an independent component, meaning it can be used in any framework or free-standing PHP application (even including WordPress). Blade is only used within Laravel. As a result more front-end developers will be familiar with Twig than with Blade.

If you are migrating some Laravel software to October you should expect to make changes to your code to make the best use of October anyway. That car X and car Y are both built on the same undercarriage does not mean you can switch any part of car X for any part of car Y.

Last updated

21-27 of 27