everyamp

I don’t have any plugins or snippets installed to intentionally disable rss2 and I don’t see any settings that would cause it. I deactivated the Google Product Feed plugin and it made no difference.

• This reply was modified 2 years, 1 month ago by everyamp.

I clicked the Flush Rewrite Rules button, tried the URL again, page not found.

Clicked the Refresh Feed XML Cache button, tried the URL again, page not found.

What’s next?

Got it, thanks!

I’ve cleaned up the settings on my products, but I’m just getting a missing page error when I try to view the feed. What am I missing here?

https://everyamp.com/google-merchant/feed/rss2/en_US.xml

Spoke too soon. I just attempted to do the banner URL and I’m back to the SSL error:

Error retrieving?https://everyamp.com/wp-content/uploads/2023/01/Banner_WPSSO_600x60.png?for caching (after 0.008 seconds). cURL error code 60 SSL certificate problem: self signed certificate. SSL verification failed with code 18. Additional requests to retrieve this URL will be ignored for another 600 second(s).

• This reply was modified 2 years, 1 month ago by everyamp.

Same error.

Ok, so we found that ca-bundle.crt was outdated for some reason and updated it to the current version from WordPress. However, I’m still not able to set the image. I’ve tried a different image with different resolution and I get the same error:

The value of option “site_org_logo_url” must be a valid image URL – resetting this option to its default value.

From Kinsta:

We’re on the current WordPress version 6.1.1.

Kinsta handles the certificates for us and they’re up to date as best as I can tell: https://www.ssllabs.com/ssltest/analyze.html?d=everyamp.com

Is there somewhere specific that I should check?

Here’s what he got:

$ ssh [email protected] -p 23960
[email protected]'s password:
Welcome to Ubuntu 20.04.3 LTS (GNU/Linux 5.4.0-1096-gcp x86_64)
  _  ___           _
 | |/ (_)_ __  ___| |_ __ _
 | ' /| | '_ \/ __| __/ _` |
 | . \| | | | \__ \ || (_| |_
 |_|\_\_|_| |_|___/\__\__,_(_)

Hi There!
Your site's files are in the /www folder.
Git, Composer and WP-CLI are all available for use!
If you need help just open a ticket on https://my.kinsta.com
Have a marvellous day!


 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage
livingteslacom@EOS-livingteslacom:~$ curl -IkL https://everyamp.com/wp-content/uploads/2023/01/[email protected]
HTTP/2 200
server: nginx
date: Fri, 27 Jan 2023 22:10:49 GMT
content-type: image/png
content-length: 458658
last-modified: Thu, 26 Jan 2023 19:54:50 GMT
etag: "63d2da8a-6ffa2"
expires: Thu, 31 Dec 2037 23:55:55 GMT
cache-control: max-age=315360000
access-control-allow-origin: *
accept-ranges: bytes

Thanks for the response. I started with Kinsta support first. Here’s what they said:

I'm not getting any broken pipes or cert warnings when I try to cURL or visit the image, so it's not the server SSL:
$ curl -IkL https://everyamp.com/wp-content/uploads/2023/01/[email protected]
HTTP/2 200
date: Fri, 27 Jan 2023 21:33:31 GMT
content-type: image/png
content-length: 458658
cf-ray: 79049b6e0e5fadbc-ATL
accept-ranges: bytes
access-control-allow-origin: *
cache-control: max-age=315360000
etag: "63d2da8a-6ffa2"
expires: Thu, 31 Dec 2037 23:55:55 GMT
last-modified: Thu, 26 Jan 2023 19:54:50 GMT
cf-cache-status: DYNAMIC
ki-cache-type: None
ki-cf-cache-status: BYPASS
ki-edge: v=17.16
x-content-type-options: nosniff
x-edge-location-klb: 1
server: cloudflare
alt-svc: h3=":443"; ma=86

How can we get you both together to find a resolution?

FYI, if you’re a Premium customer, and you want to install the Development versions on your development / staging server(s), you can select the Development branch for WPSSO Core and its add-ons under the SSO > Update Manager settings page.

We are premium and do have a staging site set up, but since that’s not connected to merchant center I’m not sure how it would help us validate that the updates resolve the mismatch error.

Ultimately, I’d like to move towards moving our sitemaps and product feed to WPSSO so I can reduce the number of different developers’ plugins we have going, so thanks for helping with this!

Assuming the MPN and GTINs appears in your feed XML, that should be fine.

Confirmed in the feed here:

so you may want to re-enable the ‘product:price’ meta tag

I don’t recall ever having a reason to disable this, but it is now enabled. I’ll see if this leads to any change in merchant center in tomorrow morning’s update.

but for this feature to be active, the WPSSO GMF add-on must be active (the add-on triggers activation of this feature).

WPSSO GMF add-on is active, but I’m still using the GPF plug-in xml to feed merchant center since I still have more to configure with WPSSO and the GPF xml is currently working well for most products.

Although moving the variation offer top-most for a variation URL should address that Google merchant crawler bug, in the future WPSSO Core will probably implement?https://schema.org/ProductGroup?markup instead.?

This sounds promising, but is there any kind of timeline on it? We’re launching a new product soon that will have different-priced variations and I expect to have this same issue with it. Not being able to advertise that product makes this a high priority for us.

I’d like to +1 this issue with @joelmellin. I followed him here from the Google Product Feed plugin thread since I’ve been having the same price mismatch issues for a long time with two of my variable products. I’m still on GPF, but I’m open to switching to this feed plugin if the recent updates resolve the issues for him.