StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POFB OpenGraph og:image not pulling images (possibly https?)
text
Body
copied!<p>First -- I <strong>do not</strong> believe this is a duplicate issue. I've searched for same or similar problems on SO extensively, and due to the nature of troubleshooting before asking, I believe this problem is unique. </p> <p>Facebook cannot grasp my <code>og:image</code> files and I have tried every usual solution. I'm beginning to think it might have something to do with <code>https://...</code></p> <ul> <li>I have checked <a href="http://developers.facebook.com/tools/debug">http://developers.facebook.com/tools/debug</a> and have zero warnings or errors.</li> <li>It is finding the images we linked to in the "<code>og:image</code>", but they're showing up blank. When we click the image(s), however, they DO exist and it takes is straight to them.</li> <li>It DOES show one image -- an image hosted on a non-https server.</li> <li>We've tried square images, jpegs, pngs, larger sizes and smaller sizes. We've put the images right in public_html. Zero are showing up.</li> <li>It's not a caching error, because when we add another <code>og:image</code> to the meta, FB's linter does find and read that. It DOES show a preview. The preview is blank. The <strong>only</strong> exception we're getting is for images that are not on this website.</li> <li>We thought maybe there was some anti-leach on <code>cpanel</code> or the <code>.htaccess</code> that was preventing the images from showing up, so we checked. There was not. We even did a quick <code>< img src="[remote file]" ></code> on an entirely different server and the image shows up fine. </li> <li>We thought maybe it was the <code>og:type</code> or another oddity with another meta tag. We removed all of them, one at a time and checked it. No change. Just warnings. </li> <li>The same code on a different website shows up without any issue. </li> <li>We thought <em>maybe</em> it was not pulling images because we're using the same product page(s) for multiple products (changing it based on the get value, ie, "details.php?id=xxx") but it's still pulling in one image (from a different url).</li> <li>Leaving any <code>og:image</code> or image_src off, FB does not find any images.</li> </ul> <p>I am at the end of my rope. If I said how much time myself and others have spent on this, you'd be shocked. The issue is that this is an online store. We absolutely, positively cannot NOT have images. We have to. We have ten or so other sites... This is the only one with <code>og:image</code> problems. It's also the only one on <code>https</code>, so we thought maybe that was the problem. But we can't find any precedent anywhere on the web for that. </p> <p>These are the meta-tags:</p> <pre class="lang-html prettyprint-override"><code><meta property="og:title" content="[The product name]" /> <meta property="og:description" content="[the product description]" /> <meta property="og:image" content="https://www.[ourwebsite].com/images/shirts/overdriven-blues-music-tshirt-details-black.png" /> <meta property="og:image" content="https://www.[ourwebsite].com/images/shirts/overdriven-blues-music-tshirt-art-black.png" /> <meta property="og:image" content="http://www.[ADIFFERENTwebsite].com/wp-content/uploads/2011/06/ARS-Header-Shine2.png" /> <meta property="og:image" content="https://www.[ourwebsite].com/images/ARShopHeader.png" /> <meta property="og:image" content="http://www.[ourwebsite].com/overdriven-blues-music-tshirt-art-black.JPG" /> <meta property="og:type" content="product"/> <meta property="og:url" content="https://www.[ourwebsite].com/apparel-details.php?i=10047" /> <meta property="og:site_name" content="[our site name]" /> <meta property="fb:admins" content="[FB-USER-ID-NUMBER]"/> <meta name="title" content="[The product name]" /> <meta name="description" content="[The product description]" /> <link rel="image_src" href="https://www.[ourwebsite].com/images/shirts/overdriven-blues-music-tshirt-details-black.png" /> <meta name="keywords" content="[four typical keywords]"> <meta name="robots" content="noarchive"> </code></pre> <p>In case you want it, here's a link to one of our product pages that we've been working on. [Link shortened to try to curb this getting into search results for our site]: <a href="http://rockn.ro/114">http://rockn.ro/114</a></p> <p>EDIT ---- </p> <p>Using the "see what facebook sees" scraper tool, we were able to see the following: </p> <pre class="lang-js prettyprint-override"><code>"image": [ { "url": "https://www.[httpSwebsite].com/images/shirts/soul-man-soul-music-tshirt-details-safari.png" }, { "url": "https://www.[httpSwebsite].com/images/shirts/soul-man-soul-music-tshirt-art-safari.png" }, { "url": "http://www.[theotherNONSECUREwebsite].com/wp-content/uploads/2011/06/ARS-Header-Shine2.png" } ], </code></pre> <p>We tested all links it found for a single page. All were perfectly valid images. </p> <p>EDIT 2 ----</p> <p>We tried a test and added a <em>subdomain</em> to the NONSECURE website (from which images are actually visible through facebook). Subdomain was http://img.[nonsecuresite].com. We then put all images into the main subdomain folder and referenced those. It would not pull those images into FB. However, it would still pull any images that were referenced on the nonsecure main domain. </p> <p>POSTED WORKAROUND ----</p> <p>Thanks to Keegan, we now know that this is a bug in Facebook. To workaround, we placed a subdomain in a different NON-HTTPS website and dumped all images in it. We referenced the coordinating <code>http://img.otherdomain.com/[like-image.jpg]</code> image in <code>og:image</code> on each product page. We then had to go through FB Linter and run EVERY link to refresh the OG data. This worked, but the solution is a band-aid workaround, and if the <code>https</code> issue is fixed and we go back to using the natural https domain, FB will have cached the images from a different website, complicating matters. Hopefully this information helps to save someone else from losing 32 coding hours of <em>their</em> life. </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload