Daniel

Hi @bjerkely911

Thank you for your patience.

For the Facebook issue, ensure your images meet Facebook’s requirements. The 30-share limit shouldn’t affect image display.

Regarding lazy loading, consider disabling it, as it may be deprecated soon. Most modern browsers now offer lazy loading natively.

For the missing images, please provide your site URL for further investigation. If you want it to remain private, you can also contact us via this contact form. If you choose to reach out directly, please include a link to this thread.

Hi @ipstenu

Thank you for your patience.

Could you confirm that the issue has been resolved? I can see that the most recent post “Hallmark Brings Another Queer Christmas” was shared to Facebook successfully.

@leftofcentre Are you still encountering the issue?

@iceknight Do you use Cloudflare? It makes sense that it would work when you’re leaving an anonymous comment (and by anonymous, I mean non-member). What do you mean when you say “regular WordPress account”? How does that differ from the “site’s account” you mentioned?

@thathappyreader

Based on what you’ve shared, it appears that you’re seeing the incorrect image being shared on Twitter even though the correct image is shared on Facebook. While this is unusual, it can happen if the specific meta tags for Twitter (twitter:image) are not consistent with the default Open Graph (og:image) meta tags.

Here are a few steps you can take to rectify this:

1. First, you should check if the twitter:image meta tag in your post’s HTML head section is referencing the correct image. You can view the source code of your webpage (right-click anywhere on your webpage > “view page source” or “inspect”) and look for the line <meta property="twitter:image" content="..." />. The URL in the content section should be the URL of the desired image.
2. If the image URL is correct in the twitter:image meta tag, then it would be best to verify if the image meets Twitter’s card requirements. Please ensure that the image is less than 5MB in size and adheres to the aspect ratio recommended by Twitter (between 2:1 and 1:1).
3. Finally, after making any changes, remember to validate your Twitter card again with Twitter’s card validator tool and clear your Bluehost cache.

Hi @alkemy007

The message you’re seeing relates to object caching, which can improve your site performance further by caching database query results. While WP Super Cache is an excellent plugin for caching static page content, it does not handle object caching.

To set up an object cache with your WordPress site, consider the suggestions from @donbowman and @jacksim. They have suggested using the Redis or Memcached systems, or, in the case of shared hosting solutions, SQLite Object Cache.

Please, remember that your hosting provider must also provide server support for these object caching modules. Contact them if you’re unsure. Once installed, this should resolve the persistent object cache warning in your Site Health panel.

Hi @hamid123gold

That SSL parameter instructs Site Accelerator to pull images via HTTPS. That is expected behavior. The ssl=1 parameter is used to force Photon to fetch images using HTTPS, resulting in safer, encrypted transfers.

Removing this parameter might cause Photon to fetch the image using HTTP or HTTPS, depending on the given circumstances. Doing this may compromise speed and performance.

I see that your site has a valid SSL certificate installed, so the communication attempt should work. Could you try turning Site Accelerator off and on? If that doesn’t resolve the issue, please perform a plugin conflict test by following the steps in this support guide.

Hi @thomastolkien

Thank you for the extra information. The “Undefined array key” error was introduced in PHP version 8.0. Prior to this version, trying to access an undefined array key would result in an “Undefined index” notice. This is why it’s appearing more visible to you now that you’re on a more recent version of PHP.

As I said in the other thread, it’s not something to be bothered about, but it might be worth looking into. Could you please log an issue about this on the public GitHub repository? Thanks!

That’s good to know. Thanks for letting us know.

Note that disabling wp-cron might also disable background syncing for other plugins and services, which may not be ideal. I suppose you took all of that into consideration.

Hi @lextor1993,

I’m sorry for the delay in responding and that you continued to experience this issue. We’ve been working through a backlog of support requests, and replies have been taking longer than normal.

If you’re open to troubleshooting the problem again, please try reconnecting Jetpack as a first step, as we previously suggested. I understand that you’ve had a negative experience so far. We appreciate your patience.

Kind regards.

@chicoist The answer you received in that other thread sounds right. However, if you want us to dig further, please contact us via?this contact form. Right now, it looks like Jetpack isn’t connected on the site mentioned in this thread, so I’m currently unable to track down the site on our system.

@fotov60 Your concerns about the changing IP addresses are totally valid. Our IPs haven’t actually changed in a long while, however we make that statement as a disclaimer as we don’t hold ourselves responsible for communicating to users relying on IP whitelisting to give Jetpack access if they do change.

Also, the line, “You should be able to protect a site’s XML-RPC file without having to allow specific IP ranges,” refers to an ideal scenario, where most hosts should allow general access to the xmlrpc.php file, because many services other than Jetpack, such as mobile apps, rely on XML-RPC to communicate with your site.

Hello @steenmn0

Thank you for reaching out to us regarding the issue you’re experiencing with Jetpack.

Based on the system status report and the error logs provided by your hosting provider, it seems like your PHP memory limit could be a possible issue. Your current PHP memory limit is set to 51MB, while we recommend a minimum of 64MB for a smooth operation of WordPress and its plugins. Low memory can cause unexpected termination of scripts, which can result in errors like “End of script output before headers and mod_fcgid: error reading data from FastCGI server.”

To resolve this issue, please increase your PHP memory limit to at least 64MB. You can do this by contacting your hosting provider or, if you’re comfortable with it, editing your wp-config.php file to include the line define('WP_MEMORY_LIMIT', '64M');.

After updating the memory limit, please deactivate all of your plugins, and then reactivate them one by one, checking each time to see if the problem reoccurs. If it does, then the last plugin activated is likely the cause of the issue.

I hope this helps

Hello,

We’re sincerely sorry to hear about your experience with Jetpack, and we understand your frustration. The behavior you’ve described is not typical for our plugin.

We’d appreciate the opportunity to look into this and help resolve the issues you’ve been encountering. To start, could you please contact our support team via this link?

Please provide us with as much detail as possible about the issues you’re facing, including any error messages and the steps you took. This information will help us understand the problem better and work towards a resolution more efficiently.

Jetpack is designed to enhance your site’s functionality and security, and we’re committed to ensuring that it does so in a seamless and non-disruptive manner.

Kind regards.

Hi @myerrorsandmysolutions,

Unfortunately, changing the code directly is something we wouldn’t recommend as plugin updates will override those changes.

Comments typically show up on a post or page which should have a H1 tag (as defined by the theme) for the post title and H2 tags in the post content for subtitles and section titles.

I think the plugin should allow to setup if use H3 or a different tag.

If you’re convinced that this is a good change to make, please consider opening an enhancement request on GitHub from here: https://github.com/Automattic/jetpack/issues/new/choose

Kind regards.

Hi @sailoraldo

I see you already marked the thread as resolved.

If you’re on the latest version of the iOS app and are still encountering that display issue, please feel free to report it (log an enhancement request) here: https://github.com/wordpress-mobile/WordPress-iOS/issues/new

• This reply was modified 1 year, 5 months ago by Daniel.