ntellisense

Right, but ACF is saving data as post meta, so everything is still built-in. But, this question is not specific to ACF or post meta really, but more of a general question about controlling, altering or adding to the content before it is synced by Jetpack. I want to know if there is a hook where we can add additional or arbitrary data to a post’s content before the content is synced by Jetpack.

• This reply was modified 5 years, 8 months ago by ntellisense.
• This reply was modified 5 years, 8 months ago by ntellisense.

https://live-pbh.pantheonsite.io/

JETPACK_STAGING_MODE is not being defined, it is running as a production site. Also, the same error occurs on the dev, test and live environment.

https://dev-pbh.pantheonsite.io/

This is Jetpack v7.1.1 on a Pantheon environment

I have added the constant definition as well as the port value, but the error remains. I’ve also tried defining the HTTP and HTTPS constant value similar to the below:

// I used the recommended server port value given by Jetpack
define( ‘JETPACK_SIGNATURE__HTTP_PORT’, 443 );
define( ‘JETPACK_SIGNATURE__HTTP_PORT’, 443 );

I’ve also tried this…

define( ‘JETPACK_SIGNATURE__HTTP_PORT’, $_SERVER[‘SERVER_PORT’] );
define( ‘JETPACK_SIGNATURE__HTTPS_PORT’, $_SERVER[‘SERVER_PORT’] );

to dynamically set these values on different environments, but I still get this error:

Debugging Center
Testing your site’s compatibility with Jetpack…
The server port value is unexpected.

Try adding the following to your wp-config.php file: define( ‘JETPACK_SIGNATURE__HTTP_PORT’, ‘THE PROVIDED PORT VALUE’ );

Also, when using the Jetpack Debug tool at https://jetpack.com/support/debug/ I get this error for the website:

Unknown error
An unknown error has occurred.

If you continue to get this error, please check out our troubleshooting guide or contact support.

• This reply was modified 5 years, 8 months ago by ntellisense.
• This reply was modified 5 years, 8 months ago by ntellisense.

Thanks, I was able to loop through all ACF custom fields and repeaters to find fields that were of the “file” type. Then, I checked if there was any index data for the file (meta_key: _relevanssi_pdf_content), and when there was, I added that data as additional post data using the relevanssi_indexing_data filter. I reused some of the code in the relevanssi_index_pdf_for_parent function to accomplish this.