ACF options importer/exporter

Import and export ACF field date from the database directly.

1. Table of Contents

• 1. Table of Contents
• 2. About The Project
  • 2.1. Built With
  • 2.2. Installation
• 3. Usage
  • 3.1. [andyp_labs_stack]
  • 3.2. [andyp_labs_rest]
• 4. Customising
• 5. Troubleshooting
• 6. Contributing
• 7. License
• 8. Contact

2. About The Project

Allows you to specify a comma separated list of options fields DATA to export to a json file.

You can then import that json file back into the database.

This is a super-dumb sql dump of all fields from the database with the name of your fields.

Why?

I have a load of data filled in on my development installation and want to port over all of the records to my staging and live servers without having to re-create all records by hand. This allows me to just dump all of the fields out of the wp_options table in wordpress and import them into another installation quite quickly.

(back to top)

2.1. Built With

This project was built with the following frameworks, technologies and software.

• ACF
• PHP
• Wordpress
• Composer

(back to top)

2.2. Installation

These are the steps to get up and running with this plugin.

1. Clone the repo into your wordpress plugin folder

   git clone https://github.com/IORoot/wp-plugin__acf--inline-datetime-field ./wp-content/plugins/acf_datetime_inline
   

2. Activate the plugin.

(back to top)

3. Usage

A new menu item will appear under the ACF 'custom fields' menu call 'ACF import/export'.

Exporting

Supply a comma separated list of field names to export.

my_field1, myrepeater, my_text_area1

Click export, and save the options.json file.

Importing

Click on the button to upload your options.json file. Note it MUST be called options.json to work.

Click import.

WARNING - ALL  EXISTING FIELDS OF THE SAME NAME WILL BE OVERWRITTEN.

Repeaters

This is very handy for repeater fields. I usually place most things into top-level repeater fields. I can just specify the name of the top-level repeater field and it will automatically grab all sub fields as well.

Warnings

1. The import function runs a insert_option function on every record it finds in the json file.
2. The file to import MUST be called options.json. I know, thats lame, but it'll have to do for now.
3. I've used it with repeaters, groups, selects, text and textarea fields. It Should be ok with others, but haven't tested it.

4. Customising

No customisation required.

5. Troubleshooting

Nope. If you want to do some changes and make a merge request, go for it. But this is for my own purposes.

(back to top)

6. Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue. Don't forget to give the project a star! Thanks again!

1. Fork the Project
2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
3. Commit your Changes (git commit -m 'Add some AmazingFeature')
4. Push to the Branch (git push origin feature/AmazingFeature)
5. Open a Pull Request

(back to top)

7. License

Distributed under the MIT License.

MIT License

Copyright (c) 2022 Andy Pearson

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

(back to top)

8. Contact

Author Link: https://github.com/IORoot

(back to top)