Jump to content
Wanze

ProcessBatcher

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

Editing

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

Creating

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:

http://processwire.com/talk/topic/2138-process-tools-create-pages-wip/

Cheers

  • Like 35

Share this post


Link to post
Share on other sites

Wanze, you are a legend, have you been reading the Wishlist/Roadmap? ;)

Will check this out hopefully tomorrow, have a great Friday evening!

  • Like 1

Share this post


Link to post
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

Share this post


Link to post
Share on other sites

to make it still harder for you teppo, imagine your clients doing the badger dance after realizing how great PW is ;)

-Mushroom

good work btw Wanze, very handy module for developing.

Share this post


Link to post
Share on other sites

"Do the ProcessWire

And get your Profits higher

Do the ProcessWire

Do the ProcessWire

"Your coding's on fire

With ProcessWire

Do the ProcessWire

Do the ProcessWire"

  • Like 1

Share this post


Link to post
Share on other sites

Looks like we will see you in the recall Joss, pretty Good performed. You just have to work on your Dancing skills.

  • Like 1

Share this post


Link to post
Share on other sites

Herr Luis!

Strange you should say this. 

My company: http://www.dancingbear.co.uk

(Warning, NEVER go to the dot com. It used to be owned by a lady who sold knitting patterns, but then it got bought by a porn company. Damn it!)

  • Like 1

Share this post


Link to post
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

@SiNNut

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

Share this post


Link to post
Share on other sites

Haha, i've got no probs with batcher....just joking...most important thing is what it does

Other options:

PW_BulkEdit

PW_Bulker

PW_MassEdit

  • Like 1

Share this post


Link to post
Share on other sites

Great module Wanze! Thanks for making this. Definitely going to come in handy. 

  • Like 1

Share this post


Link to post
Share on other sites

You're very welcome Marty!

Enjoy your bacon. ;)

Share this post


Link to post
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.

Share this post


Link to post
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?

Share this post


Link to post
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

Share this post


Link to post
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


post-582-0-09027000-1361218014_thumb.png

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

Share this post


Link to post
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

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-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 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 Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...