I have been trying for a while now to troubleshoot why the Jetpack plug-in’s “Publicize” feature seems to not be working for Facebook. The other social media seem to share as they should. My client and I have gone through the motions of the forums and support site saying to reconnect and adjust certain settings within Facebook, but we still can’t seem to get it to work.
The support site for the Publicize feature guided me to the FB Debugging website:
https://jetpack.com/support/publicize/facebook/
You can see what Facebook sees and check for errors by entering one of your posts’ URLs inFacebook Debugger.
If the debugger reports an error, you’ll need to fix it for Publicize to start working again.
A common error is a duplicate set of Open Graph meta tags. In such cases, the solution would be to make sure you only use one plugin to manage Open Graph tags.
Another error can be a wrong Facebook Admin ID. In such cases, start by looking for your current admin ID, and then update your Open Graph plugin to use the correct value.
Some themes also manage Open Graph meta tags for you. If that’s the case, you’ll need to edit the theme or contact the theme authors to ask them how to remove Open Graph meta data from your theme.
So I ended up trying this and this was the result:?
Facebook Debugger
https://developers.facebook.com/tools/debug/sharing/?q=www.lifeinapile.com
The support page doesn’t seem to have anything regarding an app_id. But the main page also stated that it may be an Open Graph meta tags issue. I do not fully understand this, how to determine if it is the issue, or to even fix it. The last option says to contact the theme creators to remove the Open Graph meta data from the theme.
However, I want to be careful not to remove anything important and of course to determine if anything must be removed at all.
I also submitted the URL through the open graph debugger, but I do not understand the results:
Open Graphic Object Debugger
https://developers.facebook.com/tools/debug/og/object/
I have browsed through a number of forum posts with variations of the same issue. It doesn’t seem like the issue is ever truly solved, or someone’s situation where it is solved is temporary (they come back and post later), or their situation doesn’t match my client’s enough to try and use the solution.
https://www.ads-software.com/support/topic/facebook-and-publicize?replies=5
https://www.ads-software.com/support/topic/fbadmins- https://www.ads-software.com/support/topic/publicize-broken-again-after-update”>and-fbapp-id-missing-in-add-meta-tags?replies=3
https://www.ads-software.com/support/topic/publicize-broken-again-after-update
https://www.ads-software.com/support/topic/another-jetpack-facebook-sharing-issue
https://www.ads-software.com/support/topic/problem-with-facebook-sharing-3?replies=8
https://www.ads-software.com/support/topic/still-troubles-with-facebook-publicize?replies=10
The debuggers seem to be the most promising, but I’m not sure how to act on the results. Many of the forum answers have something to do with another separate plug-in that deals with meta-data, but to my knowledge, there’s only the basic areas like tags, page title and description that are provided by WP when creating a blog post.
There’s no meta data or SEO plug in or anything. And I searched through the existing ones to see if there might be a similar feature, but I have not come across anything. (I hope I’m simply overlooking).
Even if I found what I was looking for, I wouldn’t quite know how to fix it as my theme creator mentioned not to tinker too much with the theme code as changes might disappear during updates (I’m not sure if that is isolated to CSS changes…).
That being said, the facebook debugger gives me the error that the Share ID is missing. One Jetpack contributor mentioned that it was not a major concern and did not quite address it.
Another provided code to add to the functions.php file but it still did not work:
function amt_extend_og_metatags( $metatags ) {
$metatags[] = '<meta property="fb:admins" content="ENTER_USER_ID_HERE" />'; $metatags[] = '<meta property="fb:app_id" content="ENTER_APPID_HERE" />'; return $metatags;
} add_filter( 'amt_opengraph_metadata_head', 'amt_extend_og_metatags', 10, 1 );
I’m a bit at a loss here. Is there anything else I can do? Have I misstepped somewhere?
Thanks so much!!
Ema Myers
https://www.ads-software.com/plugins/jetpack/
]]>So I thought I’d cut the content in half since it’s very image heavy and may be overburdening the servers. It worked. Then I tried to paste the other half and again, it wouldn’t publish. So I cut that in half and it worked. Then I repeated the process until I had just the last paragraph to add. By now I was adding half a sentence at a time until I could add no more. It’s like Zeno’s race paradox.
The problem seems to be unique to new pages. I can edit old pages just fine. Also, I can update the page without issue from my work computer. I am running the latest Firefox on Windows Vista. The website uses the 2010 theme. The update is more likely to fail if I’ve pasted lots of text or images.
My website is sunriseonilion.wordpress.com unfortunately I can’t link to the trouble page because it is set to private and I can’t change it while it’s broken. The page is nearly identical to this one: https://sunriseonilion.wordpress.com/odyssey/ It has lots of images and text but only two links, and both are internal links. All images are hosted onsite.
I have tried clearing my computer’s cache and rebooting.
I have switched to 2014 theme to no avail.
I have no plugins to disable.
I have tried recreating the page with no success.
I would rather not clear my browser’s cache because it has a lot of important stuff on it.
Due to virus issues I can only run Firefox in vanilla mode with addons disabled at each startup.
I can upload images and videos – BUT – when i click “Insert into Post” I get this message:
Not Acceptable
An appropriate representation of the requested resource /wp-admin/media-upload.php could not be found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
I am using cpanel and I have wordpress 3.3.1
I have deleted all cache memory
I have tried turning the mod_security off (not sure if I did it right tho)
Any help would be appreciated before I tear all my hair out,
Thank you,
Tess
My problem is:
I can’t Save Draft/Publish for HOURS.
I have to keep retrying and retrying and finally hours later it will Save Draft/Publish.
I’ve tried doing my stuff in Mozilla Firefox, I’ve tried it in IE, I’ve tried it in Google Chrome.
I’ve tried turning off all the plugins.
I’ve tried switching to the Twenty Ten theme to rule out theme-specific problems.
Still no joy.
EVENTUALLY the stuff will save draft/publish after many hours of trying and re-trying, but I need to get my posts done in a timely manner – and sometimes I’ve got deadlines, so I need this fixed.
Appreciate any help with this, thanks!
I’m not a coder, I use Headway’s visual editor so I don’t have to touch any code. But even when I had Twenty Ten or Atahualpa, there was the same problem.
And I tried refreshing the page and trying again after I pasted the post contents again. No joy.
And I made sure I had the latest version of everything. No joy.
And I tried the MySQL database check and repair for each database – everything fine, then I tried save draft. No joy.
I tried publish. No joy.
I usually have to try and try and try again for HOURS, sometimes DAYS, then randomly, with nothing different it will suddenly save the draft or publish.
ANOTHER weird thing is that down at the bottom of the draft I’m trying to save/publish, the little line that says when the draft was last saved, will show
“Saving Draft…” and that line will just hang there like that.
Refreshing the page will get rid of it, but then a couple of minutes later it’ll show that same msg and hang there. I’m not talking about the right column with the SAVE DRAFT or PUBLISH buttons, I mean right smack under the box containing the actual draft I’m trying to get to save or publish.
I tried switching from VISUAL mode to HTML mode and then save draft/publish, but that doesn’t work either.
Any help is GREATLY appreciated. I’ve been having this problem for MONTHS
]]>Recently,
I can’t Save Draft/Publish for HOURS.
I have to keep retrying and retrying and finally hours later it will Save Draft/Publish.
I’ve tried doing my stuff in Mozilla Firefox, I’ve tried it in IE, I’ve tried it in Google Chrome.
I’ve tried turning off all the plugins.
I’ve tried switching to the Twenty Ten theme to rule out theme-specific problems.
Still no joy.
EVENTUALLY the stuff will save draft/publish after many hours of trying and re-trying, but I need to get my posts done in a timely manner – and sometimes I’ve got deadlines, so I need this fixed.
Appreciate any help with this, thanks!
I’m not a coder, I use Headway’s visual editor so I don’t have to touch any code. But even when I had Twenty Ten or Atahualpa, there was the same problem.
Thanks everyone!
]]>That last phrase, that actually worked, is extremely important. I realise that not everything works correctly “as is” on every server. But every CMS I have ever successfully used had documentation with it that covered every aspect of the install in step by step instructions.
More to the point, I have never successfully used a CMS that didn’t have information in the <b>”Read Me” or “Install Readme”</b> file regarding the proper [em]permissions[/em] settings for every file in the CMS system.
For example:
1) Upon install I was not allowed to edit and update the Welcome! message. This was a permission problem that I think (I hope) I have resolved. I finally got the post to update, though I never changed any file permissions. Honestly, I do not know how I got it to update other than waiting 24 hours and trying again. And even then, it took several presses of the “Update” button on the admin post editor page.
2) After unsuccessfully trying two alternate theme installs, I switched back to the default theme, twentyten, and tried to upload a new header image. It simply would not allow me to do so. I used chmod multiple times to allow write access and each time I changed it and retried the upload the settings somehow switched back to deny access. Again, after many repeats of this process it finally allowed me to upload the image.
3) I tried to edit the “About” page. The admin panel shows the page to exist. But when I click on the “About” page link on the site main page, it leads to a “404:file not found”. On the admin page, my edits are saved as drafts and show in the page directory. But not even the sample “About” page is available from the site home page.
I have unsuccessfully found nothing that clearly describes what files on the server need to be set with what file permissions. Perhaps I am simply not finding the information. But it would seem to me that such a vital piece of information would be more prominent in the documentation somewhere. It has been with every other CMS I have ever used.
Out of desperation I chmod the entire wp-content folder 777 and recursed into subdirectories and it would still show 404:not found when I click on the “About” page link. So, just for giggles, I have chmod the whole of every file in the WP platform to 777 (absolutely not a good idea for standard operation IMHO) just to see if it would allow me to add the “About” page. And guess what: it didn’t. This platform will not allow me to add images, posts, or pages, which leads me to the only possible conclusion: the package is somehow broken. And I have wasted three days of my life that I will never get back on it.
Please forgive my frustration. WordPress is an attractive CMS. And apparently thousands, if not millions, of people use it all over the world. But I would REALLY appreciate knowing where the secret key to making the platform actually work from the admin panel is. If it doesn’t start working right pretty soon I will reluctantly flush it and start over with a CMS that works. I positively HATE using forums! I hate having to open an account somewhere by giving my email address for something that I have no intention of using more than once or twice. If it takes more than a couple of questions to get running, it is absolutely not worth using.
]]>