Kevin Fodness

A .papi file is just a text file, and you can create it manually, and you can enter its contents manually on the settings screen. More information with an example is available on the wiki: https://github.com/alleyinteractive/apple-news/wiki/configuration#api-settings

I believe this is an error with WordPress 6.4 itself: https://core.trac.www.ads-software.com/ticket/59842

From the updates in the ticket, I would expect there to be a 6.4.1 release that will include this fix sometime soon.

Moving this over to GitHub to consolidate the discussion: https://github.com/alleyinteractive/apple-news/issues/935

1) If it can’t fetch a list of sections, then your API credentials are not correct. I would recommend following the instructions here on creating a .papi file and validating it on the command line before attempting to add the credentials to your site:

https://github.com/alleyinteractive/apple-news/wiki/configuration#api-settings

2) This is the same problem as #1.

3) This is likely the debug setting in Apple News > Settings within WordPress. You can disable debug mode and remove your email address from receiving notifications on publish.

In order to preview articles before submitting, you should download the News Preview tool and use the “Download” function within the Apple News article listing in WordPress to get the JSON to feed into News Preview. More info can be found here:

https://github.com/alleyinteractive/apple-news/wiki/usage#downloading-posts

You need to follow the instructions here to validate your .papi file before uploading it to your WordPress site: https://github.com/alleyinteractive/apple-news/wiki/configuration#api-settings

If you can’t validate it using the CLI utility, then we can’t guarantee it will work when uploaded to the site.

Retrieving a list of settings depends on a valid API connection, so if you can’t get your .papi file working correctly via the CLI and uploaded to your WordPress site, then it won’t be able to communicate with the Apple News API at all, including fetching a list of sections. An error message indicating that a list of sections could not be fetched is usually a clear indicator to me that the API credentials are incorrect.

That should be populated with ignoreDocumentMargin which should be set to true or false based on the value of the full bleed images setting. Can you try going to Apple News > Settings and saving the settings and trying again? I’m wondering if that setting isn’t set and it’s confusing the plugin when trying to add that property to the layout.

This could also be caused by customizing the JSON for the image component (specifically, the image with caption JSON) and setting the layout to an empty array, which it shouldn’t be.

That looks like default WordPress behavior and not specific to this plugin. The Publish to Apple News plugin does in fact register an uninstall hook, but only updates the option if the option doesn’t already contain the uninstall hook, so it shouldn’t execute on every page load. Is it possible that one of the other plugins listed there is calling register_uninstall_hook too aggressively (e.g., public-post-preview, adminimize)?

We’re tracking this as a bug here: https://github.com/alleyinteractive/apple-news/issues/922

Unfortunately, there isn’t a fix available yet. I’m going to close this issue in favor of tracking progress in GitHub. You are welcome to subscribe to the issue on GitHub to receive updates there.

Hi @brentammok —

I apologize for the delay in responding—I didn’t see this message when it came in.

You should be able to use this filter to remove the ads before the content is sent to the Publish to Apple News plugin to be converted to Apple News Format:

https://github.com/alleyinteractive/apple-news/wiki/Filter:-apple_news_exporter_content

Hi @josephorr —

I apologize for the delay—I somehow missed this issue coming in.

I’ve reviewed the code and I’m perplexed as to how this could occur. Is it possible that you have modified the plugin code in some way? I would recommend fully removing the plugin’s files and reinstalling from www.ads-software.com and seeing if the issue is reproducible. I haven’t heard of others experiencing the same issue, so my guess is that it’s related to something on your environment (files or PHP version, perhaps).

This document seems to indicate that you might have a typo in your channel ID: https://developer.apple.com/documentation/apple_news/apple_news_api/about_apple_news_api_error_messages?changes=_1_4

Hi @psm9640 –

I’m sorry that you’re having trouble getting the Apple News API Client Utility to work. However, that software is developed and maintained by Apple, so you’ll need to follow up with Apple if it’s not working correctly for you. Once you have verified your channel credentials, if you have any issues configuring the Publish to Apple News WordPress plugin, please let me know.

Thanks!

Channel order is determined by Apple and isn’t always strictly chronological. If you are using the WordPress publish date as the date of publication and not a custom field, then the plugin should be properly reporting the date of publication to Apple when the article is published. You can enable debug mode in the plugin via the Settings screen and enter your email address, and you’ll receive a very detailed email containing all of the information that was sent to Apple, and you can use that to verify that the publication date is properly being reported when the article is published. The publication date should be part of the article’s metadata.

If everything is being sent to Apple properly and you have further questions about article order on your channel, you should open a support ticket with Apple (these forums are managed by Alley, who develops the plugin, so questions about Apple News itself or your channel will need to be directed to them).

Let me know if I can help further!