Jump to content

Module: Template Latte Replace


tpr
 Share

Recommended Posts

v029 is available:

  • change in adding custom macros and filters: $view->addMacro(), $view->addFilter()
  • added $view->invokeFilter($name, $args) method to run filters directly in PHP
  • updated filters to accept PageArrays instead selectors only
  • new filter: 'renderpager'
  • new filter: 'getsetting' (to use with TextformatterMultivalue module)
  • $view->latte returns the Latte object
  • lowercase filter names

See the docs for "renderpager" filter, otherwise these changes won't affect you if you're not using your own custom filters/macros. Another goodie is the ability to run a filter directly in your PHP files (ready.php or template files).

  • Like 1
Link to comment
Share on other sites

Thanks! The old method is better to forget, the module is the way to go. The latest filters and latte-only template files make templating even more enjoyable. Recently I updated an earlier site of mine and I could throw off about half of the template files and the code is also much cleaner/maintainable.

  • Like 2
Link to comment
Share on other sites

2 hours ago, tpr said:

Thanks! The old method is better to forget, the module is the way to go. The latest filters and latte-only template files make templating even more enjoyable. Recently I updated an earlier site of mine and I could throw off about half of the template files and the code is also much cleaner/maintainable.

 

On my current project I decided to keep the .php extension but on the next one I'll enjoy this new approach for sure. Many thanks, @tpr !

Link to comment
Share on other sites

I like this approach because of less number of template files. Sometimes I end up with 10+ templates and it gets duplicated because of the view files. Keep in mind that you should use ready.php (or another one) to act as a controller if you still need to separate concerns. There you can use conditionals to target the current template or even include another php files if needed - I often include files eg. in case of the search template to keep ready.php less crowded.

Link to comment
Share on other sites

Just added a new filter 'default' (v031) - this seems to be a nice shortcut for simple if-else conditions.

<div>
    {$page->product_description|default:'No description is available for this product.'}
</div>

I guess the core PW API could also use something like this:

$page->get('product_description', 'No description is available for this product.')

What do you think?

Link to comment
Share on other sites

7 minutes ago, tpr said:

I guess the core PW API could also use something like this:


$page->get('product_description', 'No description is available for this product.')

What do you think?

There is this:

<div>
    <?= $page->product_description ?: 'No description is available for this product.' ?>
</div>

 

  • Like 1
Link to comment
Share on other sites

Thanks, good suggestion, I haven't thought about this. Although for newbies it can be harder to understand.

It works in Latte too but I'll keep the 'default' filter as it's easier to use, especially when chaining filters:

{($page->title|replace:'Home','') ?: 'No content available.'}
{$page->title|replace:'Home',''|default:'No content available.'}

 

Link to comment
Share on other sites

v033 is available that contains two new filters, lazy and surround.

I like the succinctness of the surround filter, eg in case of a tag list:

{$p->tags->sort('name')->title()|surround:'li'|surround:'ul class="tags"'|noescape}
<ul class="tags">
	<li>one</li>
	<li>two</li>
	<li>three</li>
</ul>

The docs were moved to GitHub Wiki, the increasing number of filters required this.

  • Like 2
Link to comment
Share on other sites

Hi @tpr,

Have a question here (more like a Latte question rather than module question): I have my default base layout called @layout.latte which is a base template for almost all of my pages but I also want to have another layout template that does have a sidebar. How do I setup this up in such a way I only declare my base HTML file once? Using {extends} or {layout} directive seems to replace the whole template file? or am I missing something here?

Link to comment
Share on other sites

@peterfoeng - I'm not sure about Latte (tpr might be able to answer this better), but surely you can have one layout extend another? So you would have a base layout and a sidebar layout where the sidebar layout extends the base layout, which would import the content of the sidebar layout if it's provided. Blade provides a nice way of doing this by using a combination of @section() and @parent.

 

Link to comment
Share on other sites

10 minutes ago, Mike Rockett said:

@peterfoeng - I'm not sure about Latte (tpr might be able to answer this better), but surely you can have one layout extend another? So you would have a base layout and a sidebar layout where the sidebar layout extends the base layout, which would import the content of the sidebar layout if it's provided. Blade provides a nice way of doing this by using a combination of @section() and @parent.

 

My previous setup is not using this module and seems to be working ok (I am pretty sure I am just missing something here)

This is my previous setup:
I have `@base.latte` file which contains the default markup then on my `Contact Page` (where I want this page have to have a sidebar) I have the following markup:

`Contact.latte` file:

{extends '@layout.sidebar.latte'}

{block side_navigation}
  {include $config->paths->templates . 'views/components/_globals/side-navigation/contact.latte'}
{/block}

{block content}
....My content
{/block}

 

`@layout.sidebar.latte`file:

{extends '@base.latte'}

{block body}
  {var $fixed = in_array($page->template, array("Contact", "Size-Guide", "Product-Information"))}

  <main class="component component--main-content" id="content">
    <div class="component__wrapper">

      <div class="main-content">
        <div class="main-content__wrapper">
          <div class="main-content__col main-content__col--sidebar {if $fixed}main-content__col--sidebar-fixed{/if}">
            {block side_navigation}{/block}
          </div>
          <div class="main-content__col main-content__col--body">
            {include content}
          </div>
        </div>
      </div>

    </div>
  </main>
{/block}

This works with my previous setup. Hopefully @tpr can help a bit with his knowledge of this templating engine :)

Cheers

Link to comment
Share on other sites

What is the error you got? Layout inheritance is available in latte too.

btw you don't need separate layout for a sidebar, just add an empty block to the base layout and fill with markup when you need it.

Plus you don't need to pass the full path for includes, use relative paths, eg include 'components/...latte'.

Link to comment
Share on other sites

This is how I use multiple layouts in a project.

@default.latte:

...
<body>
{include content}
</body>
...

@sidebar-left.latte:

{layout '@default.latte'}

{block content}
    <div>
        <div class="main">
            {include main}
        </div>
        <div class="sidebar-left">
            {include sidebar_left}
        </div>
    </div>
{/block}

contact.latte:

{layout 'layouts/@sidebar-left.latte'}

{block sidebar_left}
    ...
{/block}

{block main}
    ...
{/block}

Maybe there's a better setup for this, please share if you find one :)

Link to comment
Share on other sites

12 hours ago, tpr said:

This is how I use multiple layouts in a project.

@default.latte:


...
<body>
{include content}
</body>
...

@sidebar-left.latte:


{layout '@default.latte'}

{block content}
    <div>
        <div class="main">
            {include main}
        </div>
        <div class="sidebar-left">
            {include sidebar_left}
        </div>
    </div>
{/block}

contact.latte:


{layout 'layouts/@sidebar-left.latte'}

{block sidebar_left}
    ...
{/block}

{block main}
    ...
{/block}

Maybe there's a better setup for this, please share if you find one :)

You're the man!!! benggg....problem solved

  • Like 1
Link to comment
Share on other sites

  • 4 weeks later...

Two new macros in v038: minify and editlink.

Minify is an easy way to remove unnecessary whitespace and optionally to try some additional tweaks too. It's nowhere to ProCache or AIOM but can help reducing markup size. I could tweak things on one site to achieve 100% HTML minification according to gtmetrix but that required extra work on the markup so this macro alone won't help you on this :) 

As a bonus the macro can be used to remove whitespace between list items (<li>'s) which sometimes can cause headaches.

Editlink is another helper that can substitute bigger modules like FEEL, Fredi or the built-in frontend editor. There's nothing special in it, just outputs edit links to edit the page in the admin. First I was about to modify FEEL but I realized this would be more fun :) 

  • Like 2
Link to comment
Share on other sites

I've modified the editlink macro in v039, now you can easily add any attributes and additional url parameters to the edit link. This way it's easy to add edit links that open the admin in a lightbox. I've added a few lines about it to the docs along with a style example.

  • Like 3
Link to comment
Share on other sites

v041 contains two new filters: getlines and imageattrs.

The first is a simple replacement to my MultiValueTextformatter module. Unlike the module it can only return a simple or an associative array but in fact that's just enough most of the time.

The imageattrs filter is an easy way of adding image width-height-alt attributes. "alt" value is taken from image description or set empty if not provided, or optionally can be removed entirely.

  • Like 1
Link to comment
Share on other sites

Just popped in to praise the getlines filter's coolness :) I have a CKEditor field containing a simple unordered list. I wanted to animate each lines separately but it wasn't possible because the whole UL was rendered together so I couldn't add the required classes to each LI's.

Using getlines together with striptags filter it's now possible ($iterator is built-in):

<ul n:inner-foreach="($p->body|striptags|getlines) as $key => $value">
  <li data-animate data-animation-classes="animated fadeInLeft" data-animation-delay="{$iterator->counter * 300 + 200}">
    <h3>{$key}</h3> {$value}
  </li>
</ul>

Of course I could add the required attributes in CKEditor but that would require more troubles (modifying CKEditor field to allow attributes, hardcoded delay values, etc).

  • Like 3
Link to comment
Share on other sites

  • 2 weeks later...

There was an undocumented "list" filter among the filters that is now "officially" published. It was similar to the built-in implode filter but didn't choke if you passed a string instead of an array to it. I suggested this improvement in the Nette forums but they weren't too enthusiastic. In PW there are times (at least I had) when you don't know for sure if a data is a string or an array so I added this check to avoid errors.

The filter removes empty values so no need to check data existence manually. You can specify a separator string and/or a HTML tag, so it's easy to build eg. an unordered list. Just apply it to an array of possible items and the filter will take care of the rest. Here is an example.

  • Like 1
Link to comment
Share on other sites

Just upgraded the module to v0.4.3. There's a new option to disable the "noescape" filter, and a workaround for translations on a non-multilanguage site.

The latter is a simple solution for a situation when you copy over a latte file from another project full with translations but the current project is single-language only. This is perhaps not an issue if you're using full strings for translation keys, e.g "_t('Read more')" instead "_t('read_more_text')" because the original key is returned. But even so you may start a non-English project and there you'll be in trouble :) I was there several times and ended up rewriting strings/translations all over the project, now they can remain in place and I have to add translations at one file (which you can copy over).

  • Like 1
Link to comment
Share on other sites

Just added a new 'getembedurl', 'append' and 'prepend' filters to v4.4.

With getembedurl you can retrieve the embed url to be used when embedding videos (currently for Youtube/Vimeo). Editors aren't really capable of copying the embed url so you can use this filter to allow them adding the url of the video to the admin.

Filters append and prepend are convenience filters that you can use to quickly append/remove data. Data can be primitive or arrays. These filters are particularly useful when chaining filters so you don't have to split the current line just to modify the original data.

The bodyclass filter now contains the name of the viewFile (if exists), prefixed with "v-", and directory separators converted to "-". Custom classes can be added using $page->body_class if needed.

Link to comment
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
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      This module lets you add some custom menu items to the main admin menu, and you can set the dropdown links dynamically in a hook if needed.
      Sidenote: the module config uses some repeatable/sortable rows for the child link settings, similar to the ProFields Table interface. The data gets saved as JSON in a hidden textarea field. Might be interesting to other module developers?
      Custom Admin Menus
      Adds up to three custom menu items with optional dropdowns to the main admin menu.
      The menu items can link to admin pages, front-end pages, or pages on external websites.
      The links can be set to open in a new browser tab, and child links in the dropdown can be given an icon.
      Requires ProcessWire v3.0.178 or newer.
      Screenshots
      Example of menu items

      Module config for the menus

      Link list shown when parent menu item is not given a URL

      Advanced
      Setting child menu items dynamically
      If needed you can set the child menu items dynamically using a hook.
      Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $colours = $event->wire()->pages->findRaw('template=colour', ['title', 'url', 'page_icon']); $children = []; foreach($colours as $colour) { // Each child item should be an array with the following keys $children[] = [ 'icon' => $colour['page_icon'], 'label' => $colour['title'], 'url' => $colour['url'], 'newtab' => false, ]; } $event->return = $children; } }); Create multiple levels of flyout menus
      It's also possible to create multiple levels of flyout submenus using a hook.

      For each level a submenu can be defined in a "children" item. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $children = [ [ 'icon' => 'adjust', 'label' => 'One', 'url' => '/one/', 'newtab' => false, ], [ 'icon' => 'anchor', 'label' => 'Two', 'url' => '/two/', 'newtab' => false, 'children' => [ [ 'icon' => 'child', 'label' => 'Red', 'url' => '/red/', 'newtab' => false, ], [ 'icon' => 'bullhorn', 'label' => 'Green', 'url' => '/green/', 'newtab' => false, 'children' => [ [ 'icon' => 'wifi', 'label' => 'Small', 'url' => '/small/', 'newtab' => true, ], [ 'icon' => 'codepen', 'label' => 'Medium', 'url' => '/medium/', 'newtab' => false, ], [ 'icon' => 'cogs', 'label' => 'Large', 'url' => '/large/', 'newtab' => false, ], ] ], [ 'icon' => 'futbol-o', 'label' => 'Blue', 'url' => '/blue/', 'newtab' => true, ], ] ], [ 'icon' => 'hand-o-left', 'label' => 'Three', 'url' => '/three/', 'newtab' => false, ], ]; $event->return = $children; } }); Showing/hiding menus according to user role
      You can determine which menu items can be seen by a role by checking the user's role in the hook.
      For example, if a user has or lacks a role you could include different child menu items in the hook return value. Or if you want to conditionally hide a custom menu altogether you can set the return value to false. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); $user = $event->wire()->user; // For custom menu number 1... if($menu_number === 1) { // ...if user does not have some particular role... if(!$user->hasRole('foo')) { // ...do not show the menu $event->return = false; } } });  
      https://github.com/Toutouwai/CustomAdminMenus
      https://processwire.com/modules/custom-admin-menus/
    • By tcnet
      This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist.
      Settings
      The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier.
      Notification email
      Specifies the email address to which the notification emails should be sent.
        Email subject
      Specifies the subject line for the notification email.
        Post variables
      Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass
        Server variables
      Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT
      Link to ProcessWire module directory:
      https://processwire.com/modules/login-fail-notifier/
      Link to github.com:
      https://github.com/techcnet/LoginFailNotifier
    • By Fokke
      ProcessWire 3.x markup module for rendering meta tags in HTML document head section. Note that this module is not a full-blown SEO solution, but rather a simple tool for rendering meta tags based on module configuration. Adding custom meta tags is also supported.
      Built-in meta tags
      The following meta tags are supported out-of-the-box:
      Document title consisting of page title and site name Character set Canonical Viewport Description Keywords Hreflang tags Open Graph og:title og:site_name og:type og:url og:description og:image og:image:width og:image:height Twitter meta tags twitter:card twitter:site twitter:creator twitter:title twitter:description twitter:image Facebook meta tags fb:app_id The full documentation with configurable options can be found here: https://github.com/Fokke-/MarkupMetadata
       
      Requirements:
      ProcessWire>=3.0.0 PHP >=7.1 Installation using Composer
      composer require fokke/markup-metadata Manual installation
      Download latest version from https://github.com/Fokke-/MarkupMetadata/archive/master.zip Extract module files to site/modules/MarkupMetadata directory.
    • By m.sieber
      ITRK-Service for ProcessWire
      Module for the automated transfer of imprint, data protection declaration and terms and conditions from IT-Recht Kanzlei to your ProcessWire installation
      What is ITRK Service for ProcessWire?
      ITRK-Service for ProcessWire is a free module for ProcessWire CMS. It provides an interface to the update service of IT-Recht Kanzlei, via which the legal texts of your online presence are automatically updated. In this way, the texts remain legally secure and warning-proof in the long term. Imprint, data protection declaration, revocation and general terms and conditions are currently supported.
      You can find our documentation (in german language) here: https://www.pupit.de/itrk-service-for-processwire/dokumentation/

      Download: https://www.pupit.de/itrk-service-for-processwire/
      Github: https://github.com/pupit-de/pwItrkServiceConnector
    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      Documentation
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
       
×
×
  • Create New...