Jump to content
Soma

MarkupSimpleNavigation

Recommended Posts

Yes, great! Haven't tried the OR-groups selector yet.

"selector_level2" => "(parent!=<parent_id_of_permission_controlled_pages>), (id=$items)"

does the job.

Thanks you very much!

Share this post


Link to post
Share on other sites

Hi Soma,

thanks for this cool module – Danke :-)

I have a question about adding some additional stuff (data-attribut and css-styles) to the markup.

I'm using the uikit: http://getuikit.org and I wanted to insert their accordion in my menu: http://getuikit.org/docs/nav.html (check »Accordion«)

To convert a menu link into a accordion, I  have to add this: <ul class="uk-nav uk-nav-parent-icon" data-uk-nav> and also this: <li class="uk-parent">

to a sublink.

I'm trying to achieve this:

Start

Page 1

   parent-subpage --> this shall be the accordion link

      item 1

      item 2

      item 3

Currently I'm using this:

<?php
$treeMenu = $modules->get("MarkupSimpleNavigation"); // load the module
$options = array(
'parent_class' => 'parent',
'current_class' => 'active',
'has_children_class' => 'has_children',
'collapsed' => false,
'show_root' => true
);
echo $treeMenu->render($options);
?>

Thank you

Edited by cstevensjr
Put example in Code Block

Share this post


Link to post
Share on other sites

If I understand it right, using the options

'outer_tpl' => '<ul class="uk-nav uk-nav-parent-icon" data-uk-nav>||</ul>',
'inner_tpl' => '<ul class="uk-nav-sub">||</ul>',
'parent_class' => 'uk-parent',

should do it.

  • Like 1

Share this post


Link to post
Share on other sites

If I understand it right, using the options

'outer_tpl' => '<ul class="uk-nav uk-nav-parent-icon" data-uk-nav>||</ul>',
'inner_tpl' => '<ul class="uk-nav-sub">||</ul>',
'parent_class' => 'uk-parent',

should do it.

Thanks for your help.

But for various reasons, I choose a different solution. One of the reason was, that I didn't thought about the accordion trigger. It can't be a link and trigger at the same time.

So I'm gonna build a half static, half dynamic accordion menu. It's possible, cause it's with Processwire :-)

Share this post


Link to post
Share on other sites

@surffun it's the "collapsed" => true, option.

  • Like 1

Share this post


Link to post
Share on other sites

Then in that case you would simply need to tell the module what root your menu has. Default is "/". (third argument)

Most common is for example use the $page->rootParent() as the root. ($page->rootParent() will always return the root level page of the current page even if on a root page itself)

echo $tree->render($options, null, $page->rootParent());
  • Like 1

Share this post


Link to post
Share on other sites

Sorry there's no example CSS. Definately something I try to add.

Write your CSS with using the css classes the module gives you by default. .  Often not much is needed. Also you can change the class names and use various tpl options too to add your own.

I mostly use the default and give the "outer_tpl" => "<ul class='main-menu'>||</ul>" as a starting point.

  • Like 1

Share this post


Link to post
Share on other sites

Hello
my english is not so good, I hope you can help me
I would like to use this bootsrap navigation, I try to have 3 days :(
can someone please help me ??
 
these are my options

$options = array(
    'parent_class' => '',
    'current_class' => 'active',
    'has_children_class' => 'dropdown',
    'levels' => false,
    'levels_prefix' => '',
    'max_levels' => null,
    'firstlast' => false,
    'collapsed' => false,
    'show_root' => true,
    'selector' => 'template=site',
    'selector_field' => '',
    'outer_tpl' => '<ul class="nav navbar-nav">||</ul>',
    'inner_tpl' => '<ul class="dropdown-menu">||</ul>',
    //'list_tpl' => '<li%s>||</li>',
	'list_tpl' => '<li%s>||</li>',
    'list_field_class' => '',
    'item_tpl' => '<a class="dropdown-toggle" data-toggle="dropdown" href="{url}">{title}</a>',
    'item_current_tpl' => '<a href="{url}">{title}</a>',
    'xtemplates' => '',
    'xitem_tpl' => '<a href="{url}">{title}</a>',
    'xitem_current_tpl' => '<span>{title}</span>',
    'date_format' => 'Y/m/d',
    'code_formatting' => true,
    'debug' => false
);

that is the output......

how can I insert the dropdown dropdown-submenu to this position

08e97b-1459261661.jpg

<!DOCTYPE html>
<html lang="de">
  <head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <!-- Die 3 Meta-Tags oben *müssen* zuerst im head stehen; jeglicher sonstiger head-Inhalt muss *nach* diesen Tags kommen -->
    <title>Bootstrap-Basis-Vorlage</title>

    <!-- Bootstrap -->
    <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css">
    <!--<link rel="stylesheet" type="text/css" href="site/templates/js/topnavsub/css/bootstrap-submenu.min.css">-->
    <!--<script src="site/templates/js/topnavsub/js/bootstrap-submenu.min.js"></script>-->
<style type="text/css">
.dropdown-menu > li.kopie > a {
    padding-left:5px;
}
 
.dropdown-submenu {
    position:relative;
}
.dropdown-submenu>.dropdown-menu {
   top:0;left:100%;
   margin-top:-6px;;
   -webkit-border-radius:0 6px 6px 6px;-moz-border-radius:0 6px 6px 6px;border-radius:0 6px 6px 6px;
 }
  
.dropdown-submenu > a:after {
  border-color: transparent transparent transparent #333;
  border-style: solid;
  border-width: 5px 0 5px 5px;
  content: " ";
  display: block;
  float: right;  
  height: 0;     
  margin-right: -10px;
  margin-top: 5px;
  width: 0;
}
 
.dropdown-submenu:hover>a:after {
    border-left-color:#555;
 }

.dropdown-menu > li > a:hover, .dropdown-menu > .active > a:hover {
  text-decoration: underline;
}  

@media (max-width: 767px) {

  .navbar-nav  {
     display: inline;
  }
  .navbar-default .navbar-brand {
    display: inline;
  }
  .navbar-default .navbar-toggle .icon-bar {
    background-color: #fff;
  }
  .navbar-default .navbar-nav .dropdown-menu > li > a {
    color: red;
    background-color: #ccc;
    border-radius: 4px;
    margin-top: 2px;   
  }
   .navbar-default .navbar-nav .open .dropdown-menu > li > a {
     color: #333;
   }
   .navbar-default .navbar-nav .open .dropdown-menu > li > a:hover,
   .navbar-default .navbar-nav .open .dropdown-menu > li > a:focus {
     background-color: #ccc;
   }

   .navbar-nav .open .dropdown-menu {
     border-bottom: 1px solid white; 
     border-radius: 0;
   }
  .dropdown-menu {
      padding-left: 10px;
  }
  .dropdown-menu .dropdown-menu {
      padding-left: 20px;
   }
   .dropdown-menu .dropdown-menu .dropdown-menu {
      padding-left: 30px;
   }
   li.dropdown.open {
    border: 0px solid red;
   }

}
 
@media (min-width: 768px) {
  ul.nav li:hover > ul.dropdown-menu {
    display: block;
  }
  #navbar {
    text-align: center;
  }
}  
 </style>
    <!-- Unterstützung für Media Queries und HTML5-Elemente in IE8 über HTML5 shim und Respond.js -->
    <!-- ACHTUNG: Respond.js funktioniert nicht, wenn du die Seite über file:// aufrufst -->
    <!--[if lt IE 9]>
      <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
      <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
    <![endif]-->
  </head>
  <body>
<div class="container">

<nav class="navbar navbar-default" role="navigation">
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#navbar-collapse-1">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="#" target="_blank">NewWindow</a>
</div>
<div class="collapse navbar-collapse" id="navbar-collapse-1">

<ul class="nav navbar-nav">
	<li class="active"><a href="/">Home</a></li>
	<li class="dropdown"><a class="dropdown-toggle" data-toggle="dropdown" href="/de/seit0/">Site 1</a>
		<ul class="dropdown-menu">
			<li class="dropdown"><a class="dropdown-toggle" data-toggle="dropdown" href="/de/seit0/action/">SubSite 1</a>
				<ul class="dropdown-menu">
					<li class="dropdown"><a class="dropdown-toggle" data-toggle="dropdown" href="/de/seit0/action/sub-action/">Sub action</a>
						<ul class="dropdown-menu">
							<li><a class="dropdown-toggle" data-toggle="dropdown" href="/de/seit0/action/sub-action/xxxxxxx/">SubSite</a></li>
						</ul>
						</li>
					<li class="dropdown"><a class="dropdown-toggle" data-toggle="dropdown" href="/de/seit0/action/another-sub-action/">Another sub action</a>
						<ul class="dropdown-menu">
							<li><a class="dropdown-toggle" data-toggle="dropdown" href="/de/seit0/action/another-sub-action/sub-action/">Sub action</a></li>
						</ul>
						</li>
				</ul>
				</li>
		</ul>
		</li>
	<li><a class="dropdown-toggle" data-toggle="dropdown" href="/de/test140/">Site 2</a></li>
	<li><a class="dropdown-toggle" data-toggle="dropdown" href="/de/aaaaaaaaaaa/">Site 3</a></li>
</ul></div>
</nav>


</div>
    <!-- jQuery (wird für Bootstrap JavaScript-Plugins benötigt) -->
    <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script>
    <!-- Binde alle kompilierten Plugins zusammen ein (wie hier unten) oder such dir einzelne Dateien nach Bedarf aus -->
    <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js"></script>
    
    <script>
	

   </script>
  </body>
</html>

Share this post


Link to post
Share on other sites

Have you tried:

'has_children_class' => 'dropdown dropdown-submenu',

Share this post


Link to post
Share on other sites

Hi slave,

Please look at the hooking example provided by soma on Github. You need to change it like this (written in browser, not tested):

function hookGetListClass(HookEvent $event){
    $child = $event->arguments('page'); // current rendered child page
    $class = $event->arguments('class'); // the class string already present
    // any check on that child to set your custom class
    if(count($child->parents) >= 2 && $child->numChildren){ // Only proceed if at least two parents and if an item has children
        $event->return .= " dropdown-submenu"; // add your custom class to the existing
    }
}
  • Like 1

Share this post


Link to post
Share on other sites

hi surffun,

of course this is possible. see the docs for all the options: https://github.com/somatonic/MarkupSimpleNavigation#markupsimplenavigation-116

// you need this line only once
$menu = $modules->get('MarkupSimpleNavigation');

// your main menu
echo $menu->render(array(
    'outer_tpl' => '<ul class="show-only-on-big-screens">||</ul>',
    // all other options here
));

// your footer menu for mobile
echo $menu->render(array(
    'outer_tpl' => '<ul class="show-only-on-small-screens">||</ul>',
    // all other options here
));

and then you can hide/show the menu by defining css rules for the classes "show-only-on-small/big-screens": http://www.w3schools.com/cssref/css3_pr_mediaquery.asp

  • Like 3

Share this post


Link to post
Share on other sites

the menu css would be in the frontend code you are writing, or using; the module is there to generate the markup you require for the menu.

What framework are you using for your site? Many frameworks have navigation css built in (such as bootstrap)

Share this post


Link to post
Share on other sites

correct, so you just need to make sure that MSN is generating the needed markup for the framework you are using.

Does this make sense?

Share this post


Link to post
Share on other sites

you just put the css in a stylesheet that is loaded on the page. That file needs to hold the CSS rules that apply to the menu.

Share this post


Link to post
Share on other sites

@surffun it's kinda hard to tell in general and it's so obvious that we may fail to see where you're struggling. There's tons of options in MSN to modify the output and examples are everywhere.

Still don't know what the problem is you have.

Share this post


Link to post
Share on other sites

https://processwire.com/talk/topic/1036-markupsimplenavigation/?p=8998

First post of this thread there's a link to an gist with an example to output bootstrap like html.


But it's just an old example I worked out back then. I never used bootstrap so can't tell if it's still working with newer versions? (one of the reason I avoid frameworks :))

  • Like 1

Share this post


Link to post
Share on other sites

I know how I "connect" html markup with css but I do not know how I "connect" MSN with css that's the problem.

You don't need to do anything different with your CSS than you would do on a static website - that goes for the MSN module, any PW module and PW in general. Your CSS just sits in a file linked in the <head> of your template.

If I understand correctly you had an HTML page "start.html" and in PW you have successfully added a template "start" associated with template file "start.php". Lets use a simplified example and say start.php looks like this...

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <title><?= $page->title ?></title>
    <link rel="stylesheet" href="/site/templates/css/mystyles.css">
</head>
<body>
<ul>
    <li><a href="/page-1/">Page 1</a></li>
    <li><a href="/page-2/">Page 2</a></li>
    <li><a href="/page-3/">Page 3</a></li>
</ul>
<?= $page->body ?>
</body>
</html>

...and that unordered list is your menu. Let's also assume you have added those 3 pages to your PW website via the admin. Now you want to replace the static menu with a dynamic menu generated by MSN. You replace the menu markup with the call to MSN. No options are needed because your menu markup doesn't have any classes or anything not generated the MSN default.

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <title><?= $page->title ?></title>
    <link rel="stylesheet" href="/site/templates/css/mystyles.css">
</head>
<body>
<?php
$nav = $modules->get("MarkupSimpleNavigation"); // load the module
echo $nav->render(); // render default menu
?>
<?= $page->body ?>
</body>
</html>

But suppose your static menu does have some classes and also an item for the Home page.

<ul class="main-menu">
    <li class="menu-item"><a class="menu-link" href="/">Home</a></li>
    <li class="menu-item"><a class="menu-link" href="/page-1/">Page 1</a></li>
    <li class="menu-item"><a class="menu-link" href="/page-2/">Page 2</a></li>
    <li class="menu-item"><a class="menu-link" href="/page-3/">Page 3</a></li>
</ul>

Now you do need to set some options for MSN.

<?php
$nav = $modules->get("MarkupSimpleNavigation"); // load the module
// set some options
$nav_options = array(
	'show_root' => true,
	'outer_tpl' => '<ul class="main-menu">||</ul>',
	'list_field_class' => 'menu-item',
	'item_tpl' => '<a class="menu-link" href="{url}">{title}</a>'
);
echo $nav->render($nav_options); // render the menu
?>

Get the idea? So if you were using a bootstrap menu in your static website then you just need to use the MSN options array (and occasionally a hook if you have some more unusual markup) to tell MSN to generate the markup you want.

  • Like 2

Share this post


Link to post
Share on other sites

hi i need help please.
I need this navigation structur

(home) (dienstl1) (dienstl2) (dienstl3)

my site struct is this

home
dienstleistungen (temp=produkte)
--dienstl1 (temp=produktkategorie)
----die1
----die2
----die3
--dienstl2 (temp=produktkategorie)
----die1
----die2
----die3
--dienstl3 (temp=produktkategorie)
----die1
----die2
----die3

I have already tried everything

Share this post


Link to post
Share on other sites

@slave

<?php
$nav = $modules->get("MarkupSimpleNavigation"); // load the module
// set options
$nav_options = array(
    'show_root' => true,
    'selector' => 'template=produktkategorie'
);
echo $nav->render($nav_options); // render the menu
?>
  • Like 1

Share this post


Link to post
Share on other sites

@Robins

thank you for your help. :)
but that has not helped.
please see the graphic

bafj4p9s.jpg

Share this post


Link to post
Share on other sites

@slave

<?php
$nav = $modules->get("MarkupSimpleNavigation"); // load the module
// set options
$nav_options = array(
    'show_root' => true,
    'selector' => 'template=produktkategorie'
);
echo $nav->render($nav_options); // render the menu
?>

thanks vor your help

but that has not helped kann yout help me please

Share this post


Link to post
Share on other sites

@slave: I didn't notice your produktkategorie pages are not direct children of Home.

Try making a PageArray of your menu items and giving that to MSN as the root argument.

<?php
$nav = $modules->get("MarkupSimpleNavigation"); // load the module
// make PageArray of your menu items
$menu_pages = $pages->find("template=produktkategorie")->prepend($pages->get("/"));
echo $nav->render(null, null, $menu_pages); // render the menu
?>
  • Like 3

Share this post


Link to post
Share on other sites

@slave: I didn't notice your produktkategorie pages are not direct children of Home.

Try making a PageArray of your menu items and giving that to MSN as the root argument.

<?php
$nav = $modules->get("MarkupSimpleNavigation"); // load the module
// make PageArray of your menu items
$menu_pages = $pages->find("template=produktkategorie")->prepend($pages->get("/"));
echo $nav->render(null, null, $menu_pages); // render the menu
?>

Wow :)

many thanks exactly it was what I wanted.

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...