Jump to content
Soma

MarkupSimpleNavigation

Recommended Posts

@Soma I used a line of your code and some new code from Ryan and it works. Thank you very much indeed again for your help.

Share this post


Link to post
Share on other sites

@Soma; THANK you for your nav module, just used it again — brilliant.

  • Like 1

Share this post


Link to post
Share on other sites

Hey alan, thanks! Glad you like it. :)

Share this post


Link to post
Share on other sites

Okay, so I'm different. Usually, people want to exclude stuff from an automagically generated navigation – I would like to add stuff. :)

Let's see if I can explain this: I have a primary navigation which this module is just perfect for. But the site also has a secondary navigation in the footer, so there should be an item in the primary nav which skips to said secondary nav in the footer. So basically, I would have to append an item to the nav generated by the module, technically another list item containing a link to an anchor on the same page.

Conveniently, this "skip to service nav" item would be the last item of the primary navigation, so I came up with this:

'outer_tpl' => '<ul class="clearfix">||<li><a id="skip-to-service" href="#service">Service</a></li></ul>'

which works fine unless I'm on a page which has children (<li class="current has_children">). In that case, outer_tpl is "reset" to '<ul class="clearfix">||</ul>' or something, at least the "appended" list item is not rendered.

Not being a PHP coder myself, I can't figure out if this is intended behaviour of the module or maybe a bug. (Although I'm aware I might be misusing 'outer_tpl' here.) I also thought about different approaches to realize that kind of nav item, maybe by using a "dummy page" or something, but I can't figure out how to do that. (Suggestions welcome, of course.)

  • Like 2

Share this post


Link to post
Share on other sites

Yeah it's a bug, thanks for finding it. Should be fixed in the last commit. Let me know if it works for you too.

Share this post


Link to post
Share on other sites

Soma: I have used your module in one project and I like it very much. Have worked without any worries. But now I have navigation scenario that I am not sure if it is possible with MarkupSimpleNavigation or should I code snippet for this.

Default view works like this (normal two levels deep):

LEVEL1 Page a

---LEVEL2 Page aa

---LEVEL2 Page ab

---LEVEL2 Page ac

LEVEL1 Page b

---LEVEL2 Page ba

---LEVEL2 Page bc

LEVEL1 Page c

---LEVEL2 Page ca

But when I go to level2, it should collapse that page and show level3 pages there, but not from other branches. Like this:

LEVEL1 Page a

---LEVEL2 Page aa

---LEVEL2 Page ab

------LEVEL3 Page aba

------LEVEL3 Page abb

---LEVEL2 Page ac

LEVEL1 Page b

---LEVEL2 Page ba

---LEVEL2 Page bc

LEVEL1 Page c

---LEVEL2 Page ca

Is this something that is possible with just settings?

Share this post


Link to post
Share on other sites

No its not possible. Kinda very special case.

Well u could try making it max levels 3 and hide third level with css and open on click.

  • Like 1

Share this post


Link to post
Share on other sites

True, should be possible with css. I'll go that route for now, thanks!

Share this post


Link to post
Share on other sites

Hi Soma, I just downloaded and installed this on a new site, and there's a weird problem:

I have pages like:

Home

About Us

More About Us

Even More About Us

Donate Online

Contact Us

If I click on "More About Us" above, the page loads fine. But, if I click on "About Us" from the "More About Us" page, I get a 404 Page Not Found error. The menu has prepended "/home/" to the URL instead of "/about-us/". So if I try to go to "Even More About Us," I also get a 404, because the URL is now "/home/even-more-about-us" instead of "/about-us/even-more-about-us"

Do you know what could cause this? I thought it might have to do with show_root but that wasn't it. Thanks!

Share this post


Link to post
Share on other sites

Marc can you show a little more of what you're doing exactly? I can't think of anything that would produce this, so far it works without known problems.

Share this post


Link to post
Share on other sites

One problem I noticed while using (and really enjoying!) this module. If I have this kind of structure:

/news/ (tpl: news)
  /pw3-released/ (tpl: news-item)
  /ryan-looking-for-drupal-work/ (tpl: news-item)
  /soma-takes-over-pw-project/ (tpl: news-item)

And all those pages use Simple Navigation with these options:

$options = array(
   'collapsed' => true,
   'selector' => 'template!=news-item'
   );

When looking one of the news-item pages it will render the navigation just fine (excluding the news-items, but showing the "/news/" page. But what is missing is the "parent" class from the news page in nav list. Not sure if that is intended or something that is difficult to fix, but it is frustrating to lose css class there. We are still under the news-page.

  • Like 1

Share this post


Link to post
Share on other sites

Well it gets kinda complex, and my guess is since there's no childs output it doesn't get added.

I'm not sure how easy it will be to add it.

Share this post


Link to post
Share on other sites

I just pushed an update and is now to 1.1.2. It was easier than first thought.

Thanks apeisa for finding it.

  • Like 2

Share this post


Link to post
Share on other sites

Soma, I use this all the time, because it's such a timesaver. Just stopping by to say thanks!

  • Like 2

Share this post


Link to post
Share on other sites

Thanks, that's kind of you arjen. Glad it's well recognized and helpful. :)

  • Like 1

Share this post


Link to post
Share on other sites

Hi again Soma, thanks so much for this module which saves me loads of time.

Do you have any tips for using it with a select/option menu for mobile. I can't seem to get it to display correctly.

Thanks!

Share this post


Link to post
Share on other sites

maybe:

   $options = array(
 'has_children_class' => '',
 'levels' => false,
 'max_levels' => 2,
 'show_root' => true,
 'outer_tpl' => '<select id="select_mobile">||</select>',
 'inner_tpl' => '<optgroup label="¬">||</optgroup>',
 'list_tpl' => '||',
 'item_tpl' => '<option value="{url}">{title}</option>',
 'item_current_tpl' => '<option value="{url}" selected="selected">{title}</option>'
   );
  • Like 3

Share this post


Link to post
Share on other sites

Not sure what you're about.

But this should give a select menu dropdown

$treeMenu = $modules->get("MarkupSimpleNavigation");
echo $treeMenu->render( array(
   'collapsed' => true,
   'max_levels' => 1,
   'outer_tpl' => "<select>||</select>",
   'list_tpl' => "||",
   'item_tpl' => "<option value='{url}'>{title}</option>"
 )
);
  • Like 1

Share this post


Link to post
Share on other sites

Soma and Martijn, thank you both, I have no idea why but I hadn't seen your replies until now, I apologize.

I ended up using a slightly adapted version as you'd need the "onchange" part of the select:

<select id="mobile_menu" class="visible-phone flr" onchange="location = this.options[this.selectedIndex].value;">
     <?php
     $mobile_nav = $modules->get("MarkupSimpleNavigation");
$options = array(
        'has_children_class' => '',
        'levels' => false,
        'max_levels' => 2,
        'show_root' => true,
        'selector' => 'template!=blog_entry|gallery|category|partner|portfolio_entry|event|testimonial|project_skill',
        'inner_tpl' => '<optgroup label="¬">||</optgroup>',
        'list_tpl' => '||',
        'item_tpl' => '<option value="{url}">{title}</option>',
        'item_current_tpl' => '<option value="{url}" selected="selected">{title}</option>'
       );
echo $mobile_nav->render($options); ?>
     </select>

Thanks again!

Share this post


Link to post
Share on other sites

onchange part if you have jQuery:

If you have jQuery loaded, this example look nicer I think. ( although your inline js is quicker )

// check if input select exists & stick the onchange part to it
if($("#mobile_menu").size() > 0) {
   $("#mobile_menu").change(function() {
    window.location = $(this).find("option:selected").val();
   });
}
  • Like 1

Share this post


Link to post
Share on other sites

The input select menu is used on mobile most likely. To turn off js there is just a little harder then on normal desktop environment. So most people don't tough the js setting at all.

A solution with a button: wrapping a submit button in a <noscript> tag. Then if javascript is turned off you will see the submit button. ( never done this, but probably work )

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