Jump to content
Wanze

Module: TemplateEngineFactory

Recommended Posts

TemplateEngineFactory

The main idea of this module is to support the developer separating logic from markup.

This is achieved by turning ProcessWire templates into controllers which interact over a new API variable to template engines like Smarty or Twig. The TemplateEngineFactory ships with a default engine "ProcessWire" that uses the internal TemplateFile class to render the templates (some of you may already be familiar with this concept). However, the module is constructed in a way that any template engine can be used, implemented as separate modules. :)

Please check out the readme on GitHub for more details how it works: https://github.com/wanze/TemplateEngineFactory

... or in the modules directory: http://modules.processwire.com/modules/template-engine-factory/

post-582-0-15633700-1404419674_thumb.png

How does it work?

A controller (aka ProcessWire template) can have an associated template file which contains the markup to render. The folder where those templates are stored is configurable for each installed engine. If the Factory finds a template file with the same name as the controller, an instance to access the template is provided with a new API variable (called "view" by default). Over this API variable, you can set the dynamic variables that should be rendered. Hopefully the following example makes things clearer:

// In controller file: /site/templates/home.php

if ($input->post->form) {
  // Do some processing, send mail, save data...
  $session->redirect('./');
}
// Pass variable to the template
$view->set('foo', 'bar');
$view->set('show_nav', true);
$view->set('nav_pages', $pages->get('/')->children());

As you can see, there is no markup echoed out. The corresponding template file is responsible for this task:

// In template file: /site/templates/view/home.php

<h1><?= $page->title ?></h1>
<p>Foo: <?= $foo ?></p>

<?php if ($show_nav): ?>
  <ul>
  <?php foreach ($nav_pages as $p): ?>
    <li><a href="<?= $p->url ?>"><?= $p->title ?></a></li>
  <?php endforeach; ?>
  </ul>
<?php endif; ?>

In the example above, "ProcessWire" is used as engine. If Smarty is the active template engine, the corresponding template file could look like this:

// In template file: /site/templates/smarty/home.tpl

<h1>{$page->title}</h1>
<p>Foo: {$foo}</p>

{if $show_nav}
  <ul>
  {foreach $nav_pages as $p}
    <li><a href="{$p->url}">{$p->title}</a></li>
  {/foreach}
  </ul>
{/if}

Note that the API variable acts as a gateway which connects you to the activated template engine. We can switch the engine behind without changing the controller logic! (I know that this is probably not a very common need, but it's a cool thing anyway :P)

For further information, please check out the readmes on GitHub. Please ask questions if anything makes no sense - sometimes it's hard to get my explanations ;)

Cheers

  • Like 19

Share this post


Link to post
Share on other sites

Oh, this is perfect timing! Taking this for a test drive as soon as possible. Lately, I was aiming at the exact same thing. But this looks perfectly done with the possibility to plug in your favorite template engine! Thanks, Wanze!

  • Like 1

Share this post


Link to post
Share on other sites

Used templateFile class before to build a site. You module should make it even easier... :)

Is it planned to add a template cache (to cache the "views") in the future? 

Don't know how much time caching would be save at a small / medium site...

I'll try your module soon to build a pocketGrid base layout also with sub templates  :)

Share this post


Link to post
Share on other sites

Hi Wanze,

after a short test...

1) My setup seems not supported

// init html basic template / layout
$tpl = new TemplateFile();
$tpl->filename = $config->paths->templates.'views/html.tpl.php';

// here handle page controller / view stuff
[...]
$pagePart = $pageTpl->render();

$tpl->set('subtpl', $pagePart);

echo $tpl->render();

Because you render and output $pagePart module controlled/ inside I can't use it as sub template :(

Could you make this use possible with TemplateEngineFactory module?

2) Get a 500 error if use chunks / sub templates (for example my html layout view...)

$factory = $modules->get('TemplateEngineFactory');

$chunk = $factory->load('views/html.php');
$chunk->set('test', 'TEST');
echo $chunk->render();
 

At the moment html.php is simple:

<h1><?php echo $page->title; ?></h1>
<p><?php echo $test; ?></p>

Any idea?

Maybe you can make my setup working with your module?

Share this post


Link to post
Share on other sites

Hi pwFoo,

Thanks for your interest :)

Now you're mixing things bit up that's why it does not work. I assume that you've chosen "ProcessWire" as TemplateEngine?

Then the TemplateFile class is also used to render your templates.

1) My setup seems not supported
Because you render and output $pagePart module controlled/ inside I can't use it as sub template  :(
Could you make this use possible with TemplateEngineFactory module?

 

If you are in your /templates/basic_page.php controller, then the factory has loaded for you already the corresponding template file ine /templates/views/basic_page.php.

Your code loading the html.tpl.php file and echo out it's markup will not have any effect, because the factory will use the /templates/views/basic_page.php file for the output. You'd want to pass the variables to that template file with $view->set();

 

2) Get a 500 error if use chunks / sub templates (for example my html layout view...)

 

In the module's setting of TemplateEngineProcesswire you define where your template files are stored.

When loading a file with the factory, it looks inside that folder. So I guess maybe it wil work so:

// Template files are in /site/templates/views/

$chunk = $factory->load('html.php'); // File is in /site/templates/views/html.php
$chunk2 = $factory->load('chunks/html.php'); // File is in /site/templates/views/chunks/html.php

Now again, if you are in a controller where a corresponding template file exists, echo out will have no effect. You'd need to pass 

the markup to your template:

// In /site/templates/basic_page.php

$view->set('chunk', $chunk->render());

// In /site/templates/views/basic_page.php

<p><?= $chunk ?></p>

Hope I could make things clearer? :)

Cheers

Share this post


Link to post
Share on other sites

Hi wanze, 

I don't think I'll use the wrong path to the template / chunk, but double check ;)

Don't know my planned setup is clear so far...

I would NOT output html.php inside basic_page view..., but try to output basic_page view inside html.php view!  :P

Won't work, I found your hook into render at source code... ;)

html.php

<html>
  <head>
[...]
  </head>
  <body>
    <p><?php echo $basic_page; ?></p>
  </body>
</html>

Hope the simplified example should show what I need ;)

$basic_page is the part of current page done by your module.

Maybe I could cutting my html.php to something like html_start.php and html_end.php to get it around basic_page...

Maybe views should be not .php because it's confusing to have TWO identical files open at editor / IDE.

I'll like to use .tpl or .tpl.php to differ controller and view / template.

Share this post


Link to post
Share on other sites

I think I understand, this is a little different need. You'd have to tell the factory that your main template file is now html.php.

Could you try something like this (not tested!):

// In basic_page.php controller

$factory = $modules->get('TemplateEngineFactory');
$basic_page = $view; // Save basic_page template which is currently behind the $view API variable
$main = $factory->load('html.php'); // Load the main markup
wire()->set('view', $main); // Set the context of wire view variable to be the main template
$view = wire('view'); // Reassign to locally scoped $view variable - not sure if this is necessary, but I think so...
$view->set('basic_page', $basic_page->render()); // Pass output of basic_page to main template

If this should work, you could enable $config->prependTemplateFile an put the code in your prepended controller file, e.g. _init.php.

Maybe views should be not .php because it's confusing to have TWO identical files open at editor / IDE.

I'll like to use .tpl or .tpl.php to differ controller and view / template.

I'll add support for that so that you can define the suffix. Actually this is supported by the Smarty and Twig additions, don't know why I did not add this for the ProcessWire engine ;)

Share this post


Link to post
Share on other sites

So I'll test it soon. Thanks for help :)

Maybe a option for module configuration?

Define a global view to be used as main view?

I'll add support for that so that you can define the suffix. Actually this is supported by the Smarty and Twig additions, don't know why I did not add this for the ProcessWire engine  ;)

Great!  :biggrin:

Share this post


Link to post
Share on other sites

Maybe a option for module configuration?

Define a global view to be used as main view?

I updated the module to version 1.0.1.

All engines now have a setting Global template file where you can enter the filename of a template file that is used as "main template" behind the API variable.

This is useful if you have a main template that contains all the markup and you need to fill certain variables per controller.

Note that Smarty and Twig already support this feature with template inheritance.

Also the TemplateEngineProcesswire module now supports custom suffixes for the template files. Change this setting if you'd like to name the templates different than the controller, e.g "home.tpl.php".

Cheers

  • Like 1

Share this post


Link to post
Share on other sites

Hi Wanze,

global template works with following example.

$factory = $modules->get('TemplateEngineFactory');

$subtpl = $factory->load('basic-page'); // current page template / view basic-page.tpl
$subtpl->set('subtplvar', $page->body); 

// global template / view
$view->set('title', $page->title);
$view->set('subtpl', $subtpl->render()); // render sub template to global template variable

I think that's how it should be used?

How did it work with smarty / twig? Was it a include inside a template to load a sub template?

If I'm right template engine can't simply switched between Processwire and Smarty/Twig because template variables seems to be handled different?

PW -> load sub template & fill it like your chunk example

Twig/ Smarty -> include sub templates and fill all the template and sub template variables via api variable?

Don't know I'm right or if it's possible. But would be nice to get it filled the same way  :cool:

At the moment I'm only working with pw template class, but maybe I'll could be switch it later... So it would be a great feature have template parser independent code ;)

Share this post


Link to post
Share on other sites

I think that's how it should be used?

Yep, looks fine to me!

Another approach could be to use ProcessWire's prepend template file option. This way, you can populate the variables in your global template and overwrite them in the controllers, if needed.

Let's assume that we have a variable 'content' and 'sidebar' in our global template.

// Populate default values in prepended template file, e.g. _init.php
$view->set('content', $page->body);
$sidebar = $factory->load('chunks/sidebar');
$sidebar->set('a_variable', 'a_value');
$view->set('sidebar', $sidebar->render());

Now in the home controller, the content variable is more complex, we overwrite it:

// In home.php the content variable is pouplatet differently
$home = $factory->load('home');
$home->set('images', $pages->find('template=gallery,sort=-created,limit=3');
$view->set('content', $home->render());

How did it work with smarty / twig? Was it a include inside a template to load a sub template?

If I'm right template engine can't simply switched between Processwire and Smarty/Twig because template variables seems to be handled different?

It works the same, switching the template engine is possible as long as you use the same template filenames (the ending/suffix can be different) and identical variable names. This is possible because behind the API variable is not directly the engine like Smarty or Twig but sort of a 'gateway class' that talks to those engines. Notice that in my examples above I loaded the template files without the suffix, just the filename. Depending on the active filename, the correct template is loaded.

As an example, you could (though this is probably a very rare need) store your templates like this:

  • For the ProcessWire engine: In folder /site/templates/views/
  • For the Smarty engine: In folder /site/templates/smarty/

Now if ProcessWire is the active engine and you load the template 'home', a file in /site/templates/views/home.tpl.php gets loaded (whatever you've configured as template file suffix). If Smarty is active, the file /site/templates/smarty/home.tpl is loaded.

Don't know I'm right or if it's possible. But would be nice to get it filled the same way   :cool:

At the moment I'm only working with pw template class, but maybe I'll could be switch it later... So it would be a great feature have template parser independent code

It works as long as you have your template filenames and variable names consistent :)

However, when switching to a template engine like Smarty or Twig you should check out template inheritance. In my opinion, this is the most powerful feature and one of the main reasons to use a template engine. For smarty, I've written a little section how this could work: 

https://github.com/wanze/TemplateEngineSmarty#best-practices

Cheers

Share this post


Link to post
Share on other sites

Really awesome module, great work!

I just have one question, 

If in one controller I need to render two different templates

how can it be done?

Example home controller

and two themes, one for night other for day.

So the controller check the time and load the corresponding view.

Share this post


Link to post
Share on other sites

Really awesome module, great work!

I just have one question, 

If in one controller I need to render two different templates

how can it be done?

Example home controller

and two themes, one for night other for day.

So the controller check the time and load the corresponding view.

Thanks!

If the HTML markup is the same, maybe you could solve it with loading different CSS files. If markup is different, you'd need to dynamically set the template that is behind the API variable ($view or your custom name).

Something like this, not tested:

$theme_template = isDay() ? 'day' : 'night';
$theme = $factory->load($theme_template); // Load the correct theme
wire()->set('view', $theme); // Set the context of view variable to be the correct theme template
$view = wire('view'); // Reassign to locally scoped $view variable - not sure if this is necessary, but could be

This must happen before you pass any variables to $view. If you need this check on the whole site, you could also use ProcessWire's prependTemplateFile option and put this code in your prepended template file (controller).

Share this post


Link to post
Share on other sites

Wanze, this is a very nice module :) I am playing around with it now

Thanks :)

Today I pushed a little update (v.1.0.2) with some improvments. If you update to this version and already installed/used Smarty or Twig, make sure to update those modules as well.

What's new?

When loading a template file with the factory, you can optionally tell the module to use the given file behind the API variable:

$factory = $modules->get('TemplateEngineFactory');
$view = $factory->load('pw_rocks', true);

Setting the second parameter to true, the template file 'pw_rocks' is now used as active template behind the API variable.

In the example above, the template file is also assigned to '$view' which reflects this change also to the $view variable which is locally scoped in controllers. Whatever template is set behind the $view variable is used by the module when rendering the output of a page.

  • Like 1

Share this post


Link to post
Share on other sites

Hi Wanze,

Any direction how to configure this with $config->ajax?

<?php
//we use the page title as template
$template = $sanitizer->name($page->title);

/* render load body */
$body = $factory->load('custom-templates/' . $template. '.php');

if ($config->ajax) {

$view = $factory->load('custom-templates/_Ajax.php', true);
return;
}

/* render custom-templates */
$view->set('Body', $body->render());

I tried the code above but I dont get the desired result. I am setting the global template with my setup. Need a bit of help :) Thanks :D

Share this post


Link to post
Share on other sites

Hi peterfoeng,

What is the content of your _Ajax.php file?

Does it work if you do echo ou the template and the exit if you do not have to process any additional logic?

if ($config->ajax) {
  $view = $factory->load('custom-templates/_Ajax.php', true);
  echo $view->render();
  exit;
}

Cheers

Share this post


Link to post
Share on other sites

Hi Wanze,

I figured it out, this is a silly mistake of not supplying the correct path LOL!

<?php
//we use the page title as template
$template = $sanitizer->name($page->title);

/* render load body */
$body = $factory->load('custom-templates/' . $template. '.php');

if ($config->ajax) {
  $view = $factory->load('_Ajax.php', true);
}

/* render custom-templates */
$view->set('Body', $body->render());

So, I am rendering the body with the global template option and if there is an ajax request, the global template is overridden with ajax.php or empty template using $factory->load() :D

Silly mistakes!

  • Like 1

Share this post


Link to post
Share on other sites

hi Wanze, this system is awesome but I'm getting some issues working with the "Global template file" option, probably i didn't get the right purpose of this.

my setup is:
"templates/views/" for the path
"tpl" for the extensions
this works good as long as i use files like home.php + home.tpl
but when i set
"main" for the Global template file (or should write main.php??)
i get just blank pages.
Can you please provide an example of the correct use of this option and file structure ?
 

Share this post


Link to post
Share on other sites

Hi Sevarf2,

Sorry for my late response...!

"main" for the Global template file (or should write main.php??)

Just "main" or "main.tpl" if you've set "tpl" as the extension.

i get just blank pages.
Can you please provide an example of the correct use of this option and file structure ?

What is the content of your main.tpl? You should see this content rendered by the selected engine.

This option is useful if your controllers (aka Pw-Templates) all render the same markup. With this option, you'd define this markup in your "main.tpl" file, and home.php would render it. If you don't use the global template file, home.php would render "home.tpl".

Does it make sense?

Cheers

Share this post


Link to post
Share on other sites

This looks very nice module Wanze, thanks.

One thing i don't understand.

Why people hook into Page::render instead of TemplateFile::render, which is actual ultimate output buffer for templates.

Forked your module and trying to figure out this and that, i like it mostly, just few things i wanted to test out.

Sorry if this post is on wrong forum section, feel free to move it to proper place.

Share this post


Link to post
Share on other sites

Hi Stikki,

Thanks!

Please report any issues or new features you'd like to see here!

Why people hook into Page::render instead of TemplateFile::render, which is actual ultimate output buffer for templates.

Never thought about that, have you tried it? :)

Share this post


Link to post
Share on other sites

This option is useful if your controllers (aka Pw-Templates) all render the same markup. With this option, you'd define this markup in your "main.tpl" file, and home.php would render it. If you don't use the global template file, home.php would render "home.tpl".

Hi Wanze!

I'm having trouble understanding the file structure yet.  

What happens with PW's _main.php and _init.php?

Where the views get the project's css/js/etc.?

What am I missing? :)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...