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 MoritzLost
      This is a new module that 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) 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.
      Beta release
      Note that I consider this a Beta release. Since the module is relatively aggressive in deleting some caches, I would advise you to install in on a test environment before using it on a live site.
      Let me know if you're getting any errors, have trouble using the module or if you have suggestions for improvement!
      In particular, can someone let me know if this module causes any problems with the ProCache module? I don't own or use it, so I can't check. As far as I can tell, ProCache uses a folder inside the cache directory to cache static pages, so my module should be able to clear the ProCache site cache as well, I'd appreciate it if someone can test that for me.
      Future plans
      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

    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="optin" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="optin" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: https://github.com/blaueQuelle/privacywire/tree/master
      Download: https://github.com/blaueQuelle/privacywire/archive/master.zip
      I would love to hear your feedback 🙂
      Edit: Updated URLs to master tree of git repo
       
    • By David Karich
      Admin Page Tree Multiple Sorting
      ClassName: ProcessPageListMultipleSorting
      Extend the ordinary sort of children of a template in the admin page tree with multiple properties. For each template, you can define your own rule. Write each template (template-name) in a row, followed by a colon and then the additional field names for sorting.
      Example: All children of the template "blog" to be sorted in descending order according to the date of creation, then descending by modification date, and then by title. Type:
      blog: -created, -modified, title  Installation
      Copy the files for this module to /site/modules/ProcessPageListMultipleSorting/ In admin: Modules > Check for new modules. Install Module "Admin Page Tree Multible Sorting". Alternative in ProcessWire 2.4+
      Login to ProcessWire backend and go to Modules Click tab "New" and enter Module Class Name: "ProcessPageListMultipleSorting" Click "Download and Install"   Compatibility   I have currently tested the module only under PW 2.6+, but think that it works on older versions too. Maybe someone can give a feedback.     Download   PW-Repo: http://modules.processwire.com/modules/process-page-list-multiple-sorting/ GitHub: https://github.com/FlipZoomMedia/Processwire-ProcessPageListMultipleSorting     I hope someone can use the module. Have fun and best regards, David
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "https://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


×
×
  • Create New...