Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • I have the same problem with Safari browser and submitting attachments.

    There is also an issue with using Chrome browser in the submission is received in raw data, not viewable formats.

    Without the attachment option, both browsers work correctly.

    Thread Starter snapshot3

    (@snapshot3)

    Sorry I have not been back sooner … schedule is quite hectic right now.

    It seems when I allow Jetpack to Publicize to FB it almost always wants to use the wrong image instead of the Featured Image I have selected. Then when I use either the Jetpack generated short link or the full permalink from the post in the FB debugger, it shows the correct image for go:image … only once in the FB Debugger did it show errors for the post link, but when trying a second time on the debugger, it shows the proper image.

    So I am at a loss as to how to correct the issue … if the Jetpack Publicize links work in the Debugger, but not in actual use … I don’t know what more I can do …

    Thread Starter snapshot3

    (@snapshot3)

    Jeremy, I think I may have stumbled onto something. I’ll let you be the judge.

    I tried to manually publicize a post doing a copy and paste of the “Custom Message” generated by Jetpack Publicize including the short link provided … the result was FB wanted to use the wrong image …

    However, each time I share a post and use the actual permalink of the post in question, FB shows the proper image … every time.

    Also … I see this thread is marked “resolved” … i find that curious as the issue still exists, regardless if the situation is the result of Jetpack Publicize or if the flaw is on Facebook’s end of the equation. To me, until this function has reached an amicable resolution … it is not truly resolved.

    I’m not trying to tell you how to run your forum, but the tag is misleading for anyone who may experience the issue in the future.

    Thread Starter snapshot3

    (@snapshot3)

    That is what is so perplexing … FB’s very own debugger widget can recognize the proper data … why is the information getting lost in translation? …

    ***that was a rhetorical question*** … not a dig on jetpack …

    I have the same issue when I publicize a post to Facebook … it’s like Russian Roulette … sometimes it uses the Featured Image I have designated … sometimes it does not … when I run the URL for the posts in question on the FB Debugger … it shows the correct Featured Image … with no errors …

    Conversely, if I manually share the post to my FB page, or if I use the jetpack FB share link in the post itself … it always uses the proper image.

    Hal, Would you consider creating another widget using a different, more accurate source? I would even be happy to pay for such a widget if it was a premium offering …

    I’m having the same issues. Current temps are as much as 10 degrees F lower than actual … predicted high temperatures are off by an average of 10-15 degrees F … then the high and low temps are always the same as the current temperature …

    I love the clean design simplicity of the widget and the ability to add my own images in the background … but the info shared is so far off accurate as to render the widget useless … if there is not a fix in the near future, I’ll either have to use something else or forego a look at the weather in the sidebar altogether …

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