brentammok

Thanks for responding.

When I woke up this morning I did see the changes I made take effect.

So it seems to have resolved overnight.

Thank you.

@adamdunnage – I cleared the cache through Site Ground. The errors still occurred. I then deactivated the SiteGround Optimizer plugin, cleared the cache (again), and the errors did not display.

I get the sense this is what you might have been expecting? what now?

thanks

Brent

Hi Adam,

1. I have submitted the form. Instructions were super-clear!

2. The errors did not show up in the plugin, either dashboard or settings sections

3. The errors DO NOT show up on an incognito chrome window. (Hmmmmm)

Let me know if you need anything else.

Thanks

Brent

Hi Kevin,

An update… the conflict problem seems to have resolved itself. I can’t explain how. Given your explanation that Publish to Apple News does not interact with the front-end of a site, whatever (now self-resolved) problem likely had nothing to do with the plugin.

I appreciate your response and my apologies for wasting your time.

Thanks

Brent

H Kevin,

Thanks for responding and giving more details about other Yoast users having no problems and that Publish to Apple News does not modify the sitemaps.

Since my post to you, I have been liaising with the help forums for Google News and I am fairly confident that the problems I have been having with my articles loading into Newsstand are at Google’s end – nothing to do with Publish with Apple News.

The conflict with the Theme functionality (featured image in post-editing) is still occurring. Any insights you have to help me diagnose and overcome this issue would be great!

Word press version: 5.9.3
Publish to Apple News version: 2.3.2
PHP version: 7.4.29

In the Chrome Browser, there are some errors:
Uncaught TypeError: Cannot read properties of undefined (reading ‘call’)
Uncaught TypeError: Cannot read properties of undefined (reading ‘createRegistrySelector’)
Uncaught TypeError: Cannot read properties of undefined (reading ‘useSelect’).

In my webhost, I have a number of font errors (which need addressing ?? ) and one error I am not familiar with.

2022-05-05 09:17:13 UTC [nginx][error] 42688#0: *22838022 openat() “/home/u1563-q3seyyiwkqxg/www/ammok.com.au/public_html/.well-known/pki-validation/ca3-a5cb824d760a451ba6f2b3930eb7a372.txt” failed (2: No such file or directory), client: 172.70.0.5, server: ammok.com.au, request: “GET /.well-known/pki-validation/ca3-a5cb824d760a451ba6f2b3930eb7a372.txt HTTP/1.1”, host: “ammok.com.au”

Any insights appreciated.

Thanks

Brent