Problem with og:image when publishing on FB

  • Resolved Geoffray

    (@geoffray)


    11 years, 10 months ago

    Hello,

    I have a “big” problem and i can’t find the issue, it would be great if someone can help me for that because it’s very hard for me to find the cause, i’m not enough clever 😉

    I just updated SQL on my VPS few days ago, i had some pingdom alerts with 403 errors and after adding and removing the Frontpage extensions, it seems to be ok (and i don’t now why!!!)

    Everything is updated and with the latest version.

    And now, when i publish articles on my website, the publicize do it’s job but can’t find the picture. So it’s a big problem for me! When i check the Facebook debugger, it’s ok, i can see the picture and when i try to share the link, it’s ok too, i can see the picture! But when i’m doing it automatically with publicize, it’s not good…

    I use the “suscribe” plugin too from Jetpack and now pictures are not readable on my email… and i’ve found where is the problem!

    On publicize and suscribe module from Jetpack, the url of my pictures are standard. When i want to click on it, i’m automatically redirect to my homepage!You can check that url : http://cdn.1max2peche.com/wp-content/uploads/2014/07/montage-carpe-blow-back-rig-01-850×566.jpg

    Now when i check the picture from my article, i can see that URL have something else : http://cdn.1max2peche.com/wp-content/uploads/2014/07/montage-carpe-blow-back-rig-01-850×566.jpg?e0e712

    And now, when i go to this adress, i can see the picture. I think that Facebook debugger do the same : when i share manually my link, i can see that the URL used is with the ?e0e712 extension, and it works. But when it’s send by email and publicize, there is no extension like ?e0e712 and it redirect to my homepage.

    I have W3C and WordPress SEO plugins, i think it could be a rewrite problem, but i really don’t know what’s happening. Any idea? Something to check?

    https://wordpress.org/plugins/jetpack/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Geoffray

    (@geoffray)

    11 years, 10 months ago

    Problem solved for my main domain, i had some strange URL rewritting in my .htaccess file, at the end.

    I don’t know wich plugin can edit this, perhaps Apache when rebuilding in a new version?

    RewriteCond %{HTTP_REFERER} !^http://1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://1max2peche.info/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://1max2peche.info$      [NC]
RewriteCond %{HTTP_REFERER} !^http://annonces.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://annonces.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://annuaire.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://annuaire.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://beaujolais.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://beaujolais.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://forum.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://forum.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://galerie.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://galerie.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://jeu.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://jeu.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://mozzo.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://mozzo.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://netdna.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://netdna.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://social.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://social.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://spots.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://spots.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.1max2peche.info/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.1max2peche.info$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.annonces.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.annonces.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.annuaire.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.annuaire.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.beaujolais.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.beaujolais.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.forum.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.forum.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.galerie.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.galerie.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.jeu.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.jeu.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.mozzo.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.mozzo.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.netdna.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.netdna.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.social.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.social.1max2peche.com$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.spots.1max2peche.com/.*$      [NC]
RewriteCond %{HTTP_REFERER} !^http://www.spots.1max2peche.com$      [NC]
RewriteRule .*\.(jpg|jpeg|gif|png|bmp)$ http://www.1max2peche.com [R,NC]

AuthName 1max2peche.com
IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*
    Thread Starter Geoffray

    (@geoffray)

    11 years, 10 months ago

    Seems to be the Frontpage extension of my VPS server that write this in all my .htaccess files and make the problem… now solved! 😉

    PPDPurveyor

    (@peoples_pundit)

    11 years, 9 months ago

    Can I ask how you stopped that Geoffray? I just migrated to a dedicated server and have started to see the same garbage on my htaccess file, as well. All the Twitter Cards and Facebook posts were not showing images, and even images on front end of site were not displaying. I removed that and viola. But it will likely be back, right?

    Thread Starter Geoffray

    (@geoffray)

    11 years, 9 months ago

    I just erase the lines above. That was lines wrote by Frontage extensions and make me those 403 errors. After editing the main .htaccess and removing the _vti folder, it was ok, and still ok now 😉

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Problem with og:image when publishing on FB’ is closed to new replies.