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
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 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 Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory (alpha version only available via GitHub) SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • 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 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...