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 eelkenet
      Hi! I've created a small Inputfield module called InputfieldFloatRange which allows you to use an HTML5 <input type="range" ../> slider as an InputField. I needed something like this for a project where the client needs to be able to tweak this value more based on 'a feeling' than just entering a boring old number. Maybe more people can use this so I'm hereby releasing it into the wild.  
       
      What is it?
      The missing range slider Inputfield for Processwire. 
      What does it do?
      This module extends InputfieldFloat and allows you to use HTML5 range sliders for number fields in your templates.
      It includes a visible and editable value field, to override/tweak the value if required.  
      Features
      Min/max values Precision (number of decimals) Steps (Read more) Manual override of the selected value (will still adhere to the rules above) Usage
      Clone / zip repo Install FieldtypeFloatRange, this automatically installs the Inputfield Create new field of type `Float (range)` or convert an existing `Float`, `Integer` or `Text` field. To render the field's value simply echo `$page->field` Demo
      A field with Min=0, Max=1, Step=0.2, Precision=2

      Field with settings Min=0, Max=200, Step=0.25, Precision=2

       
      Todo
      Make the display-field's size configurable (will use the Input Size field setting)  Hopefully become redundant If it's usable for others I'll add it to the Modules list  
      Changelog
      v002
      - Fix issue where setting the step value to an empty value created problem with validation
      - Make the display-field optional 
      v001
      - Initial release
       
      Thanks!
       
       
    • By Robin S
      Another little admin helper module...
      Template Field Widths
      Adds a "Field widths" field to Edit Template that allows you to quickly set the widths of inputfields in the template.

      Why?
      When setting up a new template or trying out different field layouts I find it a bit slow and tedious to have to open each field individually in a modal just to set the width. This module speeds up the process.
      Installation
      Install the Template Field Widths module.
      Config options
      You can set the default presentation of the "Field widths" field to collapsed or open. Field widths entered into the Template Field Widths inputfield are only applied if the Edit Template form is submitted with the Template Field Widths inputfield in an opened state. "Collapsed" is the recommended setting if you think you might also use core inputs for setting field widths in a template context. You can choose Name or Label as the primary identifier shown for the field. The unchosen alternative will become the title attribute shown on hover. You can choose to show the original field width next to the template context field width.  
      https://github.com/Toutouwai/TemplateFieldWidths
      https://modules.processwire.com/modules/template-field-widths/
    • 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

×
×
  • Create New...