Jump to content
Soma

MarkupSimpleNavigation

Recommended Posts

Hey everybody,

this is my first post here and I hope I'm not too stupid. ;)

My site structure looks like this:

Home

About us

Location
Opening Hours
Concept

Contact

and so on...

My problem is the following one: My child-pages are only shown on mouse-over. The "About us" page should not be a clickable page, but only a none-clickable placeholder. Is this possible with this plugin?

Thx and greets...

Share this post


Link to post
Share on other sites

Welcome DV-JF

Don't worry, you're not alone ;)

What are you using to make the menu hovers/dropdown? Bootstrap?

1. No, there no option to have placeholders.

2. You could do that with JScript (prevent click etc)

I'm playing with implementing some placeholder template option. Still have to figure out the details.

But since I don't really need it and am cautious to not add too many options, this could take a while.

  • Like 1

Share this post


Link to post
Share on other sites

What are you using to make the menu hovers/dropdown? Bootstrap?

Just pure CSS with some CSS3 features like opacity and transition based on Boilerplate...

I'm playing with implementing some placeholder template option. Still have to figure out the details.

But since I don't really need it and am cautious to not add too many options, this could take a while.

No, problem for me... Thx for this great module, for a beginner like me it made things much easier :)

Greets Jens.

Share this post


Link to post
Share on other sites

Soma - off the top of my head you wouldn't want to do it with JS as you might only want particular drop downs to be non-click on the parent (confusing for the end-user I know, but I've seen it before!). I know it's not exactly best practise to mix and match what can and can't be clicked at the top-level of drop-downs, but people will want to be able to do it nontheless ;)

I guess one way to achieve this would be to add another field by default that's a simple tick-box that says something like "Simple Navigation Placeholder" or something that can appear on every page template by default, maybe in the Settings tab? That way it's a simple check for a tick in that box per-page when looping through the output.

If not, and we assume that there is just a module setting to make all top-level drop-downs be non-click then that could just be a simple check for that setting in the module config and loop through.

I've just realised what you mean with the JS as I'm typing this (d'oh) but I was still envisaging that behind the scenes Google could still see a URL to the top-level even if you're telling the browser for the end-user not to be able to click a top-level menu item, so I just wanted to suggest a few options you've likely already considered :D

  • Like 1

Share this post


Link to post
Share on other sites

Somebody help!!! Pete is being attacked by a furry animal!! :o :o :o

  • Like 5

Share this post


Link to post
Share on other sites
just fitchet skunk

It's reduced Martijn to incomprehensible sentences! :P

  • Like 1

Share this post


Link to post
Share on other sites

I thought about this for some time and think having option to have list of templates and the code it would spit out for those pages would be good.

"x_templates" => "folder|placeholder"

"x_item_tpl" => "<span %s>{title}</span>";

"x_item_current_tpl" => "<span %s>{title}</span>";

Share this post


Link to post
Share on other sites

Ok the while is over.

I just committed an update to 1.1.5 to support alternative markup for specified templates.

https://github.com/s...default-options

Added 3 new options:

"xtemplate" => "folder|placeholder", // specify one or more templates
"xitem_tpl" => "<span>{title}</span>", // default markup for page with this template
"xitem_current_tpl" => "<span>{title}</span>"
echo $nav->render(array(
   'max_levels'=>2,
   'selector'=>"limit=10",
   'xtemplates' => 'placeholder|folder'
));
  • Like 3

Share this post


Link to post
Share on other sites

On the current dev branch of PW, this module does appear to need to be installed before it works (contrary to docs).

Share this post


Link to post
Share on other sites

If you call it in template with $modules->get(..) ? It will get installed (if it's listed but not installed yet) . Would be very surprized if not.

Edit: I removed the part in the documentation as it is a general note about ProcessWire modules I think only could be confusing. I tried to rewrite it to mention more details and I screwed :D

  • Like 1

Share this post


Link to post
Share on other sites

I want to output the page->created date in my list, but I only get the timestamp. Is it possible to format the date somehow?

Share this post


Link to post
Share on other sites

You can go to PW's unofficial complementary documents for this http://php.net/manua...nction.date.php

:) thanks. But I don't know how to use php in item_tpl. Maybe I just shouldn't misuse MarkupSimpleNavigation for this


$moduleMarkupSimpleNavigation->render(array(
'selector' => "template=news-article, news_category={$newsCategory}",
'item_tpl' => '<div class="news-header"><h3 class="news-headline">{title}</h3><span class="news-date">{created}</span></div><div class="news-body">{body}</div>'), null, $page);

It works! I modified the module and added these 2 line @line 203 to output my date:


else if ($match[1] === 'created' || $match[1] === 'modified' ) {
$field_value =  date('d.m.Y', $f);
}

And now I am gonna revert these changes and stop abusing this module for my purpose. :D

Share this post


Link to post
Share on other sites

No it's not possible currently as created and modified have no outputformatting. I'm not sure a fixed date format would be good, if like this the date format string would have to be another option or take it from somewhere. I'm not sure this is something many people need. One solution would be to add date_created field to template and then you would be able to format the date easily.

Share this post


Link to post
Share on other sites

I totally agree with you. A fixed date format wouldn't be of much use. Thats why I already reverted my changes. I didn't thought at using a real date field. But now I already solved it using my own foreach. I was simple enough.

I think I just wanted to play with your module. It's a great module btw. Thanks for building it, Soma.

Share this post


Link to post
Share on other sites

If you call it in template with $modules->get(..) ? It will get installed (if it's listed but not installed yet) . Would be very surprized if not.

It seemed to, first time I tried. Having said that, I have since uninstalled through admin and called it again through front end, and it installed itself as expected. Might have been something odd I did...

Share this post


Link to post
Share on other sites

Thanks for that great module, Soma!

This makes it much easier to generate all kind of navigation without having to digg through code for hours.

Just one question:

Does the module still support the costum selectors you mentioned below?

I am trying to hide the children of a specific template, doing it for now by replacing an parameter of the options array as follows:

if ($page->template == news | $page->template == news_article) $options[max_levels] = 1;

That works fine, but would be nicer to use those costum selectors. Are they still supported? Couldn't make it work for the example above...

Share this post


Link to post
Share on other sites

Hello again...

I added some code to the 'item_active_tpl' - but somehow this is not recognized and the output for the active items does not change.

In this case it's the url segment for a multilanguage site:

'item_active_tpl' => '<a href="{url}'.$segment.'">{title}</a>', // template string for the active inner items.

Has anybody else encountered that problem or could someone maybe try to reproduce it?

I am using the latest dev branch version of PW - but i cannot say if the problem is version related, as i did not tried this in an earlier version of PW.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Thanks, Soma! Works fine now - and as i see you already changed the documentation to 'item_current_tpl' and 'xitem_current_tpl'.

Interesting nobody recognized it by now.

Well, i guess there are not soooo many reasons to use the inner templates - most people will use CSS to change the active element which is added through 'current_class' - but for the multilanguage navigation it does a great job now to add the url segment for the active item.

Thanks for your help and for that great module!

Share this post


Link to post
Share on other sites

Hi all, I'm a total beginner to things like this. I understand creating fields, but not much else.

I'm trying to install this module to the template using Ryan's planet walkthrough. 

I've inserted 

$treeMenu = $modules->get("MarkupSimpleNavigation"); // load the navigation module
echo $treeMenu->render(); // render default menu

Just to see what would happen and it just prints out. Where am I supposed to put this at if not in the body of my template file?

Thanks for everything, everyone.

Share this post


Link to post
Share on other sites

It's supposed to be in the template file where you want to output your navigation markup. Not sure I understand the question. Where else should it be?

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




    • By apeisa
      Update 31.7.2019: AdminBar is now maintained by @teppo. Modules directory entry has been updated, as well as the "grab the code" link below.
      ***
      Latest screencast: http://www.screencas...73-ab3ba1fea30c
      Grab the code: https://github.com/teppokoivula/AdminBar
      ***
      I put this Adminbar thingy (from here: http://processwire.c...topic,50.0.html) to modules section and to it's own topic.
      I recorded quick and messy screencast (really, my first screencast ever) to show what I have made so far. You can see it from here: http://www.screencas...18-1bc0d49841b4
      When the modal goes off, I click on the "dark side". I make it so fast on screencast, so it might seem a little bit confusing. Current way is, that you can edit, go back to see the site (without saving anything), continue editing and save. After that you still have the edit window, but if you click "dark side" after saving, then the whole page will be reloaded and you see new edits live.
      I am not sure if that is best way: there are some strengths in this thinking, but it is probably better that after saving there shouldn't be a possibility to continue editing. It might confuse because then if you make edits, click on dark side -> *page refresh* -> You lose your edits.
      ***
      When I get my "starting module" from Ryan, I will turn this into real module. Now I had to make some little tweaks to ProcessPageEdit.module (to keep modal after form submits). These probably won't hurt anything:
      if($this->redirectUrl) $this->session->redirect($this->redirectUrl); if(!empty($_GET['modal'])) $this->session->redirect("./?id={$this->page->id}&modal=true"); // NEW LINE else $this->session->redirect("./?id={$this->page->id}");   and...
      if(!empty($_GET['modal'])) { $form->attr('action', './?id=' . $this->id . '&modal=true'); } else { $form->attr('action', './?id=' . $this->id); // OLD LINE }  
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.54
      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 nbcommunication
      I've spent the last while experimenting with srcset implementation - and PageimageSrcset is the result:
      PageimageSrcset
      Provides configurable srcset and sizes properties/methods for Pageimage.
      Overview
      The main purpose of this module is to make srcset implementation as simple as possible in your template code. It does not handle images rendered in CKEditor or similar fields.
      For an introduction to srcset and sizes, please read this Mozilla article about responsive images.
      Pageimage::srcset()
      // The property, which uses the set rules in the module configuration $srcset = $image->srcset; // A method call, using a set rules string // Delimiting with a newline (\n) would also work, but not as readable $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x"); // The same as above but using an indexed/sequential array $srcset = $image->srcset([ "320", "480", "640x480 768w", "1240", "2048 2x", ]); // The same as above but using an associative array // No rule checking is performed $srcset = $image->srcset([ "320w" => [320], "480w" => [480], "768w" => [640, 480], "1240w" => [1240], "2x" => [2048], ]); // Use the default set rules with portrait images generated for mobile/tablet devices $srcset = $image->srcset(true); // Return the srcset using all arguments $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x", [ "portrait" => "320, 640", ]); // The set rules above are a demonstration, not a recommendation! Image variations are only created for set rules which require a smaller image than the Pageimage itself. On large sites this may still result in a lot of images being generated. If you have limited storage, please use this module wisely.
      Portrait Mode
      In many situations, the ratio of the image does not need to change at different screen sizes. However, images that cover the entire viewport are an exception to this and are often the ones that benefit most from srcset implementation.
      The main problem with cover images is that they need to display landscape on desktop devices and portrait when this orientation is used on mobile and tablet devices.
      You can automatically generate portrait images by enabling portrait mode. It is recommended that you use this in combination with Pageimage::focus() so that the portrait variations retain the correct subject.
      The generated variations are HiDPI/Retina versions. Their height is determined by the portrait ratio (e.g. 9:16). Variations are always generated, regardless of whether the original image is smaller. Upscaling is disabled though, so you may find that some variations are actually smaller than they say they are in their filename.
      The sizes attribute should be used when portrait mode is enabled. Pageimage::sizes will return (orientation: portrait) and (max-width: {maxWidth}px) 50vw by default, which handles the use of these images for retina devices. The maximum width used in this rule is the largest set width.
      Pageimage::sizes()
      There is no option to configure default sizes because in most cases 100vw is all you need, and you do not need to output this anyway as it is inferred when using the srcset attribute. You can use the method for custom sizes though:
      // The property $sizes = $image->sizes; // Returns 100vw in most cases // Returns '(orientation: portrait) and (max-width: {maxWidth}px)50vw' if portrait mode enabled // A method call, using a mixture of integer widths and media query rules // Integer widths are treated as a min-width media query rule $sizes = $image->sizes([ 480 => 50, "(orientation: portrait) and (max-width: 640px)" => 100, 960 => 25, ]); // (min-width: 480px) 50vw, (orientation: portrait) and (max-width: 640px) 100vw, (min-width: 960px) 25vw // Determine widths by UIkit 'child-width' classes $sizes = $image->sizes([ "uk-child-width-1-2@s", "uk-child-width-1-3@l", ]); // (min-width: 640px) 50vw, (min-width: 1200px) 33.33vw // Determine widths by UIkit 'width' classes $sizes = $image->sizes([ "uk-width-1-2@m", "uk-width-1-3@xl", ]); // (min-width: 960px) 50vw, (min-width: 1600px) 33.33vw // Return the portrait size rule $sizes = $image->sizes(true); // (orientation: portrait) and (max-width: {maxWidth}px) 50vw // The arguments above are a demonstration, not a recommendation! Pageimage::render()
      This module extends the options available to this method with:
      srcset: When the module is installed, this will always be added, unless set to false. Any values in the formats described above can be passed. sizes: Only used if specified. Any values in the formats described above can be passed. uk-img: If passed, as either true or as a valid uk-img value, then this attribute will be added. The srcset attribute will also become data-srcset. Please refer to the API Reference for more information about this method.
      // Render an image using the default set rules echo $image->render(); // <img src='image.jpg' alt='' srcset='{default set rules}'> // Render an image using custom set rules echo $image->render(["srcset" => "480, 1240x640"]); // <img src='image.jpg' alt='' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w'> // Render an image using custom set rules and sizes // Also use the `markup` argument echo $image->render("<img class='image' src='{url}' alt='Image'>", [ "srcset" => "480, 1240", "sizes" => [1240 => 50], ]); // <img class='image' src='image.jpg' alt='Image' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 1240px) 50vw'> // Render an image using custom set rules and sizes // Enable uk-img echo $image->render([ "srcset" => "480, 1240", "sizes" => ["uk-child-width-1-2@m"], "uk-img" => true, ]); // <img src='image.jpg' alt='' data-uk-img data-srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 960px) 50vw'> // Render an image using portrait mode // Default rule sets used: 320, 640, 768, 1024, 1366, 1600 // Portrait widths used: 320, 640, 768 // Original image is 1000px wide // Not possible to use portrait mode and custom sets or portrait widths in render() // Sizes attribute automatically added echo $image->render(["srcset" => true]); // <img src='image.jpg' alt='' srcset='image.320x569-srcset-hidpi.jpg 320w, image.640x1138-srcset-hidpi.jpg 640w, image.768x1365-srcset-hidpi.jpg 768w, image.jpg 1024w' sizes='(orientation: portrait) and (max-width: 768px) 50vw'> Configuration
      To configure this module, go to Modules > Configure > PageimageSrcset.
      Set Rules
      These are the default set rules that will be used when none are specified, e.g. when calling the property: $image->srcset.
      Each set rule should be entered on a new line, in the format {width}x{height} {inherentwidth}w|{resolution}x.
      Not all arguments are required - you will probably find that specifying the width is sufficient for most cases. Here's a few examples of valid set rules and the sets they generate:
      Set Rule Set Generated Arguments Used 320 image.320x0-srcset.jpg 320w {width} 480x540 image.480x540-srcset.jpg 480w {width}x{height} 640x480 768w image.640x480-srcset.jpg 768w {width}x{height} {inherentwidth}w 2048 2x image.2048x0-srcset.jpg 2x {width} {resolution}x How you configure your rules is dependent on the needs of the site you are developing; there are no prescriptive rules that will meet the needs of most situations. This article gives a good overview of some of the things to consider.
      When you save your rules, a preview of the sets generated and an equivalent method call will be displayed to the right. Invalid rules will not be used, and you will be notified of this.
      Portrait Mode
      Set Widths
      A comma limited list of widths to create HiDPI/Retina portrait variations for.
      Crop Ratio
      The portrait ratio that should be used to crop the image. The default of 9:16 should be fine for most circumstances as this is the standard portrait ratio of most devices. However, you can specify something different if you want. If you add a landscape ratio, it will be switched to portrait when used.
      Any crops in the set rules ({width}x{height}) are ignored for portrait mode variations as this ratio is used instead.
      UIkit Widths
      If your website theme uses UIkit, you can pass an array of UIkit width classes to Pageimage::sizes to be converted to sizes. The values stored here are used to do this. If you have customised the breakpoints on your theme, you should also customise them here.
      Please note that only 1- widths are evaluated by Pageimage::sizes, e.g. uk-width-2-3 will not work.
      Remove Variations
      If checked, the image variations generated by this module are cleared on Submit. On large sites, this may take a while. It makes sense to run this after you have made changes to the set rules.
      Image Suffix
      You will see this field when Remove Variations is checked. The value is appended to the name of the images generated by this module and is used to identify variations. You should not encounter any issues with the default suffix, but if you find that it conflicts with any other functionality on your site, you can set a custom suffix instead.
      Debug Mode
      When this is enabled, a range of information is logged to pageimage-srcset.
      PageimageSrcsetDebug.js is also added to the <head> of your HTML pages. This will console.log a range of information about the images and nodes using srcset on your page after a window.onresize event is triggered. This can assist you in debugging your implementation.
      The browser will always use the highest resolution image it has loaded or has cached. You may need to disable browser caching to determine whether your set rules are working, and it makes sense to work from a small screen size and up. If you do it the other way, the browser is going to continue to use the higher resolution image it loaded first.
      UIkit Features
      This module implements some additional features that are tailored towards UIkit being used as the front-end theme framework, but this is not required to use the module.
      Installation
      Download the zip file at Github or clone the repo into your site/modules directory. If you downloaded the zip file, extract it in your sites/modules directory. In your admin, go to Modules > Refresh, then Modules > New, then click on the Install button for this module. ProcessWire >= 3.0.123 is required to use this module.
×
×
  • Create New...