update key/name for specific post types?

[adaptifyDesigns]

Hi, thanks for maintaining a great ACF solution script!

I am updating a website where there is currently an ACF field group which is applied to several different custom post types, but now I will be using the acf_add_local_field_group function to dynamically create similar field groups, and applying each unique field group to each unique custom post type.

For example, there used to be a field with:

$field = array(
    key => 'field_a8t092sthaoer7',
    name => 'some_awesome_field',
);

And this field is used by 4 post types: 'books', 'movies', 'tv-shows', and 'video-games'.

Now there will be the following 4 fields:

$books = array(
    key => 'field_books_some_awesome_field',
    name => 'books_some_awesome_field',
);

$movies = array(
    key => 'field_movies_some_awesome_field',
    name => 'movies_some_awesome_field',
);

$tv_shows = array(
    key => 'field_tv-shows_some_awesome_field',
    name => 'tv-shows_some_awesome_field',
);

$video_games = array(
    key => 'field_video-games_some_awesome_field',
    name => 'video-games_some_awesome_field',
);

And each of the above fields will be used only by their corresponding post type.

I'm wondering if your script can target a specific post type when updating keys and field names.

If not, perhaps you could point me in the right direction to figuring this out. I'm fairly proficient with PHP, but have never done any direct database manipulation. Any help is much appreciated.

Cheers!
Colin

[stevep]

@adaptifyDesigns Thanks for your interest and kind words and I apologize for taking so long to respond. As I state in the README I haven't really tested this in production, you might be the first! It is pretty bare bones, I wrote it in anticipation of upcoming projects where I needed to do some refactoring, but haven't had the change yet.

The code is all pretty simple. You can see how the posts get loaded here in getPosts. Right now it is pulling in all posts. Ideally we'd be able to pass some get_posts arguments to it. That way you could filter based on post type. getPosts is a protected function and is called by getSubjects which is public. I'd love to add some way to pass the arguments of all WordPress object types but not sure the cleanest way yet. Any ideas? This was just my first stab to pass the tests.

In the short term, my solution for you would be to just subclass the FieldMigration class and overwrite the getPosts and getSubjects functions and return what you want. Maybe one subclass for each custom post type?

[adaptifyDesigns]

@stevep Thanks for your response! I wish I could fork this and help with some new features, but I decided on another solution for my current project and I'm totally swamped with it at the moment.

I decided to rewrite my template files to fall back on older meta data if the newer post meta didn't exist. Using both the new and old post meta will facilitate a smooth transition to our new system, and enable us to still use older posts, without having to update all of them. And since the new fields are checked for first, only the older posts experience a slight drop in page load performance.

Anyway, I really appreciate your response, and your work on this script. I may very well circle back to it in the future.

Cheers!