Jump to content
Soma

MarkupSimpleNavigation

Recommended Posts

Thanks guys, I really think it should be CSS, it was just I was having a hard time handling a select/option nav for some reason

Home

About

-- About This

-- About That

Blog

Work

-- This Work

-- That Work

Contact

Am sure I'll end up with it in CSS, was just wondering if there was an added class.

Share this post


Link to post
Share on other sites

I still have no idea what you want to target and how you imagine doing it... So I can't help.

I know what a child of a parent is, but it's not something I can get a hand on in a navigation, it's nothing specific or I just don't get it. :)

Maybe this is something you can use:

"list_field_class" => {template} p_{id}

or 

"list_field_class" => p_{name}

Share this post


Link to post
Share on other sites

Just wanted to let you all know, I updated the module to 1.1.9 , with another new hook method to manipulate or add your very special case classes that will get added to list_tpl's "%s". 

To use this, here a little example to make it clearer. I want to add a class to my page with id 1001. Ok here we go.

$nav = $modules->get("MarkupSimpleNavigation");

function hookGetListClass(HookEvent $event){
    $child = $event->arguments('page'); // current rendered page item (in naviation)
    $class = $event->arguments('class'); // the class string, may be empty or filled
    if($child->id == 1001){ // add your checks, use API or whatever... daytime...
        $event->return .= " yourclass"; // add your class names
    }
}

$nav->addHookAfter('getListClass', null, 'hookGetListClass');
echo $nav->render();

Added this to readme

  • Like 5

Share this post


Link to post
Share on other sites

Hi Soma,

first of all, thanks for this great module!

I get the following message displayed:

Notice: Undefined offset: 1 in C:\[...]\site\modules\MarkupSimpleNavigation.module on line 217
 

and this is one of my calls:

            <?php    
            $treeMenu = $modules->get("MarkupSimpleNavigation"); // load the module
            $rootPage = $page->parents->count == 1 ? $page : $page->parent;
            $options = array(
            'parent_class' => 'active',
            'current_class' => 'active',
            'max_levels' => 1,
            'outer_tpl' => ''
            );
            echo $treeMenu->render($options, null, $rootPage);
            ?>
 

any ideas what might cause this, or can I ignore the message?

cheers, j

Share this post


Link to post
Share on other sites

If you leave outer tpl empty you should still specify the "||" .. 'outer_tpl' => '||'

  • Like 1

Share this post


Link to post
Share on other sites

If you leave outer tpl empty you should still specify the "||" .. 'outer_tpl' => '||'

Ka-Chiiing! :) thanks Soma

Share this post


Link to post
Share on other sites

Hi!

I'm stuck again %)

I have structure something like that:

-Red

--Circle

--Square

-Blue

--Circle

--Triangle

...

I need to output "#parent-children" anchors (#red-circle, #red-square).

Is it possible to output parent name? I've tried {parent},but this is url to parent.

Or I need the Captain Hook to help?

Share this post


Link to post
Share on other sites

@k

Hi!

I'm stuck again %)

I have structure something like that:

-Red

--Circle

--Square

-Blue

--Circle

--Triangle

...

I need to output "#parent-children" anchors (#red-circle, #red-square).

Is it possible to output parent name? I've tried {parent},but this is url to parent.

Or I need the Captain Hook to help?

Without knowing further details/context, why not just build your own menu?

It can be as simple as

$menu = "<ul>";
foreach($pages->get("/sompath/")->children as $child) {
    $menu .= "<li><a href='#'>$child->title</a>";
    if($child->numChildren) {
        $menu .= "<ul>";
        foreach($child->children as $subchild) {
            $menu .= "<li><a href='#{$child->name}-{$subchild->name}'>$subchild->title</a></li>";
        }
        $menu .= "</ul>";
    }
    $menu .= "</li>";
}
$menu .= "</ul>";

echo $menu;

If you still want to go the module way, yes there you could make a hook to archive what you want. There's a couple examples in this thread, but there can't be enough I guess ;)

function hookTagsString($event){
    $child = $event->arguments("page");
    if($child->template == "form"){ // some check for template? as you like
        // now return your own link markup with $event->return
        $event->return = "<a href='#{$child->parent->name}-{$child->name}'>-$child->title</a>";
    }
}
$nav->addHookAfter("getTagsString", null,'hookTagsString');

// render the navigation
echo $nav->render(null, null, $pages->get("/somepath/"));
  • Like 1

Share this post


Link to post
Share on other sites

@k

It can be as simple as

Domo arigato, Master Ninja!

Share this post


Link to post
Share on other sites

only output submenu of active (current) menu item

In modX, we had the "&hideSubMenus" parameter.

How could I achieve something similar with this module, without the use of css of JS?

Share this post


Link to post
Share on other sites

In peocesswire we have the collapsed option. :-)

Share this post


Link to post
Share on other sites

A little tip for anyone wanting a drop-down arrow on submenu parents, like after 'About' below -

post-378-0-92208700-1372857353_thumb.png

just add something like this to your CSS.

li.has_children > a:after {
    content: "▼";
    font-size: 70%;
    padding-left: .5em;
    vertical-align: middle;
}
  • Like 5

Share this post


Link to post
Share on other sites

If I only want to show the top-level items, what would be the correct options?

I tried 

'max_levels' => 1,
'levels' => false,
'collapsed' => true, 

but I still get all items. Is this module "overkill" if I only want to list topmost pages? Should I be better just using a simple selector and foreach, to output such a simple nav-list?

Share this post


Link to post
Share on other sites

Well the correct option is, you're right:

$nav->render(array("max_levels" => 1));

"levels" area already false and only for classes. If you output only 1 level you don't need "collapsed" true.

Not sure what you mean with you get all items.

Share this post


Link to post
Share on other sites

Well, every single page is being rendered as list / link, not just the top most hierarchy.

Share this post


Link to post
Share on other sites

Only with the default options it will render all levels. max_levels is there to limit this to as many levels as you like/need.

Share this post


Link to post
Share on other sites

OK, I'll try to rephrase it.

I have this in leftnav.inc:

$leftNav = $modules->get("MarkupSimpleNavigation");

$leftNavOptions = array(
    'max_levels' => 3,
    'collapsed' => true, // I guess this is the param that's not being executed correctly atm...
    'show_root' => false
);

echo $leftNav->render($leftNavOptions);

For simplicity's sake, let's say I have this basic 08-15 site structure:

- Company

- Products

- Downloads / Manuals

- News

Each of these main sections has sub-sections: max. 2 levels down.

Now, no matter if I'm at the root page of "products", or in a detail-page within products, the menu always outputs the entire tree. Like a sitemap, everything from A to Z. But that's not what I want. Shouldn't "collapsed = false" take care of that?

The idea is to have a basic HTML list that only displays the top-level hierarchy as links. But when I'm further down in level 1-2-3, it should recognize this... "ah, that's my home category, let's open up this navigation tree as well to show where we live".

Right now, all levels / sections are open all the time, at all levels, everywhere. "Collapsed" parameter true or false: doesn't change anything.

So e.g. if I'm visiting a product page (= 1 level down inside "products"), it should only render: 

- Company

- Products

  -- product A

  -- product B (= active)

  -- product C

- Downloads / Manuals

- News

But what the module actually does, is showing every single page, no matter how far up or down you currently are. Surely that was not the intention of the module?

So either I'm completely misunderstanding how this module is supposed to work, or it's some kind of bug. I'm sure I could visually hide the superflous elements via CSS, but I'd rather have the module not render them in the first place...

in a nutshell:

a) show only top-level links

+ b) but also show (nested) sub-levels if I am in inside this parent category, right down to the child (or grand-child document).

Share this post


Link to post
Share on other sites

Yes that's correct 'collapsed' does collapse all to the top level, except for those you'r on or in. It's only opening branches you're on.

'max_levels' does limit the levels rendered from the top level. 

So you example kinda illustrates this correct.

 Company

- Products

  -- product A

  -- product B (= active)

  -- product C

- Downloads / Manuals

- News

 

Also this 

 

 Company

- Products (= active)

  -- product A

  -- product B 

  -- product C

- Downloads / Manuals

- News

 

Or like this

 

 Company

- Products 

  -- product A

  -- product B 

  -- product C (= active)

     -- product C1

     -- product C2 

- Downloads / Manuals

- News

 

I don't know why it's not working for you, but I use it all the time, and I think quite a lot of others too.

Share this post


Link to post
Share on other sites

Quite possible. The devil is always in the details. Thanks for your clarifications though. Will try again today with more caffeine :-)

Share this post


Link to post
Share on other sites

Actually, I'm beginning to believe it's a server issue. On another site / server it's working perfectly.

Could a multilingual site setup be a potential error source? (I wouldn't know why that would be the case, everything looks perfectly OK - just clutching at straws here...)

Share this post


Link to post
Share on other sites

If all else fails, I would strip my PW install down to the bare minimals (uninstall non-core modules; minus MSN of course ;)) or test in a vanilla PW install with only core modules and MSN installed and test from there to see if it works. Yeah, it is also good to test in different environments.

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 Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.56
      Composer: rockett/jumplinks
      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 BitPoet
      As threatened in Ryan's announcement for 3.0.139, I built a little module for sliding toggles as a replacement for checkboxes. Styling of the input is CSS3 only (with all the usual caveats about older browsers), no JS necessary, and may still be a bit "rough around the edges", so to speak, since I didn't have much time for testing on different devices or brushing things up enough so I'd feel comfortable pushing it to the module directory. But here's the link to the GitHub repo for now:
      InputfieldSlideToggle
      Fieldtype and Inputfield that implements smartphone-style toggles as replacement for checkbox inputs. The visualization is CSS-only, no additional JS necessary.
      Status
      Still very alpha, use with caution!
      Features / Field Settings
      Size
      You can render the toggles in four different sizes: small, medium, large and extra large.
      Off Color
      Currently, "unchecked" toggles can be displayed either in grey (default) or red.
      On Color
      "Checked" toggles can be rendered in one of these colors: blue (default), black, green, grey, orange or red.
      Screenshots

      Some examples with checkbox label


      View all Size and Color Combinations
      Small toggles Medium toggles Big toggles Extra big toggles  









    • By Orkun
      Hi Guys
      I needed to add extended functionalities for the InputfieldDatetime Module (module is from processwire version 2.7.3) because of a Request of Customer.
      So I duplicated the module and placed it under /site/modules/.
      I have added 3 new Settings to the InputfieldDatetime Module.
      1. Day Restriction - Restrict different days based on weekdays selection (e.g. saturday, sunday) - WORKING

       
      2. Time Slots - Define Time slots based on custom Integer Value (max is 60 for 1 hour) - WORKING

       
      3. Time Range Rules per Weekday - Define a minTime and MaxTime per Weekday (e.g. Opening Hours of a Restaurant) - NOT WORKING PROPERLY

       
      The Problem
      Time Slots and Day Restriction working fine so far. But the Time Range Rules per Weekday doesn't work right.
      What should happen is, that when you click on a date, it should update the minTime and maxTime of the Time Select.
      But the change on the select only happens if you select a date 2 times or when you select a date 1 time and then close the datepicker and reopen it again.
      The time select doesn't get change when you select a date 1 time and don't close the picker.
      Here is the whole extended InputfieldDatetime Module.
      The Files that I have changed:
      InputfieldDatetime.module InputfieldDatetime.js jquery-ui-timepicker-addon.js (https://trentrichardson.com/examples/timepicker/) - updated it to the newest version, because minTime and maxTime Option was only available in the new version  
      Thats the Part of the JS that is not working correctly:
      if(datetimerules && datetimerules.length){ options.onSelect = function(date, inst) { var day = $(this).datetimepicker("getDate").getDay(); day = day.toString(); var mintime = $(this).attr('data-weekday'+day+'-mintime'); var maxtime = $(this).attr('data-weekday'+day+'-maxtime'); console.log("weekday: "+day); console.log("minTime: "+mintime); console.log("maxTime: "+maxtime); var optionsAll = $(this).datetimepicker( "option", "all" ); optionsAll.minTime = mintime; optionsAll.maxTime = maxtime; $(this).datetimepicker('destroy'); $(this).datetimepicker(optionsAll); $(this).datetimepicker('refresh'); //$.datepicker._selectDate($(this).attr("id"),date); //$.datepicker._base_getDateDatepicker(); // var inst = $.datepicker._getInst($(this)); // $.datepicker._updateDatepicker(inst); /*$(this).datetimepicker('destroy'); InputfieldDatetimeDatepicker($(this), mintime, maxtime); $(this).datetimepicker('refresh'); */ // $(this).datetimepicker('option', {minTime: mintime, maxTime: maxtime}); } } Can you have a look and find out what the Problem is?
      InputfieldDatetime.zip
       
      Kind Regards
      Orkun
    • By teppo
      This module tracks changes, additions, removals etc. of public (as in "not under admin") pages of your site. Like it's name says, it doesn't attempt to be a version control system or anything like that - just a log of what's happened.
      At the moment it's still a work in progress and will most likely be a victim of many ruthless this-won't-work-let's-try-that-instead cycles, but I believe I've nailed basic functionality well enough to post it here.. so, once again, I'll be happy to hear any comments you folks can provide
      https://modules.processwire.com/modules/process-changelog/
      https://github.com/teppokoivula/ProcessChangelog
      How does it work?
      Exactly like it's (sort of) predecessor, Process Changelog actually consists of two modules: Process Changelog and Process Changelog Hooks. Hooks module exists only to serve main module by hooking into various functions within Pages class, collecting data of performed operations, refining it and keeping up a log of events in it's own custom database table (process_changelog.) Visible part is managed by Process Changelog, which provides users a (relatively) pretty view of the contents of said log table.
      How do you use it?
      When installed this module adds new page called Changelog under Admin > Setup which provides you with a table view of collected data and basic filtering tools See attached screenshots to get a general idea about what that page should look like after a while.
      For detailed installation instructions etc. see README.md.
       


    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      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)
       




×
×
  • Create New...