Jump to content
kongondo

Menu Builder

Recommended Posts

We'll that's strange...I thought I had dealt with this.....Old code must have crept in. I'll look into it, thanks for reporting.

Wait, I'm not using the dev branch. Whoops... (unless it was patched in the one you get from the directory?)

No need for the HTML builder :-)....for the <ul, it's just a missing space I forgot to put back after switching to configurable menu wrapper and for the <li> just a space to trim...I'll update tonight...

I guess I'm just a sucker for clean code.  ;)

Share this post


Link to post
Share on other sites

Just a thought and I am not sure how much this is needed but I am thinking about rendering breadcrumbs and wondering what would be the best way to render breadcrumbs based on the menu structure. Maybe I didn't think about it enough but there seems to be a possibility of complications rendering breadcrumbs when the menu structure is different to page structure.

Is there some way to have a feature whereby breadcrumbs could be output based on the menu structure with of course homepage being one step higher in the hierarchy of pages that are on the same level.?

Hmm, interesting thought. Technically, it is not impossible - just a recursive function that only grabs one branch...I'll have think...

Share this post


Link to post
Share on other sites

Wait, I'm not using the dev branch. Whoops... (unless it was patched in the one you get from the directory?)

I guess I'm just a sucker for clean code.  ;)

I'm all for clean and valid HTML too...What I meant is that I forgot to put back a space when I went from this <ul to this <$wTag.....bundling a third-party PHP class just to deal with that seems like an overkill :-)

Share this post


Link to post
Share on other sites

I'm all for clean and valid HTML too...What I meant is that I forgot to put back a space when I went from this <ul to this <$wTag.....bundling a third-party PHP class just to deal with that seems like an overkill :-)

Yeah, I figured that. Just mentioned it because of the general output. To me, it isn't overkill if it's to be used to enhance everything the module outputs. Much the same way I used ParseCSV in Jumplinks - I wanted the flexibility it provides, which enhances the experience.

:-)

Share this post


Link to post
Share on other sites

Wait, I'm not using the dev branch. Whoops... (unless it was patched in the one you get from the directory?)

Aaah, ye that's it. It works fine in dev branch. Please test and let me know? Thanks. I tested thoroughly with different combinations of multiple classes. I want to merge to master later today.

Share this post


Link to post
Share on other sites

I downloaded this archive, and it's still sticking ul and class together, unless I use an id.

Using 

<?= $modules->MarkupMenuBuilder->render('main', array('menu_css_class' => 'navigation')); ?>

Result:

<ulclass ="navigation">
<li  ><a  href='/'>Home</a></li>
...
</ul>

Edit: Culprit seems to be line 185 of MarkupMenuBuilder on in the archive I grabbed.

$cssMenuClass = $options['menu_css_class'] ? 'class ="' . $options['menu_css_class'] . '"' : '';

Share this post


Link to post
Share on other sites

Thanks, will fix soon. As for the <li>, it works fine for me...are you seeing that extra space (as in your code above...)?

  • Like 1

Share this post


Link to post
Share on other sites

Thanks, will fix soon. As for the <li>, it works fine for me...are you seeing that extra space (as in your code above...)?

The code is as I pasted it.

post-2289-0-60312500-1426615972_thumb.pn

(Except the ul thing, which I changed.)

Share this post


Link to post
Share on other sites

Update: version 0.0.5

  • Fixed markup errors reported above in MarkupMenuBuilder
  • Merged version to master (updated in modules directory as well)
Edited by kongondo
  • Like 3

Share this post


Link to post
Share on other sites

Hmm, interesting thought. Technically, it is not impossible - just a recursive function that only grabs one branch...I'll have think...

Great. Would be cool to have this feature.

Share this post


Link to post
Share on other sites

Very nice, a must-have. Thanks!

May I ask what admin theme was used on the screenshots? Looks pretty sharp but cannot find anywhere.

  • Like 1

Share this post


Link to post
Share on other sites

@tpr,

Thanks.

They are all part of the admin themes that natively ship with PW. In the first couple of screenshots, that's AdminThemeReno, followed by AdminThemeDefault using the color set 'Futura' and last screen the color set 'Warm'.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks, I got it now. It was the Reno theme, it has to be installed first to use. Have to do some PW development soon to get back to PW basics :)

Share this post


Link to post
Share on other sites

Update: version 0.0.6

In dev branch for now

  1. As per this idea, thanks @dazzyweb, added a renderBreadcrumbs() method to render, uh..., breadcrumbs. See documentation in Read Me for how to use
  2. For both render() and renderBreadcrumbs(), you can also pass a Page object as the first parameter. This is in addition to the already available ways, i.e. you can also pass a menu page's title, name or id or an array of menu items built from a menu page's menu_items field.

Please test and let me know, especially playing around with the options you can pass renderBreadcrumbs(). See Read Me, including comments in the code. These options can be shared between the above two methods. Same goes for the first parameters - e.g. get a menu page and pass that once to both render() and renderBreadcrumbs(). Also added the option to prepend 'Homepage' as topmost breadcrumb item even when it is not ancestrally part of the breadcrumb.

Note

If you call renderBreadcrumbs() in a page that is not part of the menu items you will get an error if logged in as superadmin but nothing returned for all other users. E.g., say you have the following menu items:

Home
About Us
Products
Services
Contact Us

renderBreadcrumbs() would only work (duh!) if called from the template file of AND viewing one of those pages. This is because the method works by first matching the 'pages_id' of a menu item with the $page->id (current page) and builds the breadcrumb from that.

External menu items can be part of the breadcrumb as long as they are not the current item (of course) - which they can never be anyway since clicking on them will load external URLs

  • Like 3

Share this post


Link to post
Share on other sites

Thanks kongondo, seems to work fine but I have one or 2 queries or suggestions for a couple of issues I have.

There are times when it would be useful to display breadcrumbs for pages that are not in the main header menu created. Do you think there is a way around this with some kind of option?

So as a simple example if we have the following menu created with Menu builder:

HOME

ABOUT

-who are we?

-Our history

FAQ

CARS

CONTACT

ABOUT page would have children in the menu created and work fine with the renderBreadcrumbs method.

'CARS' would have 50 children in the page tree but I might not want to show these children as a sub menu so they would not be included in the menu created but I might still want to show breadcrumbs if going to the page 'Audi' or 'Jaguar' such as Home / Cars / Jaguar which could have been accessed from some different link or list.

Do you think it is possible to have some kind of option whereby the breadcrumbs or normal render method  recognises the children of the 'CARS' page in the normal pages tree without actually having them in the menu created by menu builder?

Another point connected with this is if I am at the page Jaguar (Home / cars / Jaguar) it would be useful with the normal menu render method to be able to still add a 'current' class to 'CARS' in the menu so it could still be highlighted as the parent page even though the page Jaguar is not in the menu created with menu builder. It would also be useful to be able to add a 'current' class to ABOUT page when viewing sub pages of the ABOUT page which are in the menu created by Menu builder.

Share this post


Link to post
Share on other sites

@dazzyweb,
 
OK, I might have found a way to achieve both of these. Although I think it is possible to include intermediate natural parents (i.e. PW parentage) that are also not in the breadcrumbs, I think I will stick to immediate parent only. Same goes for the 'current' class. What I mean is this....let's say your 'jaguar's had child pages as well, maybe 'model A', 'model B', etc., that are also NOT part of the MB menu, following your request, you would something like this: Home / cars / Jaguar / Model A. The problem I foresee is what if an intermediate parent was part of the MB menu but not in a 'natural' position? I we were to include it in the breadcrumbs, it could end up in the wrong position (from the breadcrumbs point of view). I hope this makes sense and maybe this is an edge case. Anyway, unless convinced otherwise, I am limiting this to the immediate parent, e.g. Home / cars / Jaguar /. Thoughts?
 
Edit:
 
No, scratch that. I'll make the depth to which one wants to display non MB items that are natural children of the current MB item configurable, e.g. 

append_child => 0//default - no child appended = Home / Cars
append_child => 1// append the immediate child = Home / Cars / Jaguar
append_child => 2// append immediate child and grandchild
etc...

Beyond that...how you structure your menus is up to you :-)

Edited by kongondo
Changed mind...
  • Like 1

Share this post


Link to post
Share on other sites

Another thought I have of doing this is the following though I am not sure if there are any complications making this.

What if each separate page added to the menu had an option added to it in the menu builder(where title, url, css options are etc..) such as 'include this pages natural children from page tree' with a second option with it with a yes/no to display children in normal render method? The breadcrumbs could then normally display all levels as the pages would be included in the built menu with the option of not displaying with the normal render method if not wanted there.

This could actually be useful in other ways as well if normally wanting to include natural children under a page without actually having to manually put them all there especially if there are many.

If this is set up in such a way whereby all natural children are included such as the way a selector works then I assume when adding another page as a child in the normal page tree that it would then be included as well automatically in the menu builder if set up such a way. This could be quite useful making the menu builder much more flexible.

  • Like 1

Share this post


Link to post
Share on other sites

I think your 'another thought'  is a better approach since it allows for more granularity, i.e. it targets individual menu items rather than the first approach which targets the whole menu in terms of including natural child pages. I don't think there is a need for the second option 'yes/no' though unless am not getting it? By using the 'include natural children' option, you imply that you want them to be displayed. 

The way I think I'll do it:

'include_children' => 0//default = no
'include_children' => 1//yes, but only in menu, i.e. render()
'include_children' => 2//yes, but only in breadcrumbs, i.e. renderBreadcrumbs()
'include_children' => 3//yes, in both

//number of child nesting levels to show IF include_children > 0
//include_children_levels => 1//default, i.e. show only immediate children [or child in case of breadcrumbs]
//include_children_levels => 2//etc....show up to grandchildren/grandchild, etc..

The include_children can be tricky though....One might end-up with lots of sub-menus! But this is is optional, so up to the developer really.

Apart from some coding issues I may not have thought of yet, the visual MB aspect has to be considered. Those natural child pages will not be included in the saved menu items, hence will not be displayed in the menu tree in the back-end (ProcessMenuBuilder). They will only be included in the front-end output during runtime. That may confuse your editors, but nothing you can't educate them about, and this is optional anyway.

Edit:

Or...in the spirit of flexibility and granularity....in MB admin, also add an include_children_levels text (int) box next to an include_children checkbox. Then in the front-end, render() and renderBreadcrumbs() will be guided by:

if the setting include_children_levels is empty AND you have an $options = array ('include_children' => xx,  'include_children_levels' => zz), the level set in $options takes precedence and is applied overall except for menu items where the setting include_children_levels is NOT empty; an explicit level set at menu item level will override any $options setting. Would such a workflow work for you?

Edited by kongondo
  • Like 1

Share this post


Link to post
Share on other sites

I don't think there is a need for the second option 'yes/no' though unless am not getting it? By using the 'include natural children' option, you imply that you want them to be displayed. 

Yes but sometimes not displayed in the main menu but only breadcrumbs.

The yes/no option was to give flexibility for the editors so that a choice could be made on whether to have the children displayed with the 'normal render method'(in main menu for example) or not for each page that has children. Since there can be times when I don't want them displayed on the main menu(only in breadcrumbs) and this option can be different for each page added in the menu builder. In the example I made before the car brands would not be shown in the main header menu but would be shown in breadcrumbs so option chosen would be set to 'NO'. The about page would have option set to 'YES'(which would be default) so the children of about page would be displayed in the main menu and breadcrumbs.

Choosing to 'include natural children' and 'YES' would include the children in both normal menu and breadcrumbs, choosing 'NO' would only include in breadcrumbs. Having this option with each page(menu item) enables each page added to the menu to have different options if they are displayed in main menu or not.

Maybe I am not understanding the 'include_children' option fully but wouldn't this then end up overriding all the options chosen for each individual page(menu item) by the admin for the normal render method(main menu)? This would then disable the ability to have one page on main menu displaying it's children and one page in the menu not displaying it's children.

Apart from some coding issues I may not have thought of yet, the visual MB aspect has to be considered. Those natural child pages will not be included in the saved menu items, hence will not be displayed in the menu tree in the back-end (ProcessMenuBuilder). They will only be included in the front-end output during runtime. That may confuse your editors, but nothing you can't educate them about, and this is optional anyway.

That's fine, I think that is the best way anyway since if there were many children it could make the menu builder quite crowded & unworkable. This way would actually make it much cleaner to use.

Share this post


Link to post
Share on other sites

Ah, I see (see also my edited posts above). Your yes/no is targeted at editors whereas my include_children with its options is targeted at developers. Giving editors the choice makes more sense and I'll adapt that instead. So, just to make sure we are on the same page:

  1. Editors control inclusion of natural children (default is exclude - this setting is not saved)
  2. Editors control whether natural children are shown in menu or breadcrumbs or both (This can a set of 3 radio buttons - any selection also implies include children; no selection implies don't include - or I could add a fourth button but it's already crowded in that menu setting as it is!! if one wants to edit the setting. No, better yet, I'll use a drop-down with 3 options - 'menu', 'breadcrumbs', 'both'. No selection = default and means 'don't include natural children')
  3. Editors control this per menu item (i.e. per PW page)

What do you think about my levels question though? Sticking to immediate children is pretty straightforward. Do you see a need for grand-children? This is more relevant for breadcrumbs, e.g. if you wanted Home / Cars / Jaguar / Model X where both 'Jaguar' and 'Model X' were not part of a MB menu...

Share this post


Link to post
Share on other sites

Ah, I see (see also my edited posts above). Your yes/no is targeted at editors whereas my include_children with its options is targeted at developers. Giving editors the choice makes more sense and I'll adapt that instead. So, just to make sure we are on the same page:

  1. Editors control inclusion of natural children (default is exclude - this setting is not saved)
  2. Editors control whether natural children are shown in menu or breadcrumbs or both (This can a set of 3 radio buttons - any selection also implies include children; no selection implies don't include - or I could add a fourth button but it's already crowded in that menu setting as it is!! if one wants to edit the setting. No, better yet, I'll use a drop-down with 3 options - 'menu', 'breadcrumbs', 'both'. No selection = default and means 'don't include natural children')
  3. Editors control this per menu item (i.e. per PW page)

Looks good

What do you think about my levels question though? Sticking to immediate children is pretty straightforward. Do you see a need for grand-children? This is more relevant for breadcrumbs, e.g. if you wanted Home / Cars / Jaguar / Model X where both 'Jaguar' and 'Model X' were not part of a MB menu...

Would be good to have levels and I can see a need for grand-children sometimes.

I think that levels could be useful as well for the main menu at certain times when using include_children so as to limit the amount of levels shown for example in a drop down menu. But then the levels needed to be shown in main menu could then differ to the amount needed for breadcrumbs so would maybe need different include_children_levels for main menu and breadcrumbs.

Or...in the spirit of flexibility and granularity....in MB admin, also add an include_children_levels text (int) box next to an include_children checkbox. Then in the front-end, render() and renderBreadcrumbs() will be guided by:

if the setting include_children_levels is empty AND you have an $options = array ('include_children' => xx,  'include_children_levels' => zz), the level set in $options takes precedence and is applied overall except for menu items where the setting include_children_levels is NOT empty; an explicit level set at menu item level will override any $options setting. Would such a workflow work for you?

So an options default would be set to all menu items in one swoop and then can be tweaked at admin level? It is an interesting thought. The more I think about it the more I see it could come in handy.

Share this post


Link to post
Share on other sites

Would be good to have levels and I can see a need for grand-children sometimes.

I think that levels could be useful as well for the main menu at certain times when using include_children so as to limit the amount of levels shown for example in a drop down menu. But then the levels needed to be shown in main menu could then differ to the amount needed for breadcrumbs so would maybe need different include_children_levels for main menu and breadcrumbs

OK, we should have these separate...I need to reiterate that MB will not control the number of such children to show at any level.....although I want to leave that to the developer (or editor?), I may need to limit maximum number of pages returned in that 'find'. I imagine a situation where an editor working on some other part of the site inadvertently adds tens of child pages (e.g. under CARs and under Jaguar, etc...)...Coupled with a levels of say 3, you suddenly end up with 3 x XX number of pages to find for one or more menu items! Can easily chock memory...Not sure how to implement this at the moment...maybe make it configurable at developer (template file) level...something like max_children at each level...

So an options default would be set to all menu items in one swoop and then can be tweaked at admin level? It is an interesting thought. The more I think about it the more I see it could come in handy.

Exactly...would save you a few clicks...

Edit:

Below is how I envisage the order of priority of $options (API/template file) setting vs. admin-level settings. There's 4 possible admin-level settings for each menu item in respect of whether to show its natural children. Show in: (1) Menu (2) Breadcrumbs (3) Both (4) Never. In addition there's the number of levels to show in respects of choices 1-3.

Desc order of priority for final display

  1. $options = array('include_children' => 0)//overrides everything set at admin level. No natural children displayed anywhere
  2. Any explicit admin-level setting: 1- 4//Natural children displayed/not displayed as per choices 1-4 FOR ONLY THIS menu item irrespective of what is set in $options (apart from a '0' setting as shown in point #1 above)
  3. $options = array('include_children' => 1|2|3)//overrides ONLY EMPTY admin-level settings: Show natural children of all items without an admin-level setting ONLY in menu [1] (render()) OR breadcrumb (renderBreadcrumbs()) [2] OR both [3]
  4. Empty admin-level setting: no natural children displayed anywhere
Edited by kongondo
order of priority description
  • Like 1

Share this post


Link to post
Share on other sites

Is it possible to use this in a Multi Language Site.

Tried to use it, but in the menu title I get Array and in the outputs as well, it outputs Array, instead of the menu title. When changing language it buts.

Thanks in advance.

Share this post


Link to post
Share on other sites

@bbeer,

No, it's not multi-lingual in that sense. The reason you see an array is because the various titles (in the different languages you have installed) are held in an array. When saving, since I have not implemented ML support, PW does not know what to save. That is what I am assuming. I have never worked in a ML site before so this is new to me too. I am looking into it. I'll ask in the forums (Soma probably will pick it up :-)). So far my searches have come empty, i.e. how to save a field (in this case a page title) in a ML environment. Hopefully I'll find an answer here: https://processwire.com/api/multi-language-support/multi-language-fields/

Edited by kongondo

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 Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By bernhard
      #######################
      Please use the new RockFinder2
      #######################
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
×
×
  • Create New...