Jump to content
Soma

MarkupSimpleNavigation

Recommended Posts

I have a template file following Ryan's planet.php template starter demo. The structure is

processwire/site/templates/planet.php

Inside of planet.php, I have inserted the code you have provided. When I run that page, your code just prints out exactly as is. Nothing else happens.

Is that a little more clear?

Share this post


Link to post
Share on other sites

Ah you mean it shows the php code on the Website?

This is php code and you have to put it in <?php ... ?> to make it work. Sorry but this is so obvious that I didn't think of it.

Share this post


Link to post
Share on other sites

Hold onto it. You'll get there :)

Share this post


Link to post
Share on other sites

@thatigibbyguy I clearly remember being like you (no PHP) and I am still quite a PHP lite-weight.

Luckily by the time I came to PW I had some PHP behind me because it meant I mostly had to only focus on PW.

But all I can say is that I am SO glad I spent some time getting the basics of PHP because it's allowed me to use PW which I've found to be the best CMS I've ever used, no contest. And using it has lead to learn more PHP due to the excellent and helpful examples in this forum.

In case it helps, these two are resources that you'll either already know of or if not may be good places to get more PHP mojo: http://phpmaster.com/ and of course http://php.net/.

Good luck!

  • Like 2

Share this post


Link to post
Share on other sites

Thanks for sharing the excellent module & the hard work!

Kindly let me know if the following is possible:

Main Menu Item

   -- Sub Menu 1

   -- Sub Menu 2

Few of  the main menu items (on the site I am doing) has no page associated with it & opens the page for the first sub menu item. Please let me know how, if this is possible.

Thanks a lot in advance.

Share this post


Link to post
Share on other sites
Few of  the main menu items (on the site I am doing) has no page associated with it & opens the page for the first sub menu item. Please let me know how, if this is possible.

Thanks a lot in advance.

One solution I used:

Give your main menu items that should redirect to the firt sub menu a "redirect" template.

Then in your template, simply add this code:

$children = $page->children;
if (count($children)) {
  $session->redirect($children->first()->url);
} else {
  //This page has no children to redirect... throw a 404 or do other work
  throw new Wire404Exception();
}
  • Like 1

Share this post


Link to post
Share on other sites

You could also have a template "redirect" with only a title and a page field (single page) to select any page you want to go.

Then in the code you should be able to write

array('item_tpl' => '<a href="{redirect_page|url}">{title}</a>')

So it would take the url of the referenced page in the page field if found, or if not it takes the url of the page itself. Assuming the page field is named "redirect_page".

Haven't tried but should work.

EDIT: This wasn't really working until added support for page field url in version 1.1.8.

  • Like 1

Share this post


Link to post
Share on other sites

I am trying to use an additional code for the inner items, just for pages which have a specific value in one field.

E.g. if a page has a textfield "extra_title" which is not empty the inner items should have an extra code part <span class="nav_extra_title"><span> .

Has anybody an idea how this could be solved?

Share this post


Link to post
Share on other sites

It's not possible to do conditional markup generation. So you're maybe better off building you're menu with your own code. Which is quite simple.

Only workaround I see is using JS to generate it.


array('item_tpl' => '<a href="{url}" data-extratitle="{extra_title}">{title}</a>')

Then use jquery.

$('#menu a[data-extratitle!=""]').each(function(){
    $(this).prepend($("<span class='nav_extra_title'>"+$(this).data('extratitle')+"</span>"));
});
  • Like 2

Share this post


Link to post
Share on other sites

Thanks for the hint using the data attribute - i have to admit i never used it before...

In the template i am using:

array ('item_tpl' => '<a href="{url}"><span class="nav_extra_title" data-extratitle="{nav_extra_title}"><span>{nav_extra_title}</span></span>{title}</a>')

the jQuery i tried is:

$('span.nav_extra_title[data-extratitle=""]').each(function(){
	alert("hjgf");
    $(this).toggleClass("kjh");
});

The script is located in a file which is loaded in the head.inc - the alert works fine ;-) - but i don't know how to change the class "nav_extra_title" to another or maybe add a class to it. I tried so many variations but it does not work...

Share this post


Link to post
Share on other sites

If your doing the opposite you better just do this:



array ('item_tpl' => '<a href="{url}"><span class="nav_extra_title">{nav_extra_title}</span>{title}</a>')

Then use this to hide empty spans

$("#menu span:empty").remove();

I'm not sure, but most commonly you execute the script before dom even loaded. So if the script is like this in the header it will never work.

A technique is to execute it after dom load.

$(document).ready(function(){

   // your code
});

Or short method

$(function(){

    // your code
});

Otherwise I don't know.

  • Like 1

Share this post


Link to post
Share on other sites

Yes, i thought the same and tried it with $(document).ready(function() already - but it did not work... or to be honest, i just thought it wouldn't work...

I just inspected the source code with Safari and did not switch to the DOM tree or verified it in CSS Edit - at last both possibilities which are described above work fine!

Thanks for your help again, Soma!

Share this post


Link to post
Share on other sites

I changed my code above example: It's not needed to each them just:



$("#menu span:empty").remove();

Share this post


Link to post
Share on other sites

Hi Soma,

I've read through the entine thread and documentation and most things are clear. I've got one question though:

How would you add current-parent class to a parent?

For example: I am on /services/service-1/. The menu renders as following:

Home

--Services (this is the page I would like to add another class)

----Service 1 (current, which applies a current class)

----Service 2

--About

--Contact

Offcourse I can use jQuery to do this, but I was wondering if the mighty MarkupSimpleNavigation might be able to do this.

Thanks!

Share this post


Link to post
Share on other sites

Hi arjen,

the parent page will have the "has_children_class" and if it's the actual parent it will have the "parent_class", too.

So it can be styled with CSS through:

li.parent.has_children {
	color: #fff
}
  • Like 1

Share this post


Link to post
Share on other sites

Thanks doolak! Could use some more sleep this month.

Share this post


Link to post
Share on other sites

Thanks doolak! Could use some more sleep this month.

I know this too well...

  • Like 1

Share this post


Link to post
Share on other sites

I'm using this to get my navigation from a Projects page and below. It's perfect, looks exactly how I want it.

PW page tree:

- Home

-- Projects

--- Project type

---- Project

---- Project etc

Is there a way can I go about inserting a page from another part of the page tree at the top of the output?

Regards

Marty

Share this post


Link to post
Share on other sites

Marty,

I think you could set the outer tpl to an empty string and add the ul-tags and your page manually:

<?php
$customPage = $pages->get('/.../');
echo "<ul>";
echo "<li><a href='{$customPage->url}'>{$customPage->title}</a></li>"; //Add your entry above all others
echo $modules->get('MarkupSimpleNavigation')->render(array('outer_tpl' => ''));
echo "</ul>";

Not tested and just an idea, maybe Soma has a better solution :)

Cheers

Edit: Damn I need to get some sleep NOW :blink:

  • Like 1

Share this post


Link to post
Share on other sites

Of course! Not enough (or maybe too much) coffee and not enough active brain cells in circulation this morning.

Thanks Wanze!

Share this post


Link to post
Share on other sites

Another would be to hand the items to the outer_tpl.

$customPage = $pages->get('/.../');
$item = "<li><a href='{$customPage->url}'>{$customPage->title}</a></li>";
echo $modules->get('MarkupSimpleNavigation')->render(array('outer_tpl' => "<ul>$item||</ul>"));
 
  • Like 2

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 teppo
      Needed a really simple solution to embed audio files within page content and couldn't find a module for that, so here we go. Textformatter Audio Embed works a bit like Textformatter Video Embed, converting this:
      <p>https://www.domain.tld/path/to/file.mp3</p> Into this:
      <audio controls class="TextformatterAudioEmbed"> <source src="https://www.domain.tld/path/to/file.mp3" type="audio/mpeg"> </audio> The audio element has pretty good browser support, so quite often this should be enough to get things rolling 🙂
      GitHub repository: https://github.com/teppokoivula/TextformatterAudioEmbed Modules directory: https://modules.processwire.com/modules/textformatter-audio-embed/
    • By Richard Jedlička
      Tense    
      Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
      Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.

      See example or see usage in a real project.
      How to use?
      1. Install it: 
      composer global require uiii/tense 2. Create tense.yml config:
      tense init 3. Run it:
      tense run  
      For detailed instructions see Github page: https://github.com/uiii/tense
       
      This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
       
      What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
    • By Chris Bennett
      Hi all, I am going round and round in circles and would greatly appreciate if anyone can point me in the right direction.
      I am sure I am doing something dumb, or missing something I should know, but don't. Story of my life 😉

      Playing round with a module and my basic problem is I want to upload an image and also use InputfieldMarkup and other Inputfields.
      Going back and forth between trying an api generated page defining Fieldgroup, Template, Fields, Page and the InputfieldWrapper method.

      InputfieldWrapper method works great for all the markup stuff, but I just can't wrap my head around what I need to do to save the image to the database.
      Can generate a Field for it (thanks to the api investigations) but not sure what I need to do to link the Inputfield to that. Tried a lot of stuff from various threads, of varying dates without luck.
      Undoubtedly not helped by me not knowing enough.

      Defining Fieldgroup etc through the api seems nice and clean and works great for the images but I can't wrap my head around how/if I can add/append/hook the InputfieldWrapper/InputfieldMarkup stuff I'd like to include on that template as well. Not even sure if it should be where it is on ___install with the Fieldtype stuff or later on . Not getting Tracy errors, just nothing seems to happen.
      If anyone has any ideas or can point me in the right direction, that would be great because at the moment I am stumbling round in the dark.
       
      public function ___install() { parent::___install(); $page = $this->pages->get('name='.self::PAGE_NAME); if (!$page->id) { // Create fieldgroup, template, fields and page // Create new fieldgroup $fmFieldgroup = new Fieldgroup(); $fmFieldgroup->name = MODULE_NAME.'-fieldgroup'; $fmFieldgroup->add($this->fields->get('title')); // needed title field $fmFieldgroup->save(); // Create new template using the fieldgroup $fmTemplate = new Template(); $fmTemplate->name = MODULE_NAME; $fmTemplate->fieldgroup = $fmFieldgroup; $fmTemplate->noSettings = 1; $fmTemplate->noChildren = 1; $fmTemplate->allowNewPages = 0; $fmTemplate->tabContent = MODULE_NAME; $fmTemplate->noChangeTemplate = 1; $fmTemplate->setIcon(ICON); $fmTemplate->save(); // Favicon source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFavicon'; $fmField->label = 'Favicon'; $fmField->focusMode = 'off'; $fmField->gridMode = 'grid'; $fmField->extensions = 'svg png'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Favicon Silhouette source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFaviconSilhouette'; $fmField->label = 'SVG Silhouette'; $fmField->notes = 'When creating a silhouette/mask svg version for Safari Pinned Tabs and Windows Tiles, we recommend setting your viewbox for 0 0 16 16, as this is what Apple requires. In many cases, the easiest way to do this in something like illustrator is a sacrificial rectangle with no fill, and no stroke at 16 x 16. This forces the desired viewbox and can then be discarded easily using something as simple as notepad. Easy is good, especially when you get the result you want without a lot of hassle.'; $fmField->focusMode = 'off'; $fmField->extensions = 'svg'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Create: Open Settings Tab $tabOpener = new Field(); $tabOpener->type = new FieldtypeFieldsetTabOpen(); $tabOpener->name = 'fmTab1'; $tabOpener->label = "Favicon Settings"; $tabOpener->collapsed = Inputfield::collapsedNever; $tabOpener->addTag(MODULE_NAME); $tabOpener->save(); // Create: Close Settings Tab $tabCloser = new Field(); $tabCloser->type = new FieldtypeFieldsetClose; $tabCloser->name = 'fmTab1' . FieldtypeFieldsetTabOpen::fieldsetCloseIdentifier; $tabCloser->label = "Close open tab"; $tabCloser->addTag(MODULE_NAME); $tabCloser->save(); // Create: Opens wrapper for Favicon Folder Name $filesOpener = new Field(); $filesOpener->type = new FieldtypeFieldsetOpen(); $filesOpener->name = 'fmOpenFolderName'; $filesOpener->label = 'Wrap Folder Name'; $filesOpener->class = 'inline'; $filesOpener->collapsed = Inputfield::collapsedNever; $filesOpener->addTag(MODULE_NAME); $filesOpener->save(); // Create: Close wrapper for Favicon Folder Name $filesCloser = new Field(); $filesCloser->type = new FieldtypeFieldsetClose(); $filesCloser->name = 'fmOpenFolderName' . FieldtypeFieldsetOpen::fieldsetCloseIdentifier; $filesCloser->label = "Close open fieldset"; $filesCloser->addTag(MODULE_NAME); $filesCloser->save(); // Create Favicon Folder Name $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeText"); $fmField->name = 'folderName'; $fmField->label = 'Favicon Folder:'; $fmField->description = $this->config->urls->files; $fmField->placeholder = 'Destination Folder for your generated favicons, webmanifest and browserconfig'; $fmField->columnWidth = 100; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon('folder'); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($tabOpener); $fmFieldgroup->add($filesOpener); $fmFieldgroup->add($fmField); $fmFieldgroup->add($filesCloser); $fmFieldgroup->add($tabCloser); $fmFieldgroup->save(); /////////////////////////////////////////////////////////////// // Experimental Markup Tests $wrapperFaviconMagic = new InputfieldWrapper(); $wrapperFaviconMagic->attr('id','faviconMagicWrapper'); $wrapperFaviconMagic->attr('title',$this->_('Favicon Magic')); // field show info what $field = $this->modules->get('InputfieldMarkup'); $field->name = 'use'; $field->label = __('How do I use it?'); $field->collapsed = Inputfield::collapsedNever; $field->icon('info'); $field->attr('value', 'Does this even begin to vaguely work?'); $field->columnWidth = 50; $wrapperFaviconMagic->add($field); $fmTemplate->fields->add($wrapperFaviconMagic); $fmTemplate->fields->save(); ///////////////////////////////////////////////////////////// // Create page $page = $this->wire( new Page() ); $page->template = MODULE_NAME; $page->parent = $this->wire('pages')->get('/'); $page->addStatus(Page::statusHidden); $page->title = 'Favicons'; $page->name = self::PAGE_NAME; $page->process = $this; $page->save(); } }  
    • By Sebi
      Since it's featured in ProcessWire Weekly #310, now is the time to make it official:
      Here is Twack!
      I really like the following introduction from ProcessWire Weekly, so I hope it is ok if I use it here, too. Look at the project's README for more details!
      Twack is a new — or rather newish — third party module for ProcessWire that provides support for reusable components in an Angular-inspired way. Twack is implemented as an installable module, and a collection of helper and base classes. Key concepts introduced by this module are:
      Components, which have separate views and controllers. Views are simple PHP files that handle the output for the component, whereas controllers extend the TwackComponent base class and provide additional data handling capabilities. Services, which are singletons that provide a shared service where components can request data. The README for Twack uses a NewsService, which returns data related to news items, as an example of a service. Twack components are designed for reusability and encapsulating a set of features for easy maintainability, can handle hierarchical or recursive use (child components), and are simple to integrate with an existing site — even when said site wasn't originally developed with Twack.
      A very basic Twack component view could look something like this:
      <?php namespace ProcessWire; ?> <h1>Hello World!</h1> And here's how you could render it via the API:
      <?php namespace Processwire; $twack = $modules->get('Twack'); $hello = $twack->getNewComponent('HelloWorld'); ?> <html> <head> <title>Hello World</title> </head> <body> <?= $hello->render() ?> </body> </html> Now, just to add a bit more context, here's a simple component controller:
      <?php namespace ProcessWire; class HelloWorld extends TwackComponent { public function __construct($args) { parent::__construct($args); $this->title = 'Hello World!'; if(isset($args['title'])) { $this->title = $args['title']; } } } As you can see, there's not a whole lot new stuff to learn here if you'd like to give Twack a try in one of your projects. The Twack README provides a really informative and easy to follow introduction to all the key concepts (as well as some additional examples) so be sure to check that out before getting started. 
      Twack is in development for several years and I use it for every new project I build. Also integrated is an easy to handle workflow to make outputs as JSON, so it can be used to build responses for a REST-api as well. I will work that out in one section in the readme as well. 
      If you want to see the module in an actual project, I have published the code of www.musical-fabrik.de in a repository. It runs completely with Twack and has an app-endpoint with ajax-output as well.
      I really look forward to hear, what you think of Twack🥳!
      Features Installation Usage Quickstart: Creating a component Naming conventions & component variants Component Parameters directory page parameters viewname Asset handling Services Named components Global components Ajax-Output Configuration Versioning License Changelog
    • By Robin S
      Page Reference Default Value
      Most ProcessWire core inputfield types that can be used with a Page Reference field support a "Default value" setting. This module extends support for default values to the following core inputfield types:
      Page List Select Page List Select Multiple Page Autocomplete (single and multiple) Seeing as these inputfield types only support the selection of pages a Page List Select / Page List Select Multiple is used for defining the default value instead of the Text / Textarea field used by the core for other inputfield types. This makes defining a default value a bit more user-friendly.
      Note that as per the core "Default value" setting, the Page Reference field must be set to "required" in order for the default value to be used.
      Screenshot

       
      https://github.com/Toutouwai/PageReferenceDefaultValue
      https://modules.processwire.com/modules/page-reference-default-value/
×
×
  • Create New...