Download the PHP package kodie/migrate-acf-field-data-to-repeater without Composer
On this page you can find all versions of the php package kodie/migrate-acf-field-data-to-repeater. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download kodie/migrate-acf-field-data-to-repeater
More information about kodie/migrate-acf-field-data-to-repeater
Files in kodie/migrate-acf-field-data-to-repeater
Package migrate-acf-field-data-to-repeater
Short Description A WordPress plugin that adds the `wp migrate-acf-field-data-to-repeater` command to WP CLI. That command renames the keys of metadata so that they are prepended with the repeater slug so that the fields can be moved into a repeater along with their data.
License MIT
Homepage https://github.com/kodie/migrate-acf-field-data-to-repeater
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package migrate-acf-field-data-to-repeater
Migrate ACF Field Data to Repeater WP CLI Command
Warning: This plugin and command should be considered experiemental. Use at your own risk. Be sure to test thoroughly before using in a production environment.
A WordPress plugin that adds the wp migrate-acf-field-data-to-repeater command to WP CLI. That command renames the keys of metadata so that they are prepended with the repeater slug so that the fields can be moved into a repeater along with their data.
For example: I have a field created with ACF named item_description and I have been using it on pages so that field has content in it on multiple pages. Later on I decided that I want a repeater field named items and I want item_description to be in that repeater. Well, I can easily drag the field into the repeater and there we go! Except, not really. The previously entered data for item_description will not appear in the new repeater field. That's where this command comes into play.
Use this command after you have already created your new repeater field and moved the fields you with to migrate into the repeater from the Custom Fields page.
wp migrate-acf-field-data-to-repeater <repeater_slug> <repeater_field_id> <field_slug...> [--dry-run] [--post_type=POST_TYPE] [--include=POST_ID,POST_ID,POST_ID...]
repeater_slug- The "name" field for the repeater. Example:itemsrepeater_field_id- This is the field ID for the repeater. To find this, you'll need to go to a page on the WordPress backend that has the field, inspect the element, and it should be in theforattribute for the repeater label prepended with "field_". Example:636d5921b3451field_slug- The "name" field for the field(s) you wish to move into the repeater. Seperate multiple slugs with a space. Example:item_title item_description--dry-run- Set this option to display the results without actually making any changes.--post_typeand--include- You can actually use any options to pass to the get_posts function. Seperate multiple values with a comma. Example:--post_type=page --include=47,82 --author_name=bob
Command example:
Easily install, activate, and use the plugin via:
Thanks
This plugin was originally inspired by this gist by @gthayer.
License
MIT. See the license.md file for more info.
