Hi there @dupuisg,
You did discover many things to address! I’m going to tackle them one by one as follows ??
I turned off Jetpack Social to do some debugging and found out that even when Social is disabled my subscribers were notified about by Test post…so we have a problem there also…
This is related to a different feature you might have enabled, the Newsletter feature: it works with or without the Social sharing feature. I’d recommend turning the feature temporarily off every time you need to publish a test post and re-enabling it right after so your subscribers won’t receive unwanted posts.
****
case in point, the following link works just find when shared on FB…
https://dupuisg.ca/2023/12/25/spain-2023/
I see this is an old post from 2023; if my theory about the 403 error block you reported (see below) is correct, it’s possible that this post can be shared on Facebook correctly because it’s not affected by the block you’re having at the moment, which might involve only recent posts.
****
Error code 403
This response code could be due to a robots.txt block. Please allowlist facebookexternalhit on your sites robots.txt config to utilize Facebook scraping
That’s not directly related to Jetpack Social: it looks like you have a block at your server’s end (in the robots.txt file) blocking the Facebook tool that “reads” the information needed to proceed with the data sharing. I’d recommend contacting your host about that to see if they can sort that out for you. Once that’s amended, hopefully Social should resume its usual work. ??
****
I am curious about clearing my website cache…I did clear my browser cache before publishing but I have never heard about clearing the website cache…how would that be done.?
Not only can you clear your browser cache, but there are software that can take care of the site’s internal cache too, and are useful to keep the site efficient.
I’d recommend trying WP Super Cache, which is a free, low-maintenance plugin that’s 100% compatible with Jetpack.