WooCommerce error messages no displayed with Jetpack Sharing module turn on

I tried to reproduce the issue, but the error messages appear to be displayed, whether I use Jetpack and its sharing module, or not. Here is how things look like when I test things with Storefront:

https://i.wpne.ws/h9EW
https://i.wpne.ws/h8wx
https://i.wpne.ws/h9GW
https://i.wpne.ws/h9FF

The notices use WooCommerce in the class names, so their look is most likely not customized by Jetpack:
https://i.wpne.ws/h9E5

Could you post a link to your log in page here, so I can have a look?

If you want it to remain private, you can also contact us via this contact form:
https://jetpack.com/contact-support/

Hi Jeremy,

Here is my website account page : https://bluemoonsound.com/en/my-account/
(the website is still in development)

Also, I did more tests. I think there is a conflict between Jetpack Sharing and Page Builder by SiteOrigin.

Thanks

I see you’ve added that log in form in a SiteOrigin text Widget? What happens when you use the [woocommerce_my_account] shortcode in a page instead, without using SiteOrigin, as explained here:
https://docs.woocommerce.com/document/woocommerce-shortcodes/#section-5

You can set that page as your account page in your WooCommerce settings, and logged out users will see a WooCommerce registration form there:
https://i.wpne.ws/hEu0

Yes all my pages are made like that. It’s easier for me to keep the same titles layout.

I have other pages with shortcodes in SiteOrigin text Widget and no issue until now.

Your solution works. But I’m just confused about change this organisation I was using before just because of an update. I don’t know from who it’s coming from (jetpack, woocommerce, siteorigin). The thing is we have to check and correct bugs every time a plugin has an update, even for popular ones.

I ran a few tests to try to understand the cause of the issue:

• When inserting the shortcode in a real text widget in a sidebar, the notices do get displayed, but not above the wdget. The notice appears at the top of the page content when you use the Storefront theme.
• When inserting the shortcode inside a Page Builder Text Widget, no notice is displayed.
• I then looked at how the notices are injected into the pages by WooCommerce. It appears that notices can be displayed in multiple locations inside a WordPress site:

• The notices can be hooked in 3 actions: woocommerce_shortcode_before_product_cat_loop, woocommerce_before_shop_loop, and woocommerce_before_single_product.
• These action hooks can be used by themes to control the display of the notices.
• A notice can only be displayed once. If your theme calls one of those hooks somewhere at the top of the page, the notice won’t be displayed again later, even if another hook is inserted downer on the page.
• If none of these action hooks are used, the notices are displayed right above the form.

• When inserting the Page Builder Text Widget, no notice is displayed, even when one doesn’t use a theme that includes one of the action hooks above.
• Jetpack’s Sharing module and Publicize module both have an impact on the problem.
• When I deactivate Jetpack’s Open Graph Meta tags (like so), the problem disappears. Since OG tags are added as soon as you enable one of the 2 modules I mentioned above, that narrows down the conflict to a problem between SiteOrigin’s text widget and Jetpack’s Open Open Graph Meta tags.

I’m not really familiar with the Page Builder plugin though, so I’m not sure what could cause that conflict.

Could you try to deactivate Jetpack’s Open Graph Meta Tags on your site (you can use this little plugin to do so), and let me know if that helps?

It seems to work like this.

I don’t understand, I though Open Graph meta tags were use for post previews when we share a post. I can’t see any difference when it’s deactivated.

What’s the consequences on my website if I leave it deactivated?

I don’t understand, I though Open Graph meta tags were use for post previews when we share a post. I can’t see any difference when it’s deactivated.

That’s correct. However, most social networks cache the post previews they create for each post, so if you’re trying to share a post that was cached by Facebook when the Open Graph Meta Tags were still active, things will most likely look good for a few days, as long as Facebook doesn’t decide to refresh their cache.

On the long term, you will need to find a new Open Graph plugin like this one, or fix the conflict between Open Graph Meta Tags and the Page Builder plugin.

Could you maybe contact the Page Builder plugin authors, and ask them how the text widgets are rendered in the plugin. Do they have any impact on content filters, or on the main loop? Feel free to give them a link to this thread if they need more info!

Ok I see. It makes sense.

I’ll contact the Page Builder plugin authors.

Thank you for your time Jeremy !