Jump to content
Soma

MarkupSimpleNavigation

Recommended Posts

It is 'item_current_tpl'

Sorry for the confusion, it seems to be wrong in the documentation since near beginning. Interesting nobody recognized it by now.

it's still "active" in the github wiki documentation... https://github.com/somatonic/MarkupSimpleNavigation/wiki/MarkupSimpleNavigation-Documentation

but thx so much for this work! its great

Share this post


Link to post
Share on other sites

I'd like to add a dynamic parent class based on the page name. Is there a way of doing this at the moment or is it possible to add such a feature?

Something like:

'parent_class' => 'parent {name}'

or 

'active_parent' => true

This is such a great module and time saver! Thanks for creating it Soma!

Share this post


Link to post
Share on other sites

Hey @mats, can you tell a little more what you want to do or better why, so I can think a little better? :)

Share this post


Link to post
Share on other sites

Hi Soma! I have a news page with sections and sub sections, each section has it's own color which is inherited to it's subsections. When on a sub section i'd like to indicate both the current subsection and the parent section with the section color. Does this make any sense? :undecided:  

Share this post


Link to post
Share on other sites

I might add a list field class option string, so you can add fields you want to each <li> item.

so you could add whatever classes and do:

'list_field_class' => '{template} p{id}',

and it would add this to every page list_tpl. And if left empty (default) it won't output.

I think then with this one can cover all aspects a basic navigation needs more or less.

  • Like 1

Share this post


Link to post
Share on other sites

Sounds great! Thanks a lot Soma!

Share this post


Link to post
Share on other sites

I just commited an update to 1.1.6

While editing the wiki documentation page it somehow was deleted after editing doh! So updated readme a little and copied that to the wiki.
 
 
`list_field_class` option (new in 1.1.6)
 
You can optionally define custom classes using a string that can contain tags for field names of pages.
For example:
 
'list_field_class' => '{template} p{id}', 
 
will add ' basic-page p1001' to each 'list_tpl' class string.
  • Like 1

Share this post


Link to post
Share on other sites

Thanks for the update Soma. There seems to be a undefined variable named class in the code (line 238 if i remember correctly).  

I still would like to be able to set a class on the parent/s like the item_current_tpl, if possible. I think this would it a lot easier to style the navigation. I understand if you're not willing to add it since this kind of feature might have a bit limited use. 

Share this post


Link to post
Share on other sites

Thanks mats for the heads up. I think It was late when doing this. Have to take a look a again at that $class variable. I should practice what I preach :D

As for the wish, I'm not sure what you mean because you can aleady define what you want:

parent_class : class for all active parents

has_children_class : class for parents that have children

now new

list_field_class: add classes like {name} to each item (which is what you need not?)

so a active parent of the current page will have

<li class="parent has_children about">...

I didn't just add this new feature to "parent_class" because adding the possibility to add {fieldname} to all items covers all needs and not just for parents.

  • Like 1

Share this post


Link to post
Share on other sites

I dont really get what the problem is.

You have the current parent and the section.

list_field_class => 'p{id}'

Then in css

li.parent.p1001{..}

Or

li.parent.p1001 > a { ..}

To style active section item with parent id 1001

  • Like 1

Share this post


Link to post
Share on other sites

You're right Soma, it's my css that's messed up and i'm stuck in the old way of styling the navigation. I just have to rethink it.

Thanks for all your help!

  • Like 1

Share this post


Link to post
Share on other sites

If something I learned over the years, it's to watch your css for navigations ... :) as simple as possible pays out.

However since older browsers are left behind it good to move on.

I updated the Module to 1.1.7 to fix the warning. Thx for mention.

  • Like 1

Share this post


Link to post
Share on other sites

Probably a simple thing to do but how would I go about having lowercase letters in the output?


Was thinking of using strtolower in the item_tpl but not sure how to approach it.

Thanks Soma.

Share this post


Link to post
Share on other sites

Newbie question...

I donwnloaded this great module, but now run into some trouble, how can I do the following:

In order to reduce bounce rate I want to split up longer pages in sub pages.

I want to have the following structure for the pages that will be split into more pages

topic

- topic/page2

- topic/page3

- topic/page4

- topic/page5

then on each of all the pages above I want a clickable TOC just for this topic and its sub pages

How to do this so it is as much automated as possible?

Share this post


Link to post
Share on other sites

Not exactly sure about the structure but you could try this:

If you have

/article/

/article/page1

/article/page2

/article/page3

Code on article page

$root = $page;
echo $nav->render(null, $page, $root); // $nav being instance of the module

And on the child pages

$root = $page->parent;
echo $nav->render(null, $page, $root);

$page being the current page and $root is from where it starts generating navigation.

Yu could also use the various options available to make adjustments, if not needed you can set it to "null" as in the example.

Share this post


Link to post
Share on other sites

@Soma, thanks,

yes structure like you said is correct

/article/

/article/page1

/article/page2

And on each page (article and child I would like to see a snippet as output like the following:

<details class="pw-toc" open="open"><summary>In this article</summary>
<ol>
    <li><a class="active" href="http://mydomain.com/article/">How Processwire beats any CMS handsdown</a></li>
    <li><a href="http://mydomain.com/article/page2/">3 Mistakes You Should not make in choosing a CMS</a></li>
    <li><a href="http://mydomain.com/article/page3/">Can you do this with your current CMS</a></li>
</ol></details>

So if I use on the article page:

$root = $page;
echo $nav->render(null, $page, $root); // $nav being instance of the module

and on the child pages:

$root = $page->parent;
echo $nav->render(null, $page, $root);

What step is then further needed to produce the output like above?

Oh and just for anybody's information, stuff like this usually drops your bounce rate in most cases with 20-30% easily, so google clearly loves it, thanks!

Share this post


Link to post
Share on other sites

Right with this structure it would look like this:

<details class="pw-toc" open="open">
    <summary>In this article</summary>
<?php
    $treeMenu = $modules->get("MarkupSimpleNavigation");
    $options = array(
        'max_levels' => 1,
        'current_class' => 'current',
        'outer_tpl' => '<ol>||</ol>',
        'show_root' => true
    );
    $root = $page->parents->count == 1 ? $page : $page->parent;
    echo $treeMenu->render($options, $page, $root);
?>
</details>
 

The root here is found by counting what level, and either take parent or page itself as the root.

--

You could also define root alternatively like maybe depending on the structure and templates:

$root = $page->parent->template == 'article' ? $page->parent : $page;
echo $treeMenu->render($options, $page, $root);

So saying if parent page template is 'article' take current page->parent as root, if not we take current page assuming it's the top 'article' page and not a child.

Share this post


Link to post
Share on other sites

Hi!

Read all thread, but can't solve my problem.

My structure:

Home

-- About

-- Something Else

-- Want it in menu1

----Subpage11

----Subpage12

---- ..more of them..

-- Want it in menu2

----Subpage21

----Subpage22

---- ..more of them2..

What is the easiest way to render only "Want it in menu 1|2" and their children?

I think of excluding all others pages, but pages can grow. How can I just point only 2 of pages to render?

Sorry for my English. Hope you understand what I mean.

upd:

If only be that you can specify multiple parents.

Share this post


Link to post
Share on other sites

You can' specify multiple roots, but you can exclude children.

$options = array("selector"=>"id!=1003|1004");
echo $navTree->render($options);

So the pages with those id's wont be rendered.

Or you could add a checkbox custom field to the templates to only include them if checked from the navigation.

$options = array("selector"=>"show_in_menu=1");
echo $navTree->render($options);
  • Like 1

Share this post


Link to post
Share on other sites

You can' specify multiple roots, but you can exclude children.

Thank you, Soma!

I'll try to exclude pages by template.

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 teppo
      Needed a really simple solution to embed audio files within page content and couldn't find a module for that, so here we go. Textformatter Audio Embed works a bit like Textformatter Video Embed, converting this:
      <p>https://www.domain.tld/path/to/file.mp3</p> Into this:
      <audio controls class="TextformatterAudioEmbed"> <source src="https://www.domain.tld/path/to/file.mp3" type="audio/mpeg"> </audio> The audio element has pretty good browser support, so quite often this should be enough to get things rolling 🙂
      GitHub repository: https://github.com/teppokoivula/TextformatterAudioEmbed Modules directory: https://modules.processwire.com/modules/textformatter-audio-embed/
    • By Richard Jedlička
      Tense    
      Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
      Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.

      See example or see usage in a real project.
      How to use?
      1. Install it: 
      composer global require uiii/tense 2. Create tense.yml config:
      tense init 3. Run it:
      tense run  
      For detailed instructions see Github page: https://github.com/uiii/tense
       
      This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
       
      What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
    • By Chris Bennett
      Hi all, I am going round and round in circles and would greatly appreciate if anyone can point me in the right direction.
      I am sure I am doing something dumb, or missing something I should know, but don't. Story of my life 😉

      Playing round with a module and my basic problem is I want to upload an image and also use InputfieldMarkup and other Inputfields.
      Going back and forth between trying an api generated page defining Fieldgroup, Template, Fields, Page and the InputfieldWrapper method.

      InputfieldWrapper method works great for all the markup stuff, but I just can't wrap my head around what I need to do to save the image to the database.
      Can generate a Field for it (thanks to the api investigations) but not sure what I need to do to link the Inputfield to that. Tried a lot of stuff from various threads, of varying dates without luck.
      Undoubtedly not helped by me not knowing enough.

      Defining Fieldgroup etc through the api seems nice and clean and works great for the images but I can't wrap my head around how/if I can add/append/hook the InputfieldWrapper/InputfieldMarkup stuff I'd like to include on that template as well. Not even sure if it should be where it is on ___install with the Fieldtype stuff or later on . Not getting Tracy errors, just nothing seems to happen.
      If anyone has any ideas or can point me in the right direction, that would be great because at the moment I am stumbling round in the dark.
       
      public function ___install() { parent::___install(); $page = $this->pages->get('name='.self::PAGE_NAME); if (!$page->id) { // Create fieldgroup, template, fields and page // Create new fieldgroup $fmFieldgroup = new Fieldgroup(); $fmFieldgroup->name = MODULE_NAME.'-fieldgroup'; $fmFieldgroup->add($this->fields->get('title')); // needed title field $fmFieldgroup->save(); // Create new template using the fieldgroup $fmTemplate = new Template(); $fmTemplate->name = MODULE_NAME; $fmTemplate->fieldgroup = $fmFieldgroup; $fmTemplate->noSettings = 1; $fmTemplate->noChildren = 1; $fmTemplate->allowNewPages = 0; $fmTemplate->tabContent = MODULE_NAME; $fmTemplate->noChangeTemplate = 1; $fmTemplate->setIcon(ICON); $fmTemplate->save(); // Favicon source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFavicon'; $fmField->label = 'Favicon'; $fmField->focusMode = 'off'; $fmField->gridMode = 'grid'; $fmField->extensions = 'svg png'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Favicon Silhouette source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFaviconSilhouette'; $fmField->label = 'SVG Silhouette'; $fmField->notes = 'When creating a silhouette/mask svg version for Safari Pinned Tabs and Windows Tiles, we recommend setting your viewbox for 0 0 16 16, as this is what Apple requires. In many cases, the easiest way to do this in something like illustrator is a sacrificial rectangle with no fill, and no stroke at 16 x 16. This forces the desired viewbox and can then be discarded easily using something as simple as notepad. Easy is good, especially when you get the result you want without a lot of hassle.'; $fmField->focusMode = 'off'; $fmField->extensions = 'svg'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Create: Open Settings Tab $tabOpener = new Field(); $tabOpener->type = new FieldtypeFieldsetTabOpen(); $tabOpener->name = 'fmTab1'; $tabOpener->label = "Favicon Settings"; $tabOpener->collapsed = Inputfield::collapsedNever; $tabOpener->addTag(MODULE_NAME); $tabOpener->save(); // Create: Close Settings Tab $tabCloser = new Field(); $tabCloser->type = new FieldtypeFieldsetClose; $tabCloser->name = 'fmTab1' . FieldtypeFieldsetTabOpen::fieldsetCloseIdentifier; $tabCloser->label = "Close open tab"; $tabCloser->addTag(MODULE_NAME); $tabCloser->save(); // Create: Opens wrapper for Favicon Folder Name $filesOpener = new Field(); $filesOpener->type = new FieldtypeFieldsetOpen(); $filesOpener->name = 'fmOpenFolderName'; $filesOpener->label = 'Wrap Folder Name'; $filesOpener->class = 'inline'; $filesOpener->collapsed = Inputfield::collapsedNever; $filesOpener->addTag(MODULE_NAME); $filesOpener->save(); // Create: Close wrapper for Favicon Folder Name $filesCloser = new Field(); $filesCloser->type = new FieldtypeFieldsetClose(); $filesCloser->name = 'fmOpenFolderName' . FieldtypeFieldsetOpen::fieldsetCloseIdentifier; $filesCloser->label = "Close open fieldset"; $filesCloser->addTag(MODULE_NAME); $filesCloser->save(); // Create Favicon Folder Name $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeText"); $fmField->name = 'folderName'; $fmField->label = 'Favicon Folder:'; $fmField->description = $this->config->urls->files; $fmField->placeholder = 'Destination Folder for your generated favicons, webmanifest and browserconfig'; $fmField->columnWidth = 100; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon('folder'); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($tabOpener); $fmFieldgroup->add($filesOpener); $fmFieldgroup->add($fmField); $fmFieldgroup->add($filesCloser); $fmFieldgroup->add($tabCloser); $fmFieldgroup->save(); /////////////////////////////////////////////////////////////// // Experimental Markup Tests $wrapperFaviconMagic = new InputfieldWrapper(); $wrapperFaviconMagic->attr('id','faviconMagicWrapper'); $wrapperFaviconMagic->attr('title',$this->_('Favicon Magic')); // field show info what $field = $this->modules->get('InputfieldMarkup'); $field->name = 'use'; $field->label = __('How do I use it?'); $field->collapsed = Inputfield::collapsedNever; $field->icon('info'); $field->attr('value', 'Does this even begin to vaguely work?'); $field->columnWidth = 50; $wrapperFaviconMagic->add($field); $fmTemplate->fields->add($wrapperFaviconMagic); $fmTemplate->fields->save(); ///////////////////////////////////////////////////////////// // Create page $page = $this->wire( new Page() ); $page->template = MODULE_NAME; $page->parent = $this->wire('pages')->get('/'); $page->addStatus(Page::statusHidden); $page->title = 'Favicons'; $page->name = self::PAGE_NAME; $page->process = $this; $page->save(); } }  
    • By Sebi
      Since it's featured in ProcessWire Weekly #310, now is the time to make it official:
      Here is Twack!
      I really like the following introduction from ProcessWire Weekly, so I hope it is ok if I use it here, too. Look at the project's README for more details!
      Twack is a new — or rather newish — third party module for ProcessWire that provides support for reusable components in an Angular-inspired way. Twack is implemented as an installable module, and a collection of helper and base classes. Key concepts introduced by this module are:
      Components, which have separate views and controllers. Views are simple PHP files that handle the output for the component, whereas controllers extend the TwackComponent base class and provide additional data handling capabilities. Services, which are singletons that provide a shared service where components can request data. The README for Twack uses a NewsService, which returns data related to news items, as an example of a service. Twack components are designed for reusability and encapsulating a set of features for easy maintainability, can handle hierarchical or recursive use (child components), and are simple to integrate with an existing site — even when said site wasn't originally developed with Twack.
      A very basic Twack component view could look something like this:
      <?php namespace ProcessWire; ?> <h1>Hello World!</h1> And here's how you could render it via the API:
      <?php namespace Processwire; $twack = $modules->get('Twack'); $hello = $twack->getNewComponent('HelloWorld'); ?> <html> <head> <title>Hello World</title> </head> <body> <?= $hello->render() ?> </body> </html> Now, just to add a bit more context, here's a simple component controller:
      <?php namespace ProcessWire; class HelloWorld extends TwackComponent { public function __construct($args) { parent::__construct($args); $this->title = 'Hello World!'; if(isset($args['title'])) { $this->title = $args['title']; } } } As you can see, there's not a whole lot new stuff to learn here if you'd like to give Twack a try in one of your projects. The Twack README provides a really informative and easy to follow introduction to all the key concepts (as well as some additional examples) so be sure to check that out before getting started. 
      Twack is in development for several years and I use it for every new project I build. Also integrated is an easy to handle workflow to make outputs as JSON, so it can be used to build responses for a REST-api as well. I will work that out in one section in the readme as well. 
      If you want to see the module in an actual project, I have published the code of www.musical-fabrik.de in a repository. It runs completely with Twack and has an app-endpoint with ajax-output as well.
      I really look forward to hear, what you think of Twack🥳!
      Features Installation Usage Quickstart: Creating a component Naming conventions & component variants Component Parameters directory page parameters viewname Asset handling Services Named components Global components Ajax-Output Configuration Versioning License Changelog
    • By Robin S
      Page Reference Default Value
      Most ProcessWire core inputfield types that can be used with a Page Reference field support a "Default value" setting. This module extends support for default values to the following core inputfield types:
      Page List Select Page List Select Multiple Page Autocomplete (single and multiple) Seeing as these inputfield types only support the selection of pages a Page List Select / Page List Select Multiple is used for defining the default value instead of the Text / Textarea field used by the core for other inputfield types. This makes defining a default value a bit more user-friendly.
      Note that as per the core "Default value" setting, the Page Reference field must be set to "required" in order for the default value to be used.
      Screenshot

       
      https://github.com/Toutouwai/PageReferenceDefaultValue
      https://modules.processwire.com/modules/page-reference-default-value/
×
×
  • Create New...