Parsely integration not compatible with wp-parsely 3.17

[dlh01]

Description of the bug

The "Show Trending Content from Parsely" option in the query block does not work correctly with version 3.17 of the Parsely plugin. It looks like the Analytics_Posts_API class, which the integration depends on, was removed in that version (see Parsely/wp-parsely#2889).

Steps To Reproduce

Configure a WP Curate query block with "Show Trending Content from Parsely" enabled and no other parameters, and observe that the block displays a reverse-chron list of posts.

Additional Information

No response

[kevinfodness]

Looks like the class was replaced with Parsely\Services\Content_API\Content_API_Service. It seems like we might need to do the following instead of creating a new instance of Analytics_Posts_API:

$parsely_content_api = $GLOBALS['parsely']->get_content_api();
$parsely_content_api->get_posts( /* args */ );

[kevinfodness]

Also, we should ensure we support both v3.16 and below as well as v3.17 and above, so we should try to use the get_content_api method first, and if it doesn't exist, then fall back to the Analytics_Posts_API method that we were using previously, or switch to making the REST API call to Parse.ly directly, using the authentication information that the plugin provides.

[dlh01]

WIP branch: https://github.com/alleyinteractive/wp-curate/compare/fix/gh-281/parsely?expand=1

[dlh01]

#283 didn't address this correctly and led to a fatal error.

Apparently, prior to version 3.17, the section argument could be either a string or array. a string:

wp-curate/src/features/class-parsely-support.php

Lines 98 to 106 in 450d001

	if ( isset( $args['tax_query'] ) && is_array( $args['tax_query'] ) ) {
	foreach ( $args['tax_query'] as $tax_query ) {
	if ( isset( $tax_query['taxonomy'] ) && $parsely_options['custom_taxonomy_section'] === $tax_query['taxonomy'] ) {
	$parsely_args['section'] = implode( ', ', $this->get_slugs_from_term_ids( $tax_query['terms'], $tax_query['taxonomy'] ) );
	}
	if ( isset( $tax_query['taxonomy'] ) && 'post_tag' === $tax_query['taxonomy'] ) {
	$parsely_args['tag'] = implode( ', ', $this->get_slugs_from_term_ids( $tax_query['terms'], $tax_query['taxonomy'] ) );
	}
	}

In version 3.17, a fatal error occurs because the plugin treats section as an array:

This error can be triggered using a query that has a category selected. It's an inconvenient error because it occurs in the internals of the plugin, and I have to wonder whether other similar cases are lurking. Perhaps the direct API call that @kevinfodness suggested is the safer approach.