Jump to content



Recommended Posts

Hi everyone!

With Batcher you can batch-edit and create Pages in the Pw Admin. If you install this module, you get a new Page "Batcher" under Setup.

Modules page: http://modules.processwire.com/modules/process-batcher/

Github: https://github.com/wanze/ProcessBatcher

post-582-0-04675500-1362135437_thumb.png post-582-0-62980800-1362135459_thumb.png


How does it work?

  1. Search your pages with a selector. You can check if you want to include also hidden/unpublished pages with the filters.
  2. Select the pages you want to execute an action (the action only gets executed on "checked" pages).
  3. Select the action and if necessary, additional data like the new parent or the new template.
  4. Execute.

Supported actions:

  • Publish/Unpublish Pages
  • Hide/Unhide Pages
  • Lock/Unlock Pages
  • Trash Pages
  • Delete Pages
  • Change Parent
  • Change Template

Batcher does the following permission checkings for the current user:

  • Don't display pages that are not editable
  • Remove Actions if the user doesn't have the permissions (page-delete, page-move, page-template, page-lock)

Important notes:

When changing a template, data in fields of the old template which are not assigned to the new template gets deleted.

When changing the parent, the template of the new parent must accept the pages template as children. This is a setting in the template under "family".


How does it work?

  1. Select a parent where your new pages will be added as children
  2. Add as many pages as you want by clicking "add Page"
  3. Click "Create Pages"

You must enter a title and choose a template. The name is optional: If left empty, Pw will generate this for you.

Includes permission checking and Family template restrictions. This means in detail:

  • The selected parent must accept children and their template
  • The pages template must accept the parents template
  • User needs the permission to add children to the selected parents template
  • User needs the permission to create Pages for the chosen Template

Batch-creating tips

The chosen template and the statuses are always cloned from the last row. So if you need to add 30 pages

with the same template, define it first and the click "add Page" - it'll make your life easier ;-)

You can drag & drop the table rows should you want to change the order. The dragging looks ugly but it works.

For the lazy dogs and keybord hackers among us, you can add a new row by pressing "ctrl+n".
This works (at least in firefox) only if no input has focus. After adding a new row, the title input gets the focus.

By pressing 3 times tab you arrive at the published-checkbox, here the short-cut works.

Restrict Batcher for a user to only allow editing or creating

Create permissions "batcher-edit" and/or "batcher-add". As soon those exists, the module checks if the current

user has the permissions.

If you only need batch creating, check out the following module by Soma:



  • Like 35
Link to comment
Share on other sites

Looks awesome, thanks @Wanze! This'll come in handy especially for some of our bigger sites, I'm sure :)

@Luis: some things can't be unseen. Going to have difficult time maintaining serious expression while introducing this module to coworkers or clients, simultaneously avoiding this image of dancing badgers..

  • Like 1
Link to comment
Share on other sites

Thanks guys, let me know what you think and how I could improve the module.

Some possible actions to add:

- Change User

- Change Created-date


To be honest, I knew that modx had a Tool called Batcher.

I was thinking some time of a good name and finally decided to name it Batcher too, not very creative I know :)

Batchman was another idea, based on Anti's Trashman.

My concern is that if someone sees the modules title or searches for it, the current name is more suitable than badger?

But I'm open for every suggestion, so maybe we can collect some ideas and make a poll? :)

  • Like 1
Link to comment
Share on other sites

Did quick test.

I don't see any Status in the results.

It doesn't see unpublished pages. It doesn't see hidden pages.

At the moment, the status(es) are displayed when a page is: unpublished, hidden, locked or trashed

So for a normal page there's no status.

I don't know, does it make sense to display also a status for the complement?

Published, not hidden, not locked, not trashed

Did you add "include=hidden" or "include=all" to your selector?

Link to comment
Share on other sites

It would be nice. No I didn't, but also thought it should add that anyway for all, or maybe a checkbox to include all?

I can't sort the columns. I think there's an option to enable it in the DataTable.

  • Like 1
Link to comment
Share on other sites

Just comitted v 1.0.1 to Github:

- Added checkboxes for include=hidden, include=all so you no longer need to write those in the selector

- Made AdminDataTable sortable

- Each status is now in its own column - this means you can also sort the results by status

- Added message: number of pages found


I initially disabled the sorting on the table because there was an issue with the checkbox in the first <th> which can be used to toggle all the checkboxes.

The solution is to disable the sorting of a specific column with jqueryTableSorter:

$.tablesorter.defaults.headers = {0:{sorter:false}};

...where 0 = first column, 1 = second and so on, should anyone else ever need this.

  • Like 5
Link to comment
Share on other sites

This looks like a great module Wanze!

I have a suggestion: It would be great to be able to click on the title of a page and open that page for editing in a lightbox overlay :) not sure how easy this is though.

I can see a great use for this as a quick SEO overview as the title, name (url) and parent (parent url) are shown. Further to that - it would be great to be able to have this available with reduced privileges for roles less than the superuser (with just the ability to see the list and perform actions applicable to their selected roles).

  • Like 1
Link to comment
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 Robin S
      This module lets you add some custom menu items to the main admin menu, and you can set the dropdown links dynamically in a hook if needed.
      Sidenote: the module config uses some repeatable/sortable rows for the child link settings, similar to the ProFields Table interface. The data gets saved as JSON in a hidden textarea field. Might be interesting to other module developers?
      Custom Admin Menus
      Adds up to three custom menu items with optional dropdowns to the main admin menu.
      The menu items can link to admin pages, front-end pages, or pages on external websites.
      The links can be set to open in a new browser tab, and child links in the dropdown can be given an icon.
      Requires ProcessWire v3.0.178 or newer.
      Example of menu items

      Module config for the menus

      Link list shown when parent menu item is not given a URL

      Setting child menu items dynamically
      If needed you can set the child menu items dynamically using a hook.
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $colours = $event->wire()->pages->findRaw('template=colour', ['title', 'url', 'page_icon']); $children = []; foreach($colours as $colour) { // Each child item should be an array with the following keys $children[] = [ 'icon' => $colour['page_icon'], 'label' => $colour['title'], 'url' => $colour['url'], 'newtab' => false, ]; } $event->return = $children; } }); Create multiple levels of flyout menus
      It's also possible to create multiple levels of flyout submenus using a hook.

      For each level a submenu can be defined in a "children" item. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $children = [ [ 'icon' => 'adjust', 'label' => 'One', 'url' => '/one/', 'newtab' => false, ], [ 'icon' => 'anchor', 'label' => 'Two', 'url' => '/two/', 'newtab' => false, 'children' => [ [ 'icon' => 'child', 'label' => 'Red', 'url' => '/red/', 'newtab' => false, ], [ 'icon' => 'bullhorn', 'label' => 'Green', 'url' => '/green/', 'newtab' => false, 'children' => [ [ 'icon' => 'wifi', 'label' => 'Small', 'url' => '/small/', 'newtab' => true, ], [ 'icon' => 'codepen', 'label' => 'Medium', 'url' => '/medium/', 'newtab' => false, ], [ 'icon' => 'cogs', 'label' => 'Large', 'url' => '/large/', 'newtab' => false, ], ] ], [ 'icon' => 'futbol-o', 'label' => 'Blue', 'url' => '/blue/', 'newtab' => true, ], ] ], [ 'icon' => 'hand-o-left', 'label' => 'Three', 'url' => '/three/', 'newtab' => false, ], ]; $event->return = $children; } }); Showing/hiding menus according to user role
      You can determine which menu items can be seen by a role by checking the user's role in the hook.
      For example, if a user has or lacks a role you could include different child menu items in the hook return value. Or if you want to conditionally hide a custom menu altogether you can set the return value to false. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); $user = $event->wire()->user; // For custom menu number 1... if($menu_number === 1) { // ...if user does not have some particular role... if(!$user->hasRole('foo')) { // ...do not show the menu $event->return = false; } } });  
    • By tcnet
      This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist.
      The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier.
      Notification email
      Specifies the email address to which the notification emails should be sent.
        Email subject
      Specifies the subject line for the notification email.
        Post variables
      Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass
        Server variables
      Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT
      Link to ProcessWire module directory:
      Link to github.com:
    • By Fokke
      ProcessWire 3.x markup module for rendering meta tags in HTML document head section. Note that this module is not a full-blown SEO solution, but rather a simple tool for rendering meta tags based on module configuration. Adding custom meta tags is also supported.
      Built-in meta tags
      The following meta tags are supported out-of-the-box:
      Document title consisting of page title and site name Character set Canonical Viewport Description Keywords Hreflang tags Open Graph og:title og:site_name og:type og:url og:description og:image og:image:width og:image:height Twitter meta tags twitter:card twitter:site twitter:creator twitter:title twitter:description twitter:image Facebook meta tags fb:app_id The full documentation with configurable options can be found here: https://github.com/Fokke-/MarkupMetadata
      ProcessWire>=3.0.0 PHP >=7.1 Installation using Composer
      composer require fokke/markup-metadata Manual installation
      Download latest version from https://github.com/Fokke-/MarkupMetadata/archive/master.zip Extract module files to site/modules/MarkupMetadata directory.
    • By m.sieber
      ITRK-Service for ProcessWire
      Module for the automated transfer of imprint, data protection declaration and terms and conditions from IT-Recht Kanzlei to your ProcessWire installation
      What is ITRK Service for ProcessWire?
      ITRK-Service for ProcessWire is a free module for ProcessWire CMS. It provides an interface to the update service of IT-Recht Kanzlei, via which the legal texts of your online presence are automatically updated. In this way, the texts remain legally secure and warning-proof in the long term. Imprint, data protection declaration, revocation and general terms and conditions are currently supported.
      You can find our documentation (in german language) here: https://www.pupit.de/itrk-service-for-processwire/dokumentation/

      Download: https://www.pupit.de/itrk-service-for-processwire/
      Github: https://github.com/pupit-de/pwItrkServiceConnector
    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
  • Create New...