Jump to content
Soma

MarkupSimpleNavigation

Recommended Posts

Thanks guys, I really think it should be CSS, it was just I was having a hard time handling a select/option nav for some reason

Home

About

-- About This

-- About That

Blog

Work

-- This Work

-- That Work

Contact

Am sure I'll end up with it in CSS, was just wondering if there was an added class.

Share this post


Link to post
Share on other sites

I still have no idea what you want to target and how you imagine doing it... So I can't help.

I know what a child of a parent is, but it's not something I can get a hand on in a navigation, it's nothing specific or I just don't get it. :)

Maybe this is something you can use:

"list_field_class" => {template} p_{id}

or 

"list_field_class" => p_{name}

Share this post


Link to post
Share on other sites

Just wanted to let you all know, I updated the module to 1.1.9 , with another new hook method to manipulate or add your very special case classes that will get added to list_tpl's "%s". 

To use this, here a little example to make it clearer. I want to add a class to my page with id 1001. Ok here we go.

$nav = $modules->get("MarkupSimpleNavigation");

function hookGetListClass(HookEvent $event){
    $child = $event->arguments('page'); // current rendered page item (in naviation)
    $class = $event->arguments('class'); // the class string, may be empty or filled
    if($child->id == 1001){ // add your checks, use API or whatever... daytime...
        $event->return .= " yourclass"; // add your class names
    }
}

$nav->addHookAfter('getListClass', null, 'hookGetListClass');
echo $nav->render();

Added this to readme

  • Like 5

Share this post


Link to post
Share on other sites

Hi Soma,

first of all, thanks for this great module!

I get the following message displayed:

Notice: Undefined offset: 1 in C:\[...]\site\modules\MarkupSimpleNavigation.module on line 217
 

and this is one of my calls:

            <?php    
            $treeMenu = $modules->get("MarkupSimpleNavigation"); // load the module
            $rootPage = $page->parents->count == 1 ? $page : $page->parent;
            $options = array(
            'parent_class' => 'active',
            'current_class' => 'active',
            'max_levels' => 1,
            'outer_tpl' => ''
            );
            echo $treeMenu->render($options, null, $rootPage);
            ?>
 

any ideas what might cause this, or can I ignore the message?

cheers, j

Share this post


Link to post
Share on other sites

If you leave outer tpl empty you should still specify the "||" .. 'outer_tpl' => '||'

  • Like 1

Share this post


Link to post
Share on other sites

If you leave outer tpl empty you should still specify the "||" .. 'outer_tpl' => '||'

Ka-Chiiing! :) thanks Soma

Share this post


Link to post
Share on other sites

Hi!

I'm stuck again %)

I have structure something like that:

-Red

--Circle

--Square

-Blue

--Circle

--Triangle

...

I need to output "#parent-children" anchors (#red-circle, #red-square).

Is it possible to output parent name? I've tried {parent},but this is url to parent.

Or I need the Captain Hook to help?

Share this post


Link to post
Share on other sites

@k

Hi!

I'm stuck again %)

I have structure something like that:

-Red

--Circle

--Square

-Blue

--Circle

--Triangle

...

I need to output "#parent-children" anchors (#red-circle, #red-square).

Is it possible to output parent name? I've tried {parent},but this is url to parent.

Or I need the Captain Hook to help?

Without knowing further details/context, why not just build your own menu?

It can be as simple as

$menu = "<ul>";
foreach($pages->get("/sompath/")->children as $child) {
    $menu .= "<li><a href='#'>$child->title</a>";
    if($child->numChildren) {
        $menu .= "<ul>";
        foreach($child->children as $subchild) {
            $menu .= "<li><a href='#{$child->name}-{$subchild->name}'>$subchild->title</a></li>";
        }
        $menu .= "</ul>";
    }
    $menu .= "</li>";
}
$menu .= "</ul>";

echo $menu;

If you still want to go the module way, yes there you could make a hook to archive what you want. There's a couple examples in this thread, but there can't be enough I guess ;)

function hookTagsString($event){
    $child = $event->arguments("page");
    if($child->template == "form"){ // some check for template? as you like
        // now return your own link markup with $event->return
        $event->return = "<a href='#{$child->parent->name}-{$child->name}'>-$child->title</a>";
    }
}
$nav->addHookAfter("getTagsString", null,'hookTagsString');

// render the navigation
echo $nav->render(null, null, $pages->get("/somepath/"));
  • Like 1

Share this post


Link to post
Share on other sites

@k

It can be as simple as

Domo arigato, Master Ninja!

Share this post


Link to post
Share on other sites

only output submenu of active (current) menu item

In modX, we had the "&hideSubMenus" parameter.

How could I achieve something similar with this module, without the use of css of JS?

Share this post


Link to post
Share on other sites

In peocesswire we have the collapsed option. :-)

Share this post


Link to post
Share on other sites

:D yes thx I know but doesn't this cause _all submenus to collapse?

Share this post


Link to post
Share on other sites

Have you even tried it? :)

Share this post


Link to post
Share on other sites

A little tip for anyone wanting a drop-down arrow on submenu parents, like after 'About' below -

post-378-0-92208700-1372857353_thumb.png

just add something like this to your CSS.

li.has_children > a:after {
    content: "▼";
    font-size: 70%;
    padding-left: .5em;
    vertical-align: middle;
}
  • Like 5

Share this post


Link to post
Share on other sites

If I only want to show the top-level items, what would be the correct options?

I tried 

'max_levels' => 1,
'levels' => false,
'collapsed' => true, 

but I still get all items. Is this module "overkill" if I only want to list topmost pages? Should I be better just using a simple selector and foreach, to output such a simple nav-list?

Share this post


Link to post
Share on other sites

Well the correct option is, you're right:

$nav->render(array("max_levels" => 1));

"levels" area already false and only for classes. If you output only 1 level you don't need "collapsed" true.

Not sure what you mean with you get all items.

Share this post


Link to post
Share on other sites

Well, every single page is being rendered as list / link, not just the top most hierarchy.

Share this post


Link to post
Share on other sites

Only with the default options it will render all levels. max_levels is there to limit this to as many levels as you like/need.

Share this post


Link to post
Share on other sites

OK, I'll try to rephrase it.

I have this in leftnav.inc:

$leftNav = $modules->get("MarkupSimpleNavigation");

$leftNavOptions = array(
    'max_levels' => 3,
    'collapsed' => true, // I guess this is the param that's not being executed correctly atm...
    'show_root' => false
);

echo $leftNav->render($leftNavOptions);

For simplicity's sake, let's say I have this basic 08-15 site structure:

- Company

- Products

- Downloads / Manuals

- News

Each of these main sections has sub-sections: max. 2 levels down.

Now, no matter if I'm at the root page of "products", or in a detail-page within products, the menu always outputs the entire tree. Like a sitemap, everything from A to Z. But that's not what I want. Shouldn't "collapsed = false" take care of that?

The idea is to have a basic HTML list that only displays the top-level hierarchy as links. But when I'm further down in level 1-2-3, it should recognize this... "ah, that's my home category, let's open up this navigation tree as well to show where we live".

Right now, all levels / sections are open all the time, at all levels, everywhere. "Collapsed" parameter true or false: doesn't change anything.

So e.g. if I'm visiting a product page (= 1 level down inside "products"), it should only render: 

- Company

- Products

  -- product A

  -- product B (= active)

  -- product C

- Downloads / Manuals

- News

But what the module actually does, is showing every single page, no matter how far up or down you currently are. Surely that was not the intention of the module?

So either I'm completely misunderstanding how this module is supposed to work, or it's some kind of bug. I'm sure I could visually hide the superflous elements via CSS, but I'd rather have the module not render them in the first place...

in a nutshell:

a) show only top-level links

+ b) but also show (nested) sub-levels if I am in inside this parent category, right down to the child (or grand-child document).

Share this post


Link to post
Share on other sites

Yes that's correct 'collapsed' does collapse all to the top level, except for those you'r on or in. It's only opening branches you're on.

'max_levels' does limit the levels rendered from the top level. 

So you example kinda illustrates this correct.

 Company

- Products

  -- product A

  -- product B (= active)

  -- product C

- Downloads / Manuals

- News

 

Also this 

 

 Company

- Products (= active)

  -- product A

  -- product B 

  -- product C

- Downloads / Manuals

- News

 

Or like this

 

 Company

- Products 

  -- product A

  -- product B 

  -- product C (= active)

     -- product C1

     -- product C2 

- Downloads / Manuals

- News

 

I don't know why it's not working for you, but I use it all the time, and I think quite a lot of others too.

Share this post


Link to post
Share on other sites

@dragan,

A conflict with some other code maybe? 

Share this post


Link to post
Share on other sites

Quite possible. The devil is always in the details. Thanks for your clarifications though. Will try again today with more caffeine :-)

Share this post


Link to post
Share on other sites

Actually, I'm beginning to believe it's a server issue. On another site / server it's working perfectly.

Could a multilingual site setup be a potential error source? (I wouldn't know why that would be the case, everything looks perfectly OK - just clutching at straws here...)

Share this post


Link to post
Share on other sites

If all else fails, I would strip my PW install down to the bare minimals (uninstall non-core modules; minus MSN of course ;)) or test in a vanilla PW install with only core modules and MSN installed and test from there to see if it works. Yeah, it is also good to test in different environments.

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