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 adrian
      Tracy Debugger for ProcessWire
      The ultimate “swiss army knife” debugging and development tool for the ProcessWire CMF/CMS

       
      Integrates and extends Nette's Tracy debugging tool and adds 35+ custom tools designed for effective ProcessWire debugging and lightning fast development
      The most comprehensive set of instructions and examples is available at: https://adrianbj.github.io/TracyDebugger
      Modules Directory: http://modules.processwire.com/modules/tracy-debugger/
      Github: https://github.com/adrianbj/TracyDebugger
      A big thanks to @tpr for introducing me to Tracy and for the idea for this module and for significant feedback, testing, and feature suggestions.
    • By adrian
      This module allows you to automatically rename file (including image) uploads according to a configurable format
      This module lets you define as many rules as you need to determine how uploaded files will be named and you can have different rules for different pages, templates, fields, and file extensions, or one rule for all uploads. Renaming works for files uploaded via the admin interface and also via the API, including images added from remote URLs.   Github: https://github.com/adrianbj/CustomUploadNames
      Modules Directory: http://modules.processwire.com/modules/process-custom-upload-names/
      Renaming Rules
      The module config allows you to set an unlimited number of Rename Rules. You can define rules to specific fields, templates, pages, and file extensions. If a rule option is left blank, the rule with be applied to all fields/templates/pages/extensions. Leave Filename Format blank to prevent renaming for a specific field/template/page combo, overriding a more general rule. Rules are processed in order, so put more specific rules before more general ones. You can drag to change the order of rules as needed. The following variables can be used in the filename format: $page, $template, $field, and $file. For some of these (eg. $field->description), if they haven't been filled out and saved prior to uploading the image, renaming won't occur on upload, but will happen on page save (could be an issue if image has already been inserted into RTE/HTML field before page save). Some examples: $page->title mysite-{$template->name}-images $field->label $file->description {$page->name}-{$file->filesize}-kb prefix-[Y-m-d_H-i-s]-suffix (anything inside square brackets is is considered to be a PHP date format for the current date/time) randstring[n] (where n is the number of characters you want in the string) ### (custom number mask, eg. 001 if more than one image with same name on a page. This is an enhanced version of the automatic addition of numbers if required) If 'Rename on Save' is checked files will be renamed again each time a page is saved (admin or front-end via API). WARNING: this setting will break any direct links to the old filename, which is particularly relevant for images inserted into RTE/HTML fields. The Filename Format can be defined using plain text and PW $page variable, for example: mysite-{$page->path} You can preserve the uploaded filename for certain rules. This will allow you to set a general renaming rule for your entire site, but then add a rule for a specific page/template/field that does not rename the uploaded file. Just simply build the rule, but leave the Filename Format field empty. You can specify an optional character limit (to nearest whole word) for the length of the filename - useful if you are using $page->path, $path->name etc and have very long page names - eg. news articles, publication titles etc. NOTE - if you are using ProcessWire's webp features, be sure to use the useSrcExt because if you have jpg and png files on the same page and your rename rules result in the same name, you need to maintain the src extension so they are kept as separate files.
      $config->webpOptions = array(     'useSrcExt' => false, // Use source file extension in webp filename? (file.jpg.webp rather than file.webp) ); Acknowledgments
      The module config settings make use of code from Pete's EmailToPage module and the renaming function is based on this code from Ryan: http://processwire.com/talk/topic/3299-ability-to-define-convention-for-image-and-file-upload-names/?p=32623 (also see this post for his thoughts on file renaming and why it is the lazy way out - worth a read before deciding to use this module). 
       
       
      NOTE:
      This should not be needed on most sites, but I work with lots of sites that host PDFs and photos/vectors that are available for download and I have always renamed the files on upload because clients will often upload files with horrible meaningless filenames like:
      Final ReportV6 web version for John Feb 23.PDF

    • 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! :)
×
×
  • Create New...