This plugin allows you to clone flexible content blocks (layouts) to another page or site.
\nThe entire contents of block will be transferred, including repeater items and its contents.<\/p>\n
It uses a regular clipboard to store content, so you can paste it to notepad application and use it later to populating other pages.<\/p>\n
Simply install and activate the plugin. No settings available.<\/p>\n
The plugin will add a new option \u201cCopy layout\u201d to the header of each layout, and new menu at the bottom of the flexible container.<\/p>\n
Click on \u201cCopy layout\u201d option will copy the content of the block to the clipboard.
\nIn the bottom menu on target page use \u201cPaste layouts\u201d option and new blocks will appear.
\nNothing is saved unless you click the regular \u201cUpdate\u201d button.<\/p>\n
Bottom menu contains \u201cCopy all layouts\u201d to copy the entire flexible container to the clipboard.<\/p>\n
As a feature, this plugin will try to recognize the URLs in the pasted content and replace the source domain with the target one.
\nThis is often required when moving blocks from a staging to a live environment to keep links local.<\/p>\n
This will not transfer media or posts.
\nCoping fields that use ID-s to refer to a content (such as: media images, links, relationship\u2026) to another website may link the wrong resource to the field because posts\/media on another site may have different ID-s.
\nIn this case you must manually edit such fields and connect appropriate media\/posts.<\/p>\n
Only built-in field types are supported and tested.
\nAdditional (extended) field types are likely to be copied as well, but without guarantees.<\/p>\n
This plugin contains code form other GPLv2 projects, credits go to:
\n \u2013 https:\/\/www.acf-extended.com
\n \u2013 https:\/\/wordpress.org\/plugins\/acf-flexible-layouts-manager
\n \u2013 https:\/\/github.com\/magicstickuk\/Flexible-Content-Duplication<\/p>\n
\u201cACF-extended\u201d has similar feature, but it didn\u2019t work on any of 20 sites I tested, probably because of the way how the flexible container is integrated into the project.
\nSo I created a solution that works for me and shared publicly with everyone with the same problem.<\/p>\n