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

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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      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 If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      Please have a look at the screenshots to get an idea what I'm talking about (open spoiler):
      (Please note: these screenshots are from an early development state of SnipWire. To see actual screens please have a look at later posts below!)
       
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! 🙂
    • By Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...