maetmar

Just checked out the module and I really like it. Still need to wait for the next version as I need support for images.

yes, that is what I meant! I was not even aware that that weekly newsletter is not officially from Ryan, as its sent from email address "newsletter@processwire.com" ? But now checking in more details, the footer mentions its sent from Teppo Koivula. My mistake, sorry @bernhardthanks for clarifiying.

@ryan, in this weeks newsletter you advertise the new commerciale module called "RockForms". Does this mean, its a replacement for your "ProForms" module?

@cwsoft, yes got Option 2 working. Also including my custom variables. Regarding Option 1: I tried your proposals to but didn´t get it to work. LATTE is properly installed, otherwise Option 2 would also not work I guess. But anyway. I am happy with Option 2 for my purposes. Thanks

that is exactly what I try to do, find a solution to use LATTE without any of the modules that offer support for LATTE. That is what this thread is about and I didn´t post this in the RockFrontend thread ? From the existing modules that I tried, RockFrontend offers in my opinion the best LATTE support and is the easiest to use. But if I find a solution w/o a module needed, for me that would even be better. So I try to find that out now. fyi, I used an older backup from the site where I got the issues, and I tried to reproduce the error, but I can not manage to reproduce it anymore. So I take back the statement that it was RockFrontend causing the issues, it might have been also something else.

I used it for quite some time now. But recently I revisted an older project and wanted to upgrade all modules to the newest versions. When upgrading Rockfront from a very old to the newest version it broke my whole site and needed to restore it. The only thing I really used was LATTE, that made me think about a solution where I am not depending on another module. RockFrontend offers great things, but as said I personally dont need a module to take care of loading google fonts, managing font-sizes, etc.

thanks for your reply. I will try that out. And yes, I would be interested in the code you mentioned. Always good to see other approaches to learn something.

I wanted to add, that I experience the same (or similar) issue when using TemplateEngineLatte. However, with Bernards RockFrontend this works out of the box

Hi @cwsoft, thanks for this tutorial. I absolutely support what you write in the beginning, to have LATTE support without dependencies to any modules. While RockFrontend is in regards to LATTE supporting and doing everything I need, and it works perfect for that, the drawback is, that it comes with too many things, I don´t need and don´t want to have in my project. So I tried out your proposals. Option 1 ends up with this error: "Uncaught Error: Class "Latte\Engine" not found in site/classes/DefaultPage.php:61" But Option 2 works without issues. I also have a question to you that you might be able to answer. standard.php <?php namespace ProcessWire; echo $website_name; echo wire('latte')->renderTemplate('views/standard.latte'); $website_name is defined in my _init.php which is automatically called before standard.php. And within standard.php the value for $website_name is properly available end rendered when the template is called. In the 3rd line I now call the latte template, which looks like this: latte.php {$website_name} now I get the following warning "PHP Warning: Undefined variable $website_name in .../Latte/templates-views-standard.latte" What do I need to do to make $website_name also available within the latte template? thanks

In my templates I normaly call a _init.php file as prepend to initialize / set some variables, etc. However, as soon as I activate "Enalbe automatic page rendering" in the "Template Engine Factory" Module, this _init.php seems to be nor longer called and therefore my default setting values are undefined and can not be used. Any Idea how to fix this behaviour? If I disable this feature, the system still calls my "standard.php" file including the _init.php call upfront. So maybe I could just load the latte template (as I wnat to use the latte extension) from within standard.php ? But I donßt know how to call it properly. thanks for any help

will do so. but could you give me a working example of how to call and render standard.latte from within standard.php? would be great

In my templates I normaly call a _init.php file as prepend to initialize / set some variables, etc. However, as soon as I activate "Enalobe automatic page rendering" in the "Template Engine Factory" Module, this _init.php seems to be nor longer called and therefore my default setting values are undefined and can not be used. Any Idea how to fix this behaviour? If I disable this feature, the system still calls my "standard.php" file including the _init.php call upfront. So maybe I could just load the latte template from within standard.php ? But I donßt know how to call it properly. thanks for any help

thanks, it works that way! One more thing, I found to get this warning due to PHP 8.2: Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /usr/www/users/xxxxxxxxxx/site/modules/TemplateEngineLatte/src/TemplateEngineLatte.php on line 139

Does someone have a working example of using LATTE to parse through a Repeater Matrix (pro fields)? Similar like here: https://processwire.com/blog/posts/more-repeaters-repeater-matrix-and-new-field-rendering/ just using LATTE files instead of PHP

I would like to add my 50cents here as well. I basically agree to what @Stefanowitsch mentioned above. I love to use RockFrontend for the following reasons: LATTE, LATTE, LATTE then AutoRefresh and thats it for me personally. I also like to keep all my modules as much as possible to the latest version. With RockFrontend this means, I get lots of new stuff, which might or might not affects my site (I always need to test this), but which I do not really need most of the time. Maybe it would make sense to split the module into two parts. RockBackend and RockFrontend where RockFrontend needs to have RockBackend as a dependent module somehow? I personally find it strange that a module which offers neatless integration with LATTE and auto compiles LESS files also provides scritps for fluid font sizes, animations, downloading fonts to local folders, etc. I know this is just my personal preference and the way I work, and others will have a different approach here and will use many features of what the module offers. And by no means I want to criticize Bernhard for the way he develops his module.