Jump to content
adrian

Batch Child Editor

Recommended Posts

@antpre - I've just committed a new version - field pairings will now work regardless of the "ignore first row" setting. Please try it out when you get a chance and let me know if you still have any problems.

  • Like 1

Share this post


Link to post
Share on other sites

@adrian, tested it just now with the new version. It worked like a charm.
Thanks

  • Like 1

Share this post


Link to post
Share on other sites

Hi everybody,

I am running in a problem when I try to import a date into a dateTime field type (the fields remain blank after the import, if I import the same data in a standard text field the import result is ok).

Is the DateTime field type supported in the CSV import function of BCE ?
Thanks & stay safe

Share this post


Link to post
Share on other sites

@antpre - it's working for me with some simple testing. What format is the date in the CSV? What about the settings of the datetime field that it is being imported into - anything special?

Share this post


Link to post
Share on other sites

@adrian the date in the csv is dd/mm/yyyy and the datetime field is input format is set to the same.

But thanks for the pointer. I will dig a bit on fromat tomorrow.

Regards

Share this post


Link to post
Share on other sites
Just now, antpre said:

@adrian the date in the csv is dd/mm/yyyy and the datetime field is input format is set to the same.

But thanks for the pointer. I will dig a bit on fromat tomorrow.

Regards

I tried both timestamp and YYYY-MM-DD and they worked fine, so I expect that will be the issue.

Share this post


Link to post
Share on other sites
On 12/13/2019 at 6:55 AM, pullasuti said:

Hello. Not the greatest first post, but here we go 🙂

I'm having a small issue exporting to CSV. Every export begins with an error relating to pagesToInclude:

<br />
<b>Notice</b>:  Undefined index: pagesToInclude in <b>...\site\assets\cache\FileCompiler\site\modules\BatchChildEditor\ProcessChildrenCsvExport.module.php</b> on line <b>112</b><br />

This happens regardless of whether I set a rule for the pages to be included or not. Otherwise the export works, but need manual removal of the first two lines.

Any good ideas?

I've just tried exporting some pages and I'm getting the same error as above in the exported csv file. Then when I try and reimport the csv it's only importing the first line of the csv file.

I've tried uninstalling/resinstalling the module but to no effect.

Share this post


Link to post
Share on other sites

@houseofdeadleg - can you send me the module settings data - this module (http://modules.processwire.com/modules/module-settings-import-export/) makes it really easy. Otherwise, if you have Tracy installed, open up the BCE module settings page and then open the Adminer panel and copy the json from the data field.

Can you also post (here or PM) the CSV that you are trying to import that only imports the first line.

Share this post


Link to post
Share on other sites

@adrian settings info is below. I've just noticed, after reading through a few other recent posts, that I don't seem to have the field pairing options – something that would be really useful.

{"BatchChildEditor":{"version":"1.8.20","settings":{"enabledTemplates":[],"enabledPages":[],"configurablePages":[],"editModes":["edit","add","update","replace","export"],"defaultMode":"edit","overwriteNames":"","allowOverrideOverwriteNames":"","disableContentProtection":"","allowTemplateChanges":"","allowAdminPages":"","trashOrDelete":"trash","listerDefaultSort":"sort","listerColumns":["title","path","modified","modified_users_id"],"defaultFilter":"","listerConfigurable":null,"csvOptions":["upload"],"csvOptionsCollapsed":[],"csvImportFieldSeparator":",","csvImportFieldEnclosure":"\"","ignoreFirstRow":"","importMultipleValuesSeparator":"|","newImageFirst":"","allowOverrideCsvImportSettings":"","csvExportFieldSeparator":",","csvExportFieldEnclosure":"\"","csvExportExtension":"csv","columnsFirstRow":1,"exportMultipleValuesSeparator":"|","formatExport":"","allowOverrideCsvExportSettings":"","position":"newTab","insertAfterField":false,"removeChildrenTab":1,"loadOpen":null,"openMethod":"normal","tabName":"Batch Child Editor","editModeTitle":"Edit Child Pages","editModeDescription":"You can edit the page titles, sort, delete, add new, or edit pages in a modal popup.","editModeNotes":"","listerModeTitle":"List Child Pages","listerModeDescription":"View child pages in a Lister interface.","listerModeNotes":"","addModeTitle":"Add Child Pages","addModeDescription":"Editing this field will add all the child page titles listed here to the existing set of child pages.","addModeNotes":"Each row is a separate page.\n\nYou can also use CSV formatted lines for populating all text/numeric fields on the page, eg:\n\"Bolivia, Plurinational State of\",BO,\"BOLIVIA, PLURINATIONAL STATE OF\",BOL,68","updateModeTitle":"Update Child Pages","updateModeDescription":"Editing this field will update the field values of the pages represented here.","updateModeNotes":"WARNING: If you use this option, the content of all fields in existing pages will be replaced.\n\nEach row is a separate page.\n\nYou can also use CSV formatted lines for populating all text/numeric fields on the page, eg:\n\"Bolivia, Plurinational State of\",BO,\"BOLIVIA, PLURINATIONAL STATE OF\",BOL,68","replaceModeTitle":"Replace Child Pages","replaceModeDescription":"Editing this field will replace all the child page titles represented here.","replaceModeNotes":"WARNING: If you use this option, all the existing child \\ProcessWire\\pages(and grandchildren) will be deleted and new ones created.\n\nEach row is a separate page.\n\nYou can also use CSV formatted lines for populating all text/numeric fields on the page, eg:\n\"Bolivia, Plurinational State of\",BO,\"BOLIVIA, PLURINATIONAL STATE OF\",BOL,68","exportModeTitle":"Export Child Pages","exportModeDescription":"Creates a CSV file with one row for each child page.","exportModeNotes":"","uninstall":"","submit_save_module":"Submit"}}}

I can't share the csv file I'm afraid.

Share this post


Link to post
Share on other sites

Thanks @houseofdeadleg for those settings.

1) Testing here I am not seeing any problems, but I have committed a new version that should fix that notice that is showing up in your CSV export.

2) The field pairing options are available if you define Configurable Pages under the "Where editing tools are available and separately configurable" section. You then define the field pairing on the settings tab of the page whose children you are exporting.

3) You don't need to share sensitive data - please just create a minimum test case CSV file that shows the problem with only the first line importing. Also, are you on Windows, Linux, or MacOS? I am thinking it might be a lined ending issue. Also, what PHP version are you running?

 

Share this post


Link to post
Share on other sites

Dear Adrian,

Does the export function of BCE supports multi language text fields ? I saw you mentioning in this threat that it would be a good addition. But not sure whether you implemented it or not.

Thanks again for the great module.

Share this post


Link to post
Share on other sites

OK got my answer lol.

BCE exports the value in the language of the user. Clever !!!

TKS

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