mattlindley0804

I guess I will just downgrade my apple news account to rss instead of the Apple News Format, then.

Ok, what I am seeing is that turning on allow_url_fopen is a significant security risk. It opens the door to code injection attacks. Everything – EVERYTHING – I am reading recommends using CURL instead. Considering the frequency with which I see hacking attempts on my sites (luckily blocked by Wordfence), I am not sure I am willing to even try turning on this setting, assuming Network Solutions would even allow it.

This is a deal breaker.

Ok. For some reason, WP wasn’t showing an available update until I went to the plugins page. Got it.

I’ll research how to check the allow_url_fopen settings on Network Solutions.

Maybe. Now, when I try to publish an individual post, nothing happens and I am no longer getting any reports of any errors. On the settings page, I no longer see a place to make sure the reports are being sent.

I just tried a bulk publish. It showed each post being published. But, in the Apple News panel, none of the articles appeared as Drafts or Published.

Again, no email logs. However, when I return to the Apple News panel (where I can individually or bulk publish), I see a number of error messages:

“There has been an error with the API. Please make sure your API settings are correct and try again: The attachment article.json could not be included in the request because it was empty.”
“There has been an error with the API. Please make sure your API settings are correct and try again: The attachment Rice-throwing.jpg could not be included in the request because it was empty.”

All the errors are saying basically the same thing.

Plus, I see a couple of errors in the settings page:
Minor error: “Enter your Apple News credentials below.” text appears where it should and in the next section. Just duplicated text, no big deal.
At the bottom, after the “Advertisement” settings, there is a header for “Component Order” that has no content. The settings page just ends there.

Perfect – Thank you!

Ok. With a bit of research and examining of the downloadable article.json (through the plugin interface in the Admin section), I think I may know the source of the error – though the solution may be a bit beyond my abilities. It seems that there is a missing or bad parameter(s) in the json file that is submitted to Apple.

Specifically, with regard to the errors that reference an image, it seems that the json file is either missing or has a bad SIZE parameter for the images.

Bear with me, as json is not a part of my wheelhouse.
Looking at the Apple Developer docs: https://developer.apple.com/library/ios/documentation/General/Conceptual/News_API_Ref/CreateArticle.html, you can see (in the first example code block) that every image referenced in the json file needs to have a corresponding resource section after the json block. There, image MIME TYPE’s (‘Content-Type’) are defined, including their size (in ‘Content-Disposition’).

Further down that page, it lists the errors and their meanings. MIME_PART_INVALID_SIZE says that the Size parameter is not an integer greater than or equal to zero.

Now, in the article.json file I downloaded from my site (generated by this plugin), there is no resource section that defines the images for the article. I do not know if that means it isn’t being submitted correctly to Apple or if it simply isn’t included in the downloadable json file.

So, for anyone who may be monitoring this thread, maybe this provides a clue to a solution?

Then my next test returned an error, again referencing an image.

Ok. Not sure if this will help anyone… I had my settings to display Gallery items in a Mosaic format. I changed it back to Gallery (Settings->Apple News->Gallery Type) and the error I received changed. Now, instead of referencing an image, it references a json file.

Array
(
    [headers] => Array
        (
            [date] => Wed, 16 Mar 2016 16:04:52 GMT
            [request-id] => c6183f3b-ee9a-476b-b3fa-f95dc9c26342
            [content-type] => application/json; charset=UTF-8
            [content-length] => 73
            [connection] => keep-alive
        )

    [body] => {"errors":[{"code":"MIME_PART_INVALID_SIZE","keyPath":["article.json"]}]}
    [response] => Array
        (
            [code] => 400
            [message] => Bad Request
        )

    [cookies] => Array
        (
        )

    [filename] =>
)

Every attempt to publish yields the same error, always referencing an image. I do not think it is due to the image size, since the images referenced are in a variety of sizes, from small to large.