Forum Replies Created

Viewing 15 replies - 91 through 105 (of 732 total)
  • Plugin Author Chuck Reynolds

    (@ryno267)

    Well (1) Thanks for leaving a rating NateBeaty – much appreciated. and (2) if you have suggestions that could benefit the plugin and other users feel free to let me know on github. Also new(ish) beta is almost finished that may have some of the changes you’re talking about?
    Anyways here: https://github.com/chuckreynolds/WPFBOGP/tree/develop

    Thanks again. Cheers

    Plugin Author Chuck Reynolds

    (@ryno267)

    👍
    for reference there are the required image sizes needed listed here: https://github.com/chuckreynolds/social-profile-image-sizes

    Plugin Author Chuck Reynolds

    (@ryno267)

    Hey andjelahn, On your home page and blog posts it’s showing the default image as well as another image related to that page/post. Facebook should allow you to choose the image when you post to FB (see this example of your post, the arrows in the top left: http://i.imgur.com/kIm24Fd.png )

    In a future release of this plugin (in beta) I’m making it so only one image will ever be given to FB so there’s no ‘leaving it up to FB to choose’ but I’m not done testing all the changes yet.

    Hope that helps. Cheers!

    Plugin Author Chuck Reynolds

    (@ryno267)

    yeaup – i’ll get that in the beta. issue already created – ty: https://github.com/chuckreynolds/WPFBOGP/issues/65

    Plugin Author Chuck Reynolds

    (@ryno267)

    Hey thistleandvine – just got back from vaca so I’m catching up here…

    Problem 1. the app_id thing. You don’t need both the App ID and the Admin ID – unless you specifically want the Insights connected with your Facebook App you don’t need it. It seems to be the wrong ID anyways so I’d suggest just removing it from the plugin settings and using Insights as your personal FB ID. If you’d rather use your FB App then remove the Admin ID and fix the App ID.

    Problem 2. image selection. The release of the plugin that’s on the WP plugin repo is older. While still functional, Facebook changed some things in how they select an image to display. The plugin pulls all possible images from the post/page content as well as the image from the settings, if included. FB used to choose the one at the top of the array (or bottom – can’t remember now) and I had made my array of images work to that – then they changed it. They used to have an image select arrow display to select the image and they removed that feature a while ago. Today actually I noticed they added it back?? so maybe they’re bringing that back? idk… thing is they change stuff constantly and there’s not much I can do about it; except one thing…

    That said… in the new beta of this plugin I’ve been far more specific as to not give FB a choice anymore… I have to finish testing that plugin… I’ve not had a lot of time recently due to client work etc. That will be finalized soon(ish).

    Plugin Author Chuck Reynolds

    (@ryno267)

    @sncrodriguez you should create a new thread. but from what I can tell you’re using content=”WPSSO 3.21.5G -UM” and not this plugin. can’t help too much there. Cheers

    Plugin Author Chuck Reynolds

    (@ryno267)

    Hey jpnava,

    First – there’s something else, your theme or another plugin, that’s adding in the facebook app ID into the source – luckily it’s the same as the one you have in this plugin but i’m sure FB is’nt liking the fact there are two of them. So look into that.

    Okay… Home page pulls only this image:

    <meta property="og:image" content="http://deviaje.jpnava.com/wp-content/uploads/2016/01/home.png"/>

    The contact page pulls two:

    <meta property="og:image" content="http://deviaje.jpnava.com/wp-content/uploads/2016/01/home.png"/>
    <meta property="og:image" content="http://deviaje.jpnava.com/wp-content/uploads/2014/10/contant1-1024x533.jpg"/>

    From that I’m assuming you have the /2016/01/home.png image set in the plugin settings as the default image?

    The way the current plugin works… it takes the default image and puts it at the top of the image array of any featured images or images found in content. Facebook used to allow selection of images – well they changed how they pull images now so sometimes you’ll get that first one… sometimes they’ll randomly choose one… sometimes they don’t pull any. I can’t explain it… it pisses me off… and they change how it works constantly.

    That said. I’ve been slowly rebuilding how that image declaration works in the new beta, which is mentioned in a sticky on this support forum, and I just need more testing to finalize it and release it. That should better generalize the image declaration process to not give FB as many chances to screw it up. I’d love to get that done before the end of February but I’m pretty slammed with client stuff.

    Also make sure to run your site pages through the FB debugger – it clears FB’s cache and can sometimes help with those image selection issues:

    Hope that helps. Cheers.

    Plugin Author Chuck Reynolds

    (@ryno267)

    Good question Sean,
    When this plugin was released the object caching worked pretty good with plugins that modified page titles and descriptions. That since has changed. I’m slowly finishing a new version that addresses that issue; at least the titles. No simple way to get descriptions out other than adding in a check for each major seo plugin to see if it’s outputting a desc code; not exactly into doing that but the titles work much better at least.

    The problem with keeping a plugin simple is… it’s not simple lol.

    I have the beta up on github if you’re interested in testing; that info is listed in the sticky in this support forum. Otherwise I hope to get it to a releasable point in late February after my trips.

    Thanks for the support man. Cheers!

    Plugin Author Chuck Reynolds

    (@ryno267)

    Hey I was super busy today but I wanted to thank you very much for that. Definitely didn’t have to do that. But I appreciate it 🙂
    Have a good one! Cheers!

    Plugin Author Chuck Reynolds

    (@ryno267)

    Okay few things here:

    1. the image you have in settings isn’t an image, it’s a link. You have http://audreyclement.com/sunflower_yellow_kstroke when it should be the actual image ending in .png or .jpg. You’re linking to a page that shows the image, not the image.
    The direct link for that specific image, being served from wp.com is this:
    http://i2.wp.com/audreyclement.com/wp-content/uploads/2016/01/Sunflower_yellow_Kstroke.gif

    2. your admin settings field you have your facebook link, not your facebook user ID. an ID is your ID number, not a link. You have this: https://www.facebook.com/Audrey.R.Clement when you need a number in that field. To find that go here:
    – go to https://facebook.com/insights
    – click “Add Your Domain”
    – in that window that pops up add your site to it but also look at the ID number it displays. put that number, and only that number, in this plugin’s settings.

    3. SO this one is technically optional…. but you don’t need both an Admin ID (#2 above) AND this App ID. You need one or the other. Reason being is what this is doing is telling facebook where you want to track Insights for this domain… either on your personal ID or your App’s ID. So that’s up to you but you don’t need both.

    Do that homework and that should get you going. Cheers! 🙂

    Plugin Author Chuck Reynolds

    (@ryno267)

    w/o knowing your url to look at I can’t be too much help. maybe the image is being blocked from being seen by the facebook scraper? idk.

    Plugin Author Chuck Reynolds

    (@ryno267)

    So back when that was released Facebook was good about having multiple images and always displayed the last one in the array first; so having the default image as the first was fine. At one point they flipped it… so did I… then they went back to the original way. So I flipped it back.
    Then FB was giving arrows to cycle through them… and that functionality is still there, but only rarely. The way I’ve rebuilt the new one is a little different. Again if you go to github in the develop branch and read that readme it explains the new way it’ll work.

    Hope that helps you out. Cheers.

    Plugin Author Chuck Reynolds

    (@ryno267)

    Hey BloggerDave, actually that was the intended usage of it, and if you look at the changelog I changed it a couple times trying to keep up with how Facebook pulls the image array order.
    I’ve got a new version ready to release that completely rewrites the way images are handled anyways. If you look at the readme you’ll see the github link and in the “develop” branch that pre-release version is there.

    Plugin Author Chuck Reynolds

    (@ryno267)

    so your Admin ID or App ID has nothing to do with an image. If the page you’re testing isn’t a single post then putting a default image url in the plugin settings will use that image for FB. That image needs to be at least 600 x 315 minimum, as per Facebook best practices.

    Plugin Author Chuck Reynolds

    (@ryno267)

    If it’s the initial share when you’ve posted something new it has nothing to do with width/height not being declared – FB does a pretty good job of figuring that out themselves. It just means they haven’t scanned your site yet and the scraper didn’t get it initially when you posted the link. You should use the debugger to get their caching engine to work properly; I”ve had to do this for new youtube videos i’ve posted or even news posts that are new like cnn stuff or other big sites. I’ve had to run them through the debugger to get FB to pull an image at all or the right image. It’s just FB.
    Debugger is here: https://developers.facebook.com/tools/debug/

Viewing 15 replies - 91 through 105 (of 732 total)