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

Sorry, saw just now that you can set the selectors in the options array - works great!

  • Like 1

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

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By bernhard
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
    • By MoritzLost
      Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:

      This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
      As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
×
×
  • Create New...