Jump to content
Wanze

ProcessBatcher

Recommended Posts

Hi owzim

Thanks!

I see your point but I think this sort of functionality is hard to implement for a general, simple solution.

There are lot's of possible fields of different size. Displaying them below each other - it becomes the same as creating

a normal page and fill out the fields there. That's not really 'batch-creating' then IMO.

Check out niks After save actions module which lets you create a new page after saving.

If you have the need to let your users batch-create pages with a defined template, I'd go with a Process module.

You could build a form with the required fields and then create the pages with the API.

  • Like 2

Share this post


Link to post
Share on other sites

Hi @Wanze, I may be late to the party to thank you but nonetheless, thank you for this great Module—I am sure I am going to be using it.

  • Like 1

Share this post


Link to post
Share on other sites

There are lot's of possible fields of different size. Displaying them below each other - it becomes the same as creating

a normal page and fill out the fields there. That's not really 'batch-creating' then IMO.

You are right, my request might be beyond/off the scope of your module. Thank you for the other suggestions, will definitely check them out.

  • Like 1

Share this post


Link to post
Share on other sites

You are right, my request might be beyond/off the scope of your module. Thank you for the other suggestions, will definitely check them out.

I've been using this module to fill in a database of movies lately. Lets just say that there are "quite a few" of them and it's a lot of work. My point here is that since I happened to need a few custom fields that were always there, I modified module source just enough to include those -- no need for a generic option, just couple of lines of PHP and voilà: inserting movies just got a lot easier!

I'm sure this is not what you were looking for there, just wanted to point out that modifying code of this module like that is quite easy to do and can save a lot of time if you're facing importing a lot of data by hand. That's one benefit of free software / open source, you know..  ;)

  • Like 2

Share this post


Link to post
Share on other sites

I've been using this module to fill in a database of movies lately. Lets just say that there are "quite a few" of them and it's a lot of work. My point here is that since I happened to need a few custom fields that were always there, I modified module source just enough to include those -- no need for a generic option, just couple of lines of PHP and voilà: inserting movies just got a lot easier!

I'm sure this is not what you were looking for there, just wanted to point out that modifying code of this module like that is quite easy to do and can save a lot of time if you're facing importing a lot of data by hand. That's one benefit of free software / open source, you know..  ;)

I actually do that all the time, modifying jQuery plugins. But it always feels awkward and wrong to hack plugins/modules or even the core. But yeah, in this your this is a one time thing, since you would not modify the module for the actual live site but for the import process. But in your case you might even be better off using the api or the csv import module, no?

Share this post


Link to post
Share on other sites

Just used this to remove over 900 pages, while keeping about 50 valid pages. Saved at least hour of work. Just a brilliant module, thanks Wanze!

  • Like 3

Share this post


Link to post
Share on other sites

Batcher has saved me major time on a few occasions too. Definitely a must-have module. 

  • Like 2

Share this post


Link to post
Share on other sites

I actually do that all the time, modifying jQuery plugins. But it always feels awkward and wrong to hack plugins/modules or even the core. But yeah, in this your this is a one time thing, since you would not modify the module for the actual live site but for the import process. But in your case you might even be better off using the api or the csv import module, no?

You can always make a copy of a particular module, rename it and install it as a different module so you can change its functionality without losing the original or losing your changes if/when the original is updated. There is at least one thread in the forum on the subject but I can't find it just now, even thru Google.

  • Like 1

Share this post


Link to post
Share on other sites

Many thanks for this great module. This was I need. (And thanks to user @titanium for his recomendation)
I'd like to see in future versions, some default filters for non-technical user as generally are our clients, such as user @raydale suggested.
Best regards
Fernando

Share this post


Link to post
Share on other sites

Feature Request ;-)

It would really handy if the Batcher url under Setup was resource-oriented and stored the submitted Selector in the URL. That way you could bookmark the selectors that you reuse most often, or share very specific lists of content to team members etc simply by sharing a URL. 

-Brent

  • Like 2

Share this post


Link to post
Share on other sites

Hi Marty,

You can use the parent selector:

parent=/path/to/my_parent/
  • Like 1

Share this post


Link to post
Share on other sites

ProcessBatcher is in my 'site/modules' folder but doesn't show up, not in 'modules' nor 'setup'.

Logged in as Superuser PW 2.3. Checked for new modules, logged out & in again, all to no avail...

Share this post


Link to post
Share on other sites

That sounds strange. And other modules work fine?

Share this post


Link to post
Share on other sites

ProcessBatcher is in my 'site/modules' folder but doesn't show up, not in 'modules' nor 'setup'.

Logged in as Superuser PW 2.3. Checked for new modules, logged out & in again, all to no avail...

Is ProcessBatcher directory directly under site/modules or is the directory structure deeper than that? Just making sure as there's a built-in limit to directory depth, though this isn't something you'll usually need to worry about.

One thing you might want to try, even though checking for new modules should already handle this, is to remove all Modules* files from your /site/assets/cache/ just to make sure that module list is properly updated.

  • Like 2

Share this post


Link to post
Share on other sites

ProcessBatcher is in site/modules. I removed all Modules files from the site/assets/cache. Went to the admin modules page and ProcessBatcher was in the list so I happily clicked 'install. Then this happened:

Unable to complete this request due to an error. Error has been logged.

The logged error says:

 2013-09-30 05:44:31    ?    http://www.birthfactdeathcalendar.net/?/    Error:     Call to a member function getLoadQueryAutojoin() on a non-object (line 309 of /wire/core/Pages.php)

And now the complete website, admin and public are unavailable....

I just replaced the wire folder with a new one because of a previous error....

Share this post


Link to post
Share on other sites

Just a quick note: similar error is mentioned here, though in a slightly different context, so it might not necessarily be related to this issue at all. Still based on that thread it'd be nice to know a) which PHP version you have and b) are you using a cloud hosting platform or some other "regular" hosting, ie. typical web hotel or VPS?

Share this post


Link to post
Share on other sites

Since I started a complete new install of PW it shows up all well now. I guess my FTP application was the culprit.

Share this post


Link to post
Share on other sites

Thanks! This module is absolutely great! I really like the simplicity of it. The only thing I'm missing is a way save my selector searches for later use. I often return to do similar searches.

Share this post


Link to post
Share on other sites

Shouldn't it be possible to search with rootParent=/somesection/ with batcher?

Share this post


Link to post
Share on other sites

You should be able to use has_parent=/root-parent/, replacing 'root-parent' with the name of your root parent page. That's assuming that you want to match all pages that live within the root parent and their children, etc. If you just want children of that root parent, then you'd do parent=/root-parent/

Share this post


Link to post
Share on other sites

One of the greatest tools for big sites.

I only miss action "Change Field".

@Wanze - would be super to see this action in future updates. Thanks!

Share this post


Link to post
Share on other sites

This module is great. And when you see something like that you start dreaming of more and more...

I used Batcher to create a list of new pages. Could it be possible to import actual list of page titles (one title one line) in some textarea and get those new page inputs populated with those? We should choose a template for all those somehow too... Maybe make the "title" field in crete tab a textarea and apply all the other settings to the list (name autogenerated)?

Thank you for the timesaver anyway.

Share this post


Link to post
Share on other sites

You may better use Import CSV to pages module by Ryan then.

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