Rankmath SEO

Debugger Error og:image on link: [ redundant link removed ]

Why??

• This reply was modified 3 years ago by Jan Dembowski.

Hi @stefa98, thank you for reaching out.

Branded Social Images can overrule the go:image html meta set by RankMath SEO.
If you select an image with RankMath SEO for use as Facebook image, Branded Social Images will use it.
Selection process is:
1. Image selected in BSI Meta box
2. Featured Image (if enabled in settings)
3. RankMath Facebook image
4. Fallback Image (in BSI general settings)

Your second question, I don’t understand. I have checked the page and it’s generated social image (https://www.hynerd.it/apex-legends-mappa-stagione-11/social-image.png/) and I don’t see anything wrong.
Can you please tell us more?

• This reply was modified 3 years, 1 month ago by Internetbureau Clearsite.
• This reply was modified 3 years, 1 month ago by Internetbureau Clearsite.

Ok, I deleted my new function rank math setting to remove og:image and refresh the cache.
But as far as you can see in the Head and in the open graph tests, BSI does not replace the og: image of RankMath with that of BSI

• This reply was modified 3 years, 1 month ago by stefa98.

Hmmm, that is weird. In every test set-up I do with RankMath, the go:image tag is changed to url/of/the/page/social-image.png

I do see that it does not on your website.

I hope you could try out something for me;

in file branded-social-images/lib/class.og-image-plugin.php you will find, around line 340, the following;

add_filter('rank_math/opengraph/facebook/image', [static::class, 'overrule_og_image'], PHP_INT_MAX);

can you add;

add_filter('rank_math/opengraph/facebook/og_image', [static::class, 'overrule_og_image'], PHP_INT_MAX);
add_filter('rank_math/opengraph/facebook/og_image_secure_url', [static::class, 'overrule_og_image'], PHP_INT_MAX);

and see if that solves it?

sorry for the inconvenience.

Ok, yes it works now. I guessed that was the error because going to apply my changes to disable rankmath og image, I also inserted og_image to disable it.

The second problem is the following:

https://www.opengraph.xyz/url/https%3A%2F%2Fwww.hynerd.it%2Fwarzone-the-haunting-2021%2F/

As you can see, the image doesn’t load me. Also from the Facebook Debugger I encounter the same problem.
It is strange, because the image in the head is there, and in the last 3 articles of my site it works correctly.
While on the older ones (2/3 days ago) the image is not displayed.`

I can see it working for
https://www.hynerd.it/apex-legends-nuova-leggenda-nuova-arma/social-image.png/

With
https://www.hynerd.it/warzone-the-haunting-2021/social-image.png/

In can see the following headers:
x-og-error-fail: Generating image failed.
x-og-error-file: Source image not found. This is a 404 on the source image.

Can you verify you set-up the image correctly?

If you’re feeling adventurous; can you look at lib/class.og-image.php around line 150 where it says header('X-OG-Error-File: Source image not found. This is a 404 on the source image.');?

temporarily add var_dump($image_id, $source, $image, $width, $height, $image_file); and refresh the https://www.hynerd.it/warzone-the-haunting-2021/social-image.png/ page

If $image_id is not a number greater than 0, there’s a problem with image selection
$source should be an array with an URL, a width and a height, and optionally a file-type.
$image should be an URL to the image, try to access it in the browser
$with and $height should match the dimensions of the image
$image_file should be a valid file-path.

Hopefully this will help you and me in the direction of a solution.

Where should I add var_dump? In the header?

On it’s own line directly above or below the header line, please.

Ok, so I was done, but it shows me a blank page.

(comment deleted)

• This reply was modified 3 years ago by Remon Pel. Reason: wrong account

email sent

a recap for future reference;

– a caching plugin interfered with displaying the debugging information
code has been added to prevent this in future.
– a CDN plugin interfered with getting the image source
code has been expanded to use a few different methods of getting the image-file-path.

changes will be reflected in version 1.0.12.

@stefa98 Please revoke any access to the developer or their coworkers. @clearsite and his coworkers will be banned from the forums if they repeat that.

@clearsite I have archived your ask and flagged your account for moderation.

While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.

You are absolutely right, Jan. And it really was a last-resort type of situation.

It will not happen again. The plugin should now have more than enough logging to allow debugging without us doing the debugging ourselves ??

We try hard to help everyone but we must accept that it is not always possible.