Jump to content

Recommended Posts

ProcessWire InputfieldRepeaterMatrixDuplicate

Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.

This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.

Check out the screencast

What the module can do

  • Duplicate a repeater item from one page to another
  • No matter how complex the item is
  • Full support for file and image fields
  • Multilingual support
  • Support of Min and Max settings
  • Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button
  • Support of multiple RepeaterMatrix fields on one page
  • Configurable which roles and fields are excluded
  • Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published
  • Automatic clipboard update when other items are picked
  • Automatically removes old clipboard data if it is not pasted within 6 hours
  • Delete clipboard itself by clicking the selected item again
  • Benefit: unbelievably fast workflow and content replication

What the module can't do

  • Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated
  • Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely
  • No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item
  • Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event

Changelog
1.0.4

  • Bug fix: Various bug fixes and improvements in live synchronization
  • Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked
  • Feature: Support of multiple repeater fields in one page
  • Feature: Support of repeater Min/Max settings
  • Feature: Configurable roles and fields
  • Enhancement: Improved clipboard management
  • Enhancement: Documentation improvement
  • Enhancement: Corrected few typos #1

1.0.3

  • Feature: Live synchronization
  • Enhancement: Load the module only in the backend
  • Enhancement: Documentation improvement

1.0.2

  • Bug fix: Various bug fixes and improvements in JS functions
  • Enhancement: Documentation improvement
  • Enhancement: Corrected few typos

1.0.1

  • Bug fix: Various bug fixes and improvements in the duplication process

1.0.0

  • Initial release

Support this module

If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)

Download this module

> Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
> PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/

Edited by David Karich
Now in PW module direcotory
  • Like 20
  • Thanks 1

Share this post


Link to post
Share on other sites

Wow, that's awesome.

Yes, this would be great to have in the RM core indeed.

btw: How did you build the CKE dropdown for lorem ipsum paragraphs?

Share this post


Link to post
Share on other sites
8 minutes ago, kongondo said:

Nice! 

What admin theme is that?

AdminTheme Boss with some customizations. 😊

  • Like 2

Share this post


Link to post
Share on other sites

WOW!! Jaw dropped here... I'm really impressed, David! This module and the admin settings you built look incredible.

Dumb question: how did you create those matrix thumbnails?

  • Like 2

Share this post


Link to post
Share on other sites

Nice! We know what you were doing in the last few months 🙂

  • Like 1

Share this post


Link to post
Share on other sites

Awesome!! I'm also interested in how you changed the Repeater Matrix labels to images 🙂

Share this post


Link to post
Share on other sites

I guess it's just CSS?

a.InputfieldRepeaterAddLink.InputfieldRepeaterMatrixAddLink.InputfieldRepeaterAddLinkInit[data-type="3"] {
	font-size: 0;
	width: 150px;
	height: 100px;
	display: inline-block;
	background-image: url(https://via.placeholder.com/150);
	background-repeat: no-repeat;
}

span.ui-priority-secondary {
	display: none;
}

 

  • Like 8

Share this post


Link to post
Share on other sites
44 minutes ago, dragan said:

I guess it's just CSS?


a.InputfieldRepeaterAddLink.InputfieldRepeaterMatrixAddLink.InputfieldRepeaterAddLinkInit[data-type="3"] {
	font-size: 0;
	width: 150px;
	height: 100px;
	display: inline-block;
	background-image: url(https://via.placeholder.com/150);
	background-repeat: no-repeat;
}

span.ui-priority-secondary {
	display: none;
}

 

Exactly. It's just a bit custom CSS. 👍 It might also be an idea for a matrix update that you can configure labels as images.  Would be more flexible.

  • Like 6

Share this post


Link to post
Share on other sites
1 minute ago, David Karich said:

It might also be an idea for a matrix update that you can configure labels as images.  Would be more flexible.

Yep. And add a nice touch to convert automagically label/link-texts to title attributes, so when the author hovers over an image, he knows exactly what kind of matrix item he/she will add.

  • Like 2

Share this post


Link to post
Share on other sites

I have started a topic in Repeater Matrix closed support board with a request to make it possible to override InputfieldRepeaterMatrix::renderFooter method in a hook. This way we can probably implement any kind of add content type design without css overrides.

  • Like 4

Share this post


Link to post
Share on other sites

Version Update 1.0.3

The current version 1.0.3 has some minor improvements. Items are inserted at the last position on the target page and set to the status unpublished. Furthermore, the clipboard is synchronized live, so you can jump between browser tabs without reloading the target page, for direct pasting. And the module runs only in the backend in the autoload.

> Grap a copy: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDublicate

Edited by David Karich
Version Update 1.0.3
  • Like 4

Share this post


Link to post
Share on other sites

Version Update 1.0.4

The current version has got some improvements, bug fixes and new features. Meanwhile a bit further than just a proof of concept. I would call it a beta version. I now submit it to the PW directory.

IMPORTANT for an update from older versions: completely uninstall and delete the old versions! Only then install the new version.

All information and downloads are updated in the first post.

@kongondo Can you please move this topic under "Modules"? I think the module is out of development. Thanks a lot.

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, David Karich said:

@kongondo Can you please move this topic under "Modules"? I think the module is out of development. Thanks a lot.

Done 🙂

  • Like 1

Share this post


Link to post
Share on other sites

great module @David Karich, thx!

will there be an option to cross-copy-paste content between two different matrix-repeater-fields with same matrix-repeater-field-types (same configuration)?
is or is this not possible?

Share this post


Link to post
Share on other sites
16 hours ago, ngrmm said:

great module @David Karich, thx!

will there be an option to cross-copy-paste content between two different matrix-repeater-fields with same matrix-repeater-field-types (same configuration)?
is or is this not possible?

Thank you, I'm glad it's useful to you and thank you for your donation. 🙂 

Unfortunately, cross-copying is not possible because at the point where you initialize the copy, the module does not know the name of the other field. So it can only read the current name of the matrix field and use this name when copying to the target. I'll think about whether you can introduce an option to select the target field before copying. But I think there is a lot of potential for errors when copying.

So first of all, unfortunately not possible at the moment.

BTW, @ryan, the module has been in checking for the module directory for several months now and has not yet been released. Does this module bother you in the context of a free extension for your ProModule?

  • Like 2

Share this post


Link to post
Share on other sites

@David Karich thanks for this valuable module.

It is exactly what I need for the site I am now working on!

@ryan could this be integrated into the repeater matrix module? Would be awesome!

  • Like 1

Share this post


Link to post
Share on other sites

@David Karich I think I may have found a bug.

When I click the copy button I get the popup overlay, which when I click on OK does NOT go away.

I tried on firefox and on chrome, I am on PW 3.0.148 current master

Only way I can move on to next item is when I refresh the page

Question: would it be possible to extend your module with option for multiselect repeater matrix items?

Share this post


Link to post
Share on other sites
On 4/25/2020 at 12:05 PM, OllieMackJames said:

@David Karich I think I may have found a bug.

When I click the copy button I get the popup overlay, which when I click on OK does NOT go away.

I tried on firefox and on chrome, I am on PW 3.0.148 current master

Only way I can move on to next item is when I refresh the page

Question: would it be possible to extend your module with option for multiselect repeater matrix items?

Hey @OllieMackJames thank you, also for the donation. I think it came from you? 🍻

I'm not able to reproduce the problem with the prompt. Does the DeveloperConsole give you any JS Errors?

I had tried to implement the multiselect function before. But I failed on some points because it was not stable and reliable and in the end there were too many dirty JS hacks. Originally, this module was just a proof of concept, with the hope that @ryan would implement this function cleanly into the core of RepeaterMatrix. The needs for this feature are already quite high for the users.

  • Like 2

Share this post


Link to post
Share on other sites
2 hours ago, David Karich said:

Hey @OllieMackJames thank you, also for the donation. I think it came from you? 🍻

I'm not able to reproduce the problem with the prompt. Does the DeveloperConsole give you any JS Errors?

I had tried to implement the multiselect function before. But I failed on some points because it was not stable and reliable and in the end there were too many dirty JS hacks. Originally, this module was just a proof of concept, with the hope that @ryan would implement this function cleanly into the core of RepeaterMatrix. The needs for this feature are already quite high for the users.

Yes, that was me via paypal.

Console says: Empty string passed to getElementById().

The message stays on top and only goes away when I refresh the page.

Share this post


Link to post
Share on other sites

@David Karich Thank you for a good module. Your templates-setup also looks very good. 

I noticed you use Admin Theme Boss. But how do you achieve those very nice looking "View", "Save Only" and "Publish" buttons to the left?

 

image.png.1a6acbc92716fafe8e2b8ada024dba63.png

Share this post


Link to post
Share on other sites

@David Karich i remember using this module and everything was fine. I wanted to use it again but the copy icon doesn't show up anymore after installing the module. am i missing something?
pw 3.0.148 and tested with matrixrepeater v4 and v5

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