Boston Tom

Thanks for getting back to me. The problem with switching to a generic theme like 2022 is that the problem only occurs if you’re logged out of the site, so that won’t do me any good. The Health Check plugin’s troubleshooting mode does that for you and only the admin can see the generic browser. It also doesn’t show the Jetpack buttons in that mode. When I’m logged in as Admin, regardless of Browser, the issue goes away. But when I log out, the problem returns.

The Health Check also said everything was good. Site health is good. No conflicts. The problem only occurs if you’re logged out of the site. Since I have “Anyone can register” in General Settings turned off (always have), people can comment freely without needing to create an account.

The link address when you hover your mouse over a button reads: https://example.com/link-to-article/?share=facebook&nb=1

I renamed the domain and url for privacy reasons. This new support system doesn’t allow you to hide sensitive information.

Since I can’t edit my thread posts I thought I reply with an update (does anybody from Jetpack read these? I see a lot of unanswered questions from other users).

When I log in as admin on the browsers that don’t work, I’m able to share an article from the front end of the site. As soon as I log out, it reverts to not working. That’s why the share buttons were working in Safari (it was the only browser where I was logged into the backend of my site).

When I logged into the admin backend via Chrome, the sharing buttons worked. Hence, unless a user sends you an email the buttons aren’t working, you would NEVER know the share buttons don’t work if you’re logged in as admin.

Could someone from Jetpack dive in here for a little help? I’ve gone through the whole process of deactivating every plugin and nothing works. And it only started happening after updating to the latest version.

Anybody there? I disabled Yoast (and a multitude of other plugins) trying to debug this and am at a loss. The share buttons only work correctly in Safari/Mac. In Chrome, Brave, Firefox, and Edge, they all open a pop-up window with the article inside, not the social media site. I’m at my wit’s end with this.

Did you check the errors_log in the root directory of your WordPress installation? That would be a good place to see if there is a conflict. I had this issue before and I deleted the widget and did it from scratch. Then it started working again. I saw subscription in your post and skimmed over so my bad.

Hey, thanks for not responding (as I see with other posts). The issues was fixed when I turned off:

Enable Subscribe Modal in the Settings > Discussion

I never have seen this as it’s at the very bottom of the screen nor did I turn it on. Stop adding features and turning them on unless I want to do it. Your presumptuousness broke my entire site.

I’m having the same issue. The homepage loads but if you click on an article, it gives you an error page.

There has been a critical error on this website.
Learn more about troubleshooting WordPress.

And the error_log says:

[07-Dec-2023 14:54:01 UTC] PHP Fatal error: Uncaught Error: Class ‘Automattic\Jetpack\Extensions\Premium_Content\Subscription_Service\Token_Subscription_Service’ not found in …/wp-content/plugins/jetpack/modules/subscriptions/subscribe-modal/class-jetpack-subscribe-modal.php:193

The error_log also shows a stack trace:

Stack trace: 0 …wp-content/plugins/jetpack/modules/subscriptions/subscribe-modal/class-jetpack-subscribe-modal.php(62): Jetpack_Subscribe_Modal->should_user_see_modal()
1 …/wp-includes/class-wp-hook.php(324): Jetpack_Subscribe_Modal->enqueue_assets(”)
2 …/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
3 …/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
4 …/wp-includes/script-loader.php(2262): do_action(‘wp_enqueue_scri…’)
5 /home3/nonames2/public_html/cl in …/wp-content/plugins/jetpack/modules/subscriptions/subscribe-modal/class-jetpack-subscribe-modal.php on line 193

I’ve truncated the full path as it shows the server’s root path. I need a functioning website and now it doesn’t work after updating JetPack to 12.9. Also, this error message repeats over and over again. Nearly 4,000 lines.

Ok, Thanks for your help. Seems to be helping.

So I followed the instructions and went through the last couple of days marking all the spam comments. How does Cleantalk miss a comment that says:

"If you are looking for opportunities to earn something extra alongside your studies or in your free time. With the advent of the digital age, finding a part-time job online is easier than ever. eo Here are some of the best ways to find and get part-time jobs online for students or the unemployed. 
Click and see….... Join Start Google Day1"

Or

Get paid for simple online data entry tasks. Work at your own pace. Regular Payments. Search in different job categories. Work anywhere on your computer, rd laptop or mobile phone.Update your profile at any time.
You get paid every day. here Click It…… Join Start Google Day1

I just went back to my comments and FOUR more comments that are spam got through. This is nuts!

In the WP backend, I always mark comments as Spam. Why doesn’t Cleantalk record that? I might as well just Trash them since marking them as spam has to be done via the Cleantalk dashboard. I literally don’t have time to do this. If I mark it as Spam in the WP backend, it should automatically communicate with Cleantalk and update your logs. Now I have to do it twice?

I left out my site’s URL because I don’t want to make it public. No way to hide it like you could before.

Sebosiris is right. You need to use the inline code tag in the toolbar so your single quotes don’t become curly quotes.

add_filter( 'option_rop_first_install_version', '__return_false' );

• This reply was modified 1 year, 7 months ago by Boston Tom.

Yes, it’s fixed! Thanks. So what was the problem?

Hi Peter,
I’m running PHP 7.4.32 (which I got from under Tools > Site Health > Info) on both sites. One is having no issues, but the other is. The one having issues is using a different theme but by the same company. Cheers, Tom

Hi Peter,
I also have the plugin installed on a different site I manage that uses a different theme and have no issues. On the site where the plugin doesn’t work, I can’t turn off and on plugins as you suggest as it’s a heavily trafficked site and some of the plugins will lose their default settings upon deactivation.
I’ll look into plugins that also modify URLs, as the only difference between the two sites is the problematic site uses Cloudflare with WP Rocket and the non-problematic site uses WP Rocket (no cloudflare). The problematic site also uses AISEO while the non-problematic site uses Yoast.
Turning either of these plugins off is hugely disruptive as the site would literally go offline, the cloudflare cache would have to be deactivated (I emptied it but it didn’t fix the issue), and so on.
Cheers.

Same thing on my site. Nothing shows up on the homepage with an error message (below) that the page is missing (that’s how I narrowed it down to your plugin). Also, when I preview articles, I get this error message generated by the custom 404 error message:

“Sorry, we can’t find what you’re looking for!
You’ve landed on a URL that doesn’t exist and it’s probably our fault.”

Once I disabled it, the issue went away. Hate to not have this working! Keep us updated on a fix or maybe suggest an alternative.

• This reply was modified 2 years, 4 months ago by Boston Tom.

Thanks so much for your time and help. Much appreciated!

Hi there,
Thanks so much for all the time you’ve vested in this. I guess I spoke too soon. It appears that selecting a hi-res image for Twitter didn’t fix the problem. Users using the Twitter share button are still posting tweets with blank images, even though it’s specifically specified. The page source code shows the twitter:image tag with the URL to the image.
This is what it shows when you look at the page source code (For privacy reasons, I’ve changed the website name to a fake one.):
<meta name="twitter:image" content="https://i0.wp.com/domainname.com/wp-content/uploads/2020/10/earth-image.jpg?fit=1127%2C833&ssl=1"/>
Incidentally, the meta tag for Facebook shows:
<meta property="og:image" content="https://domainname/wp-content/uploads/2020/10/earth-image.jpg"/>
Both images were manually selected on the backend via the Yoast panel. Please note the URLs are different. Removing the Twitter image also removes the twitter:image tag with the same results: a blank image when sharing to twitter.
I’ve tried clearing the server cache, my browser’s cache, the WP cache, nothing seems to help. Should I start a new topic since I can’t edit the original one to show you hidden info?