Allow use_filters change when creating post

[xipasduarte]

Context

This was an issue encountered while using the Distributor plugin, but fixing it can allow for greater compatibility with other plugins. When duplicating a post provide a way to enable filtering the original data that gets copied (post data, meta values and terms).

We opted not to include all instances of use_filters because one was already addressed in #244, even though the filter's name might need some adjusting.

Summary

This PR can be summarized in the following changelog entry:
Adds a new filter duplicate_post_create_duplicate_use_filters to enable filtering the original data that gets copied (post data, meta values and terms).

Relevant technical choices:

The prefix for the filter name was kept consistent with the rest of the plugin, while adding specific details with function and property being filtered.

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

• Enable data filtering on create:

// Uses WordPress' global functions.
add_filter( 'duplicate_post_create_duplicate_use_filters', '__return_true' );

• Add some meta to be excluded

public function exclude_meta_keys( array $meta_keys ) : array {
	// Replace this meta key according to your setup.
	$meta_keys[] = 'excluded_meta_key';
	return $meta_keys;
}

add_filter( 'duplicate_post_excludelist_filter', 'exclude_meta_keys' );

• Duplicate and check that the 'excluded_meta_key' is not present in the new post.

Relevant test scenarios

• Changes should be tested with the browser console open
• Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
• Changes should be tested on different editors (Block/Classic/Elementor/other)
• Changes should be tested on different browsers
• Changes should be tested on multisite

Test instructions for QA when the code is in the RC

• QA should use the same steps as above.

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

• None that we could find.

UI changes

• This PR changes the UI in the plugin. I have added the 'UI change' label to this PR.

Documentation

• I have written documentation for this change.

Quality assurance

• I have tested this code to the best of my abilities
• I have added unittests to verify the code works as intended

Fixes #204

[grappler]

Thank you @xipasduarte for working on this PR.

I don't think this is the right solution as all of the filters will be activated. There is no way of only activating certain filters.

duplicate-post/src/post-duplicator.php

Lines 101 to 111 in 1b790c1

	if ( $options['use_filters'] ) {
	/**
	* Filter new post values.
	*
	* @param array $new_post New post values.
	* @param WP_Post $post Original post object.
	*
	* @return array
	*/
	$new_post = \apply_filters( 'duplicate_post_new_post', $new_post, $post );
	}

duplicate-post/src/post-duplicator.php

Lines 207 to 216 in 1b790c1

	if ( $options['use_filters'] ) {
	/**
	* Filters the taxonomy excludelist when copying a post.
	*
	* @param array $taxonomies_excludelist The taxonomy excludelist from the options.
	*
	* @return array
	*/
	$taxonomies_excludelist = \apply_filters( 'duplicate_post_taxonomies_excludelist_filter', $taxonomies_excludelist );
	}

duplicate-post/src/post-duplicator.php

Lines 257 to 266 in 1b790c1

	if ( $options['use_filters'] ) {
	/**
	* Filters the meta fields excludelist when copying a post.
	*
	* @param array $meta_excludelist The meta fields excludelist from the options.
	*
	* @return array
	*/
	$meta_excludelist = \apply_filters( 'duplicate_post_excludelist_filter', $meta_excludelist );
	}

duplicate-post/src/post-duplicator.php

Lines 283 to 292 in 1b790c1

	if ( $options['use_filters'] ) {
	/**
	* Filters the list of meta fields names when copying a post.
	*
	* @param array $meta_keys The list of meta fields name, with the ones in the excludelist already removed.
	*
	* @return array
	*/
	$meta_keys = \apply_filters( 'duplicate_post_meta_keys_filter', $meta_keys );
	}

[xipasduarte]

@grappler Hello, I understand, but what you're saying is a level deeper. We could make this into a map that enables each use of $options['use_filters'] with more granularity. Something like:

[
	'use_case_1' => true,
	'use_case_2' => false,
]

This would then allow us to change the conditions to:

if ( $options['use_filters']['use_case_1'] ) {
	// Run use_case_1
}

Let me know if you have any other suggestions.