Jump to content
Soma

MarkupSimpleNavigation

Recommended Posts

Next little tutorial on this really great module...

Getting a Footermenu stripped from the mainmenu and output in a footermenu

1. Setup Pagefield for your /settings/ or /tools/ page

This solution could be set by the user direct via a simple pagefield to select normal contentpages that a normaly in the mainmenu...but this items should stay not there and render somewhere else...

post-2327-0-42569000-1442412709_thumb.jp

2. Strip the choosen pages from the mainmenu

//get the pagefield content
$footerMenu = $settings->footer_menu;

//just the needed option listed - other options like needed for your menu
$options = array(
       'selector' => 'id!='.$footerMenu.'',    // define custom PW selector
);

3. Output the pagefield items

post-2327-0-41513000-1442412792_thumb.jp

<?php //in my example i am in the _main.php template and render some footermenu
if ($settings->footer_menu) { //check for the pagefield
    echo '<div class="eight columns">';
    foreach ($settings->footer_menu as $item) {
        if (!$item->is('hidden') || $item->is('unpublished')) { //check for hidden/unpublished pages!!
	    echo '<a href="'.$item->url.'" class="button sendbtn btnSend">'.$item->title.'</a>';
	}
    }
    echo '</div>';
}
?>

hope this is helpful...have fun.

I don't have a blog and i am a fan of keeping things together....so don't bother if i'm posting such things here and write me if such usecases are not helpful or nonsense...... ;)

Best regards mr-fan

  • Like 2

Share this post


Link to post
Share on other sites

Is it possible to use the "selector" option to choose menu items based on parent?

I tried...

"selector" => "parent=1020"

...and...

"selector" => "parent=/my-page/"

...but neither of these worked.

I know I can do this by setting a PageArray as the root object but I'm trying to understand why I can't do this with the selector option.

Share this post


Link to post
Share on other sites

No it's not possible, it iterates the tree structure as is. "parent -> childrens -> childrens".

You can only set the top root items per a PageArray. Form there these are iterated down the tree. The selector only is used to filter the children of the current nodes.

Share this post


Link to post
Share on other sites

Next little tutorial on this really great module...

Getting a Footermenu stripped from the mainmenu and output in a footermenu

1. Setup Pagefield for your /settings/ or /tools/ page

This solution could be set by the user direct via a simple pagefield to select normal contentpages that a normaly in the mainmenu...but this items should stay not there and render somewhere else...

attachicon.giffootermenu.jpg

2. Strip the choosen pages from the mainmenu

//get the pagefield content
$footerMenu = $settings->footer_menu;

//just the needed option listed - other options like needed for your menu
$options = array(
       'selector' => 'id!='.$footerMenu.'',    // define custom PW selector
);

3. Output the pagefield items

attachicon.giffootermenusorting.jpg

<?php //in my example i am in the _main.php template and render some footermenu
if ($settings->footer_menu) { //check for the pagefield
    echo '<div class="eight columns">';
    foreach ($settings->footer_menu as $item) {
        if (!$item->is('hidden') || $item->is('unpublished')) { //check for hidden/unpublished pages!!
	    echo '<a href="'.$item->url.'" class="button sendbtn btnSend">'.$item->title.'</a>';
	}
    }
    echo '</div>';
}
?>

hope this is helpful...have fun.

I don't have a blog and i am a fan of keeping things together....so don't bother if i'm posting such things here and write me if such usecases are not helpful or nonsense...... ;)

Best regards mr-fan

There's a tutorial board here in the forums where you would post such examples. I don't think it helps much in here.

Share this post


Link to post
Share on other sites

The selector only is used to filter the children of the current nodes.

Thanks Soma, I understand better now.

Share this post


Link to post
Share on other sites

There's a tutorial board here in the forums where you would post such examples. I don't think it helps much in here.

Ok if i've the time i collect my snippets to a "Tipps&Tricks with MarkupSimpleNavigation" topic - to get things connected.

For myself - i always read modulethreat completly if i'm using them to get the best start or knowlegde about the used addon...Read the fucking Manual....is not a option it is a obligation if you are new to a cms/module/technique....;)

But i will follow your advice since it better fits as tutorials than tracking issues or getting help.

Best regards and thank you for feedback mr-fan

Share this post


Link to post
Share on other sites

Markup Simple Navigation Module

While there was a lot of people asking how to make navigation, and there were many examples around already (apeisa, ryan...) I took the chance to sit down 2-3 hours to make a simple navigation module. It has even some options you can control some aspects of the output.

Installation:

1. Put this module's folder "MarkupSimpleNavigation" into your /site/modules folder.

2. Go to your module Install page and click "Check for new modules". It will appear under the section Markup. Click "install" button. Done.

Technically you don't even need to install it, after the first load call ( $modules->get("MarkupSimpleNavigation") ) it will install automaticly on first request if it isn't already. But it feels better. However, it will not be "autoloaded" by Processwire unless you load it in one of your php templates.

Documentation:

https://github.com/somatonic/MarkupSimpleNavigation/blob/master/README.md

Modules Repository processwire.com

mods.pw/u

Download on github

https://github.com/somatonic/MarkupSimpleNavigation

Advanced example with hooks

creating a Bootstrap 2.3.2 Multilevel Navbar

https://gist.github.com/somatonic/6258081

I use hooks to manipulate certain attributes and classes to li's and anchors. If you understand the concept you can do a lot with this Module.

could i put the "creating a Bootstrap 2.3.2 Multilevel Navbar" code in the _init.php to run ?

Share this post


Link to post
Share on other sites

The load and setup hooks you could put in _init.php but the render would be where you render your navigation.

Share this post


Link to post
Share on other sites

Hi Soma,

I need to use plain PHP pages ("/foo/bar.php") to a website powered by ProcessWire. How can I add this in Markup Simple Navigation?

Sample structure that shows the mix of Processwire pages and PHP pages in use:

  • Products
    • Product 1
    • Product 2
    • Product 3
    • Request quote <- Quote form in plain PHP.
  • References
  • About us

Share this post


Link to post
Share on other sites

I need to use plain PHP pages ("/foo/bar.php") to a website powered by ProcessWire. How can I add this in Markup Simple Navigation?

Question: any particular reason why the form needs to be processed outside of PW?

Share this post


Link to post
Share on other sites

Wanted to ask the same.

Only way I see is use a page with a text field to enter a path to a php file. Then use that field as in the url tag in the item template. I.e. href='{pathphp|url}'

Share this post


Link to post
Share on other sites

@Mike Rockett & Soma: The reason for processing the form outside PW is that it's part of a 3rd party booking system using an external database.

I have the following enhancement request for the module: "It shall be possible to include plain PHP pages ("/foo/bar.php") from third party plug-ins and the like to MarkupSimpleNavigation. Suggested solution is to allow adding in-memory pages to the navigation entries on the fly. The purpose of adding in-memory pages is to place the 3rd party page in PWs Page structure. Something along these lines:

$p = new Page();
$p->setOutputFormatting(false);
$p->parent = $pages->get("/MyParentPage");
$p->template = "SomeTemplate";
$p->title = "External page";
$p->name = "external_page";
// Note I do not use $p->save(), so it's a pseudo page that exists in memory only.
// Add the page to $entries somehow [...] -> $entries = $pages->get("/")->navigation_entries; ....
$entries = $pages->get("/")->navigation_entries; // Load entries (including our new page)
echo $treeMenu->render(null, null, $entries);

(Perhaps this is already possible without making changes to the module?)

Right now, I will go ahead and 1) make a unique template for the form that "include()" the form from a PHP file, 2) add a PW page for the form and 3) repeat this process for all relevant files (4 times in total per site using the booking system). I can then output a link and title to the page using MarkupSimpleNavigation. (I have done this before, it's a bit cumbersome but it will work.)

Share this post


Link to post
Share on other sites

While it would be possible to inject in memory pages, I don't want to go that route for various reasons.

What I do is add a dummy page as you mention. Then add a field "exturl" to the template. Then enter the url in that field like "/path/to/file.php".

In the navigation code you then use "exturl" in the item_tpl:

$options = array("item_tpl" => "<a href='{exturl|url}>{title}</a>');
  • Like 1

Share this post


Link to post
Share on other sites

I have problems with outputting the whole Menu Tree  up to the parent page Product when in 3rd level of a submenu.

The structure is

Home

  Products

      product 1

      product 2

         Item 1

         Item 2

         Item 4

      product 3

My menu looks like this

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

$leftNavOptions = array(
	'max_levels' => 3,
	'collapsed' => true,
	'show_root' => false,
	'levels' => true,
	'outer_tpl' => '<ul id="leftNavOuter" class="noPrint">||</ul>',
	'firstlast' => true
);

$root = $page->parents->count == 1 ? $page : $page->parent;
echo $leftNav->render($leftNavOptions, $page, $root);

that works perfect well until you navigate into the 3rd Level, then all levels above disapear and you see only the items level

Is there a way to output all three levels when in 3rd level?

Your help is much appreciated.

Share this post


Link to post
Share on other sites

that works perfect well until you navigate into the 3rd Level, then all levels above disapear and you see only the items level

I think your problem comes from this:

$root = $page->parents->count == 1 ? $page : $page->parent;

For the first two levels $root is "Products", but on the third level $root is "product 2" or whatever level 2 parent you are in. So you only see children of "product 2".

I think this will do what you want:

$root = $page->rootParent;

Share this post


Link to post
Share on other sites

Hello all,

I have two questions:

First:

using MSN Module ... is it possible to have "unlinked" items  in the menu?.
I have several pages that serve as headlines to structure the content better. They have a seprate template (menu-ueberschrift) and they should not be clickable ... just be there as plain text. These Items have children. I want an uncollapsed menu..

Second question:

Goes into the same direction: I would like to have active pages without links, too. I think there is no need for links  for a page I'm currently viewing.

Hopefully someone can help, as I'm stuck here.

Share this post


Link to post
Share on other sites

Solved it myself ...

Finally managed to set up hooks:

function myItemString(HookEvent $event) {
    $child = $event->arguments('page'); // current rendered child page
    // any logic with $child possible here
    
    /**
     * Überschriften
     */
    if ($child->template->name == 'menue-ueberschrift') {
        $event->return = "<span> $child->title</span>";
    };

    /**
     * active
     */
    if ($child->template->name == 'standard') {
        if ($child->id == wire('page')->id) {
            $event->return = "<span> $child->title</span>";

        }
    };
}

// setup the hook after on ___getItemString($class, $page) method
$nav->addHookAfter('getItemString', null, 'myItemString');
/* Render Navigation Markup adding options, too---------------- */
echo $nav->render()

Seems to work so I guess it's ok.

And I've learned something new :-)

Cheers Hanna

  • Like 2

Share this post


Link to post
Share on other sites

Ok,

I am having some issues with this menu (will be in bootstrap).

I currently have:

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

	 function hookGetListClass(HookEvent $event){
	    $child = $event->arguments('page'); // current rendered child page
	    $class = $event->arguments('class'); // the class string already present
			$options = array(
				'has_children_class' => 'dropdown',
				'outer_tpl' => '<ul class="nav">||</ul>',
				'inner_tpl' => '<ul class="dropdown-menu">||</ul>'
			);


	     // any check on that child to set your custom class
	     if($child->id == 1001){
	         $event->return .= " inner"; // add your custom class to the existing
	     }
	 }

	 // setup the hook after on ___getListClass($class, $page) method
	 $nav->addHookAfter('getListClass', null, 'hookGetListClass');
	 echo $nav->render($options);
	 ?>

However, the nav doesnt seem to be taking the options, and is instead using the "has_children" class. I saw a post almost exactly like this, but couldnt get the outcome. The inner ul should have a class of "dropdown".

Share this post


Link to post
Share on other sites

Hey guys,

I love this plugin. It works almost perfect for me. But I have a little question. I want that the parents don´t have a link.

This is my markup now:
<nav>
               
        <a href="<?=$config->urls->root; ?>" id="home">Von der Berkelaue</a>
       
        <?php 
            $treeMenu = $modules->get("MarkupSimpleNavigation"); // Modul laden   

        
            $options = array(
                'max_levels' => 2,
                'show_root' => true,
                'outer_tpl' => '<ul id="menu">||</ul>',
                'inner_tpl' => '<ul>||</ul>',
                'list_tpl' => '<li%s>||</li>',
                'item_tpl' => '<a href="{url}">{title}</a>',
                'item_current_tpl' => '<a href="{url}" class="active">{title}</a>',
                'debug' => true,
                'selector' => 'template!=aktuelles-eintrag, has_parent!=/galerie/',
            );
            echo $treeMenu->render($options); // Navigation rendern
        ?>
    </nav>

And this is my output:

<ul id="menu">
    <li class="current"><a href="/" class="active">Startseite</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
    </li>
    <li><a href="/aktuelles/">Aktuelles</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
    </li>
    <li class="has_children"><a href="/uber-uns/">Über uns</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
        <ul>
            <li><a href="/uber-uns/familie/">Familie</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
            <li><a href="/uber-uns/unsere-hunde/">Unsere Landseer</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
        </ul>
    </li>
    <li><a href="/wurfplanung/">Wurfplanung</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
    </li>
    <li class="has_children"><a href="/wurfe/">Würfe</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
        <ul>
            <li><a href="/wurfe/wurfplanung/">A-Wurf</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
            <li><a href="/wurfe/b-wurf/">B-Wurf</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
            <li><a href="/wurfe/c-wurf/">C-Wurf</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
            <li><a href="/wurfe/d-wurf/">D-Wurf</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
            <li><a href="/wurfe/e-wurf/">E-Wurf</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
            <li><a href="/wurfe/f-wurf/">F-Wurf</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
            <li><a href="/wurfe/g-wurf/">G-Wurf</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
        </ul>
    </li>
    <li><a href="/galerie/">Galerie</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
    </li>
    <li><a href="/gastebuch/">Gästebuch</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
    </li>
    <li><a href="/links/">Links</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
    </li>
    <li><a href="/kontakt/">Kontakt</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
    </li>
</ul>
<!-- [MarkupSimpleNavigation Rendertime: 0.0366] -->
</nav>

And it should look like this:

<ul id="menu">
    <li class="current"><a href="/" class="active">Startseite</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
    </li>
    <li><a href="/aktuelles/">Aktuelles</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
    </li>
    <li class="has_children"><a href="#">Über uns</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
        <ul>
            <li><a href="/uber-uns/familie/">Familie</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
            <li><a href="/uber-uns/unsere-hunde/">Unsere Landseer</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
        </ul>
    </li>
    <li><a href="/wurfplanung/">Wurfplanung</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
    </li>
    <li class="has_children"><a href="#">Würfe</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
        <ul>
            <li><a href="/wurfe/wurfplanung/">A-Wurf</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
            <li><a href="/wurfe/b-wurf/">B-Wurf</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
            <li><a href="/wurfe/c-wurf/">C-Wurf</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
            <li><a href="/wurfe/d-wurf/">D-Wurf</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
            <li><a href="/wurfe/e-wurf/">E-Wurf</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
            <li><a href="/wurfe/f-wurf/">F-Wurf</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
            <li><a href="/wurfe/g-wurf/">G-Wurf</a>
                <!-- [Selector Level2: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
            </li>
        </ul>
    </li>
    <li><a href="/galerie/">Galerie</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
    </li>
    <li><a href="/gastebuch/">Gästebuch</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
    </li>
    <li><a href="/links/">Links</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
    </li>
    <li><a href="/kontakt/">Kontakt</a>
        <!-- [Selector Level1: template!=aktuelles-eintrag, has_parent!=/galerie/] -->
    </li>
</ul>
<!-- [MarkupSimpleNavigation Rendertime: 0.0366] -->
</nav>

I hope you understand my problem. My english isn´t very good :D

Thanks, Jannis

Share this post


Link to post
Share on other sites

Hi Jannis,

Is  that you want this

<li class="has_children"><a href="#">Über uns</a>

appear like a headline ? with no link?

I think it would be a good idea to give those 'headlines' their own template like 'ueberschrift' or so.

Then you could proceed similar to what I posted here using a hook.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks HannaP,

this should work. But I find now another way to solve it. 

Still thanks!

Share this post


Link to post
Share on other sites

Hi,

i am using this Module for quit a while with great joy. Easy to implement and very flexible.

Right now i wonder if something like this is possible by using just the module options without hooking the core: I have a 2-level menu with several parents and relevant child pages. On last parent the child array is (should) populated from a variable ($items), which collects only (child) pages with dedicated page view permission.

So i fiddle around with the "selector_levelN" option. First try:

$options = array(
  "levels" => true,
  "max_levels" => 2,
  "selector_level2" => "id=$items"
);

This gives me the expected result in level2 on the last child tree, but fails of course because the selector ("id="$items") returns nothing on all other parent/child levels. What i would need is some condition like (Tried this and other notations, no luck):

$options = array(
...
"selector_level2" => (parent=<id>) ? "id=$items" : ""
);

In words. If the parent page has a dedicated ID (here: the parent page which holds all permission controlled (child) pages), populate the "selector_level2" option with predefined pages ($items), otherwise don't constrain the collecting for level 2.

Probably this is the nutshell: Are condition possible/allowed in module option selector values?

cheers and thanks

felic

Share this post


Link to post
Share on other sites

You could perhaps use OR-groups in the selector (untested):

$options = array(
  "level" => true,
  "max_levels" => 2,
  "selector_level2" => "(parent!=$lastpageid), (id=$items)"
);
  • Like 1

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 David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.0)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM... one of those three or four letter acronyms anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework", since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no JavaScript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode. There are 4 different view modes.
      View mode "Day" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records. View mode "Month" shows the total of all visitors per day from the first to the last day of the selected month. View mode "Year" shows the total of all visitors per month from the first to the last month of the selected year. View mode "Total" shows the total of all visitors per year for all recorded years. Please note that multiple visits from the same IP address within the selected period are counted as a single visitor.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).
       
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...