Josh (a11n)
Forum Replies Created
-
Forum: Plugins
In reply to: [WP Super Cache] Any Changes Always Delete CacheHowdy @shshshea
It sounds like the cache clearing you’re seeing is expected behavior. Jetpack Boost automatically clears cached content when posts are updated, published, or deleted to ensure visitors always see the latest version of your site.
If you’re still running into issues or need more personalized help, feel free to contact Jetpack support directly and we can take a closer look.
Howdy @schulmanconsulting
Since the reinstall didn’t help, two things to verify:
- SEO module is enabled: Go to Jetpack → Settings → Traffic and make sure “Customize your SEO settings” is toggled on.
- Screen Options checkbox: In the Classic Editor, click Screen Options (top-right of the edit screen) and ensure the Jetpack SEO checkbox is ticked.
If both are already set correctly and the meta box still isn’t appearing, reach out to us directly using this contact form so we can dig deeper. Please be sure to reference the URL to this thread in your message.
Forum: WordPress Mobile App
In reply to: “HMAC Verification Failed”Howdy @chrismonty
Thanks for all that testing. What you’re describing matches a known bug we’re fixing in the iOS app.
When you connect a self-hosted site directly (without Jetpack), the app should pull your categories and tags from your site’s REST API. There’s currently a bug that prevents this from working properly, which is why the category list shows blank and tags don’t populate.
The fix is complete and will ship in the next iOS app update. Once you update, connecting without Jetpack should give you access to your categories and tags.
Until then, wp-admin in a mobile browser is the most reliable workaround if you need to assign categories or tags.
Howdy @desiggnsiggnatur
Thanks for taking the time to share this feedback, and for sticking with Protect despite the frustration. You’re touching on something real.
You’re right that security warnings are only as useful as their clarity. Knowing something might be wrong is step one, but understanding the severity, exploitability, and next steps is what actually helps you take action. The uncertainty you described is the opposite of what we want.
We’re actively working on improving how Protect communicates risks, including better context around severity and clearer guidance on what (if anything) needs immediate attention. Your feedback helps shape that work.
If you run into specific warnings that felt unclear or overblown, I’d love to hear the details. You can reach us directly through this contact form and reference this thread. Concrete examples help us prioritize what to fix first.
Appreciate you sharing this.
Forum: Plugins
In reply to: [Jetpack Social] Stuck Facebook connectionHowdy @ludwigkeck,
Your Jetpack plugin is connected, but your WordPress.com account isn’t linked as the site owner. This is why the Facebook connection is stuck and won’t let you disconnect it. Without an owner account connected, Jetpack Social can’t properly manage the social media connections – and the Jetpack connection is still broken.Here’s how to fix it:
- Go to your site’s WP Admin dashboard
- Navigate to Jetpack → Dashboard (or Jetpack → My Jetpack)
- You should see a prompt to connect your WordPress.com account, or there may be a banner indicating the connection needs attention
- Click through to complete the connection, signing in with your WordPress.com account
Once your WordPress.com account is connected as the site owner, head to Jetpack → Social and try disconnecting that stuck Facebook connection again. It should work this time.
After disconnecting, you can reconnect Facebook fresh by following the steps here: https://jetpack.com/support/jetpack-social/facebook/
You can also reach us directly for faster, private support if you’d prefer, using this contact form.
Just mention this forum thread when you do and we’ll pick up right where we left off.
@ravanh Glad the JavaScript workaround is doing the trick. We’ll make some noise in the changelog when the official fix ships, so keep an eye out for that. If anything acts up after the update, just flag it here and we’ll sort it out with you.
Hi @tomangell
Thanks for the detailed report, and sorry for the trouble with the latest update.
You’ve hit a known issue. Jetpack 15.9’s Social admin page doesn’t load on WordPress versions older than 7.0. The build references script handles that only exist in WP 7.0, so the page renders blank on 6.9.x while everything else (like AI and Newsletter) works fine.
As @jgprdanielle mentioned, updating WordPress to 7.0 resolves this immediately.
Our engineering team is also working on a fix to restore compatibility with older WordPress versions, but upgrading to 7.0 is the fastest path forward if that’s an option for you.
If you experience any issues after this update, please let us know and we can dig into it.
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Blaze AdsHowdy @cheaplahousing, thank you for reaching out. We do have human support, please reach out to us directly via this Contact Form so we can help you out.
When you do, please reference this forum topic. Thanks!
Howdy @claudiamathiaslauramaria – that is awesome, I’m happy we were able to help you out. 🙂
@claudiamathiaslauramaria
Thanks for the report and the link to the affected page. I confirmed that the Jetpack connection on your site is working properly.The issue (thumbnails not showing but full images loading when clicked) indicates something is blocking the connection between your server and Jetpack’s Image CDN. The Tiled Gallery block always uses our CDN for thumbnails.
Please check:
- Security plugins like Wordfence, All-In-One WP Security, or Sucuri can block Jetpack requests. Temporarily deactivate these to test.
- Ask your hosting provider if they’re blocking requests from the
Photon/1.0user agent, or if Jetpack’s IPs need to be allowlisted: Jetpack IPs - Clear your cache if you’re using a caching plugin.
Let me know how it goes.
Howdy @rvsolomonjr1 ,
Thanks for reporting this issue. After looking into this, it sounds like you may be using a different podcast player plugin rather than Jetpack’s built-in Podcast Player block.
Jetpack’s Podcast Player block doesn’t have a “time ticker” feature that syncs with time in the way you’re describing. However, there’s a popular third-party plugin called “Podcast Player” by Veda/vedathemes that has similar functionality with a time progress feature.
Could you check which plugin you’re actually using?
- Go to Plugins → Installed Plugins in your WordPress admin
- Look for either “Jetpack” or “Podcast Player” (by vedathemes)
If you’re using the “Podcast Player” plugin by Veda, you’ll want to post in their support forum instead: https://wordpress.org/support/plugin/podcast-player/
If you are indeed using Jetpack’s Podcast Player block and can share a link to the page where you’re experiencing the issue, I’d be happy to take a closer look!
Forum: Plugins
In reply to: [Jetpack Social] Jetpack shares with Instagram only the title of the postHowdy @brunogal!
Thanks for the details and the site URLs.
Jetpack Social currently shares the post title plus optional custom message to Instagram by default. The amount of post body text included in the caption can vary depending on how the share is constructed, but full post content isn’t included automatically because Instagram has its own formatting constraints (like the 2200 character caption limit).
If you want to control exactly what text appears in your Instagram caption, you can add a custom message when publishing:
- In the post editor, click the Jetpack icon in the top right corner
- Look for the “Share to Social Media” section
- Add your custom message there (up to 255 characters for Instagram)
- This text will be used as your Instagram caption
The change you noticed might be related to a recent update, but the default behavior has been to share title + excerpt (or custom message) rather than full post content.
I’ll also pass along your feedback about wanting more post text included automatically. The team is actively looking at ways to improve how content is formatted for different social networks.
Let me know if you have any other questions about customizing your shares.
Hi @aamiine ,
Thanks for sharing the URL and confirming you’re using Twenty Twenty-Four. Since the issue happens with a default WordPress theme, this points to a block-level issue rather than a theme conflict.
I believe this may be related to a known bug with the Phone Number Field block initialization that our developers are actively working on. The fix has been prioritized and is currently in progress. The issue can cause the phone field component to not render correctly, which in turn affects layout on smaller screens.
I currently do not have an ETA for this fix to ship but we can keep you in the loop. In the meantime, to make sure we are on the same page, could you share a screenshot of how the layout breaks on mobile? That would help me confirm whether this is the same bug and potentially offer a more targeted CSS fix while the underlying issue is resolved.
Howdy @ravanh
Thanks for the follow-up and the clear explanation. You’re right: the Jetpack Connection card showing a “Connect” button (and then erroring out when clicked) is confusing when Offline Mode is intentionally enabled. In that scenario, the card is essentially offering an action that can’t succeed.
I’ve filed this as a bug report with our development team. The expected behavior would be for the Connector Card to either be hidden entirely when Offline Mode is active, or to show an informational state that explains why connection isn’t available. I can’t promise a timeline, but it’s on the radar now.
Thanks for taking the time to report this. Feedback like this helps us catch the edge cases that make the experience smoother.
Howdy @jvande,
Thanks for reaching out and for including the error details.
Since this is happening on a staging site (staging.actonexchange.org), the most likely cause is an access restriction preventing the Critical CSS generator from reaching the page. The generator needs to fetch your pages to analyze the CSS, so if the staging environment has any of the following, it won’t be able to complete:
- HTTP authentication (username/password prompt)
- IP allowlisting or firewall rules
- A “coming soon” or maintenance mode plugin
- The site not being publicly accessible
Could you confirm whether your staging site is publicly accessible? Try opening staging.actonexchange.org in a private/incognito browser window (while logged out) and see if the homepage loads without any login prompts or blocks.
If the staging site is intentionally restricted, Critical CSS generation won’t work there. You’d either need to temporarily open access while generating the CSS, or skip Critical CSS on staging and only use it on your production site.
Let us know what you find and we can go from there.