rashadow

I have this issue too. No solution yet, but deactivating the photon module in Jetpack is a temporary fix. Check this other thread where more people are experiencing the same issue: https://www.ads-software.com/support/topic/photon-failure-messages-in-header-and-post

Great news to wake up to (I appreciate the little things in life). All clear here as well ?? I guess we can call this one resolved…although the root issue was never discovered.

Way off the mark with that last post. Went poking around the db to see if I could manually add a mention, but the string is something like: a:6:{i:0;a:2:{s:2:”id”;s:15:”104046862964234″;s:4:”name”;s:7:”Writing”;} — that would be the “Writing” page on FB.

I’m gonna leave this alone now. Hopefully someone will come along and fix this for us.

On a side note. I noticed that most of the custom field names still existed so I just added the custom field “fb_mentioned_pages” and added my own page as a mention and created a test post https://silenciobarnes.com/test-2/test-no-need-to-click-me/

I ended with an error on plugins/facebook/social-publisher/mentions.php on line 34 but the actual mention still resolved to the correct FB ID# on the edit screen once the post was saved

Don’t know if that helps anyone…but I’m tryin! ??

Same issue here, still a problem as of ver. 1.1.8, not sure what caused these fields to disappear. I have no mentions, and no custom status to page fields when creating new posts. I DO have the custom status to timeline field, but that’s it. The mentions that I used in a previous post still show on said post, but the option to add mentions to posts has completely disappeared.

I tried the above mentioned troubleshooting options to no avail. Since there aren’t a ton of people crying foul on this issue, I’m assuming many of us have something in common that may be causing this issue. The only plugin I have in common with one of the above posters is NextGen – maybe there is some setting missing on our FB apps…I dunno.

my site is silenciobarnes.com

It looks like the guys over on this thread are having the same issue: https://www.ads-software.com/support/topic/mentions-missing

Something must have changed as I’m able to connect again.

Same issue, same host. I thought it was just me since there were no complaints here in the forum. I noticed a few days ago that my stats stopped working. I thought maybe the wp.com connection was a little wonky so I disconnected and got this error when I tried to reconnect.

I think the issue may be on Fatcow’s side (or Cloudflare’s if we all have that in common as well). I tried older versions of the plugin and they all fail to connect.

On a side note, if anybody is using the facebook for wordpress plugin, I found that once jetpack was deactivated, a few issues I had with the facebook plugin were resolved as well :/ go figure.

My site is silenciobarnes.com

Just chiming in here to confirm that the fix suggested by bmex63 worked for me using Redirection 2.2.13 and WordPress 3.4 on my main site https://silenciobarnes.com

Replace tools.php?page=redirection.php with just redirection.php

After that I was able to export a CSV and view the RSS

As for the dude that asked about the CSV format, I had the same question – if you didn’t understand mike.ianni’s answer it’s like this

3 Columns
source | target | hits
You don’t have to put anything into the hits column

I created a few test csv files and successfully uploaded them. The name of the file doesn’t matter.

It looks like he added lines but did not modify any existing lines

line 25: if(!class_exists(‘FacebookApiException’)):

lines 110-112: endif;

if(!class_exists(‘BaseFacebook’)):

line 1148: endif;

Compared the base_facebook.php contained in wpbooklite client folder with the copied pastebin using winmerge – https://winmerge.org/

Just to add: I was having problems with getting the ‘SEO Facebook Comments’ plugin to play nice with WPBook and WPBook Lite. While SEO FB Comments was active, I would receive a 500 internal error when trying to view the FB version of my blog with WPBook. With the Lite, I would get a 500 internal error on the settings page, so I couldn’t even configure it.

I tried the changes to base_facebook.php that Sabuj kundu listed above and it looks to have solved my problem. The commenting system is working and I can get into the WPBook Lite settings. At this time, I have yet to post a new post or retry WPBook to see if all is well yet. But the fact that there are no 500 errors gives me hope. Site is https://silenciobarnes.com

Changed title back to “not resolved”

I had not noticed at first, but this problem also happens with my category pages – I unchecked the show in category option, but the problem persists.

This problem is probably related to gillespieza’s in some sort of way as well.

You can see it in action here: https://silenciobarnes.com/category/random-thoughts/

Not working for me neither. I’m not even sure when it stopped working.I pretty much came to rely on it to post to my Myspace blog and to post to all three supported sites when I edit a post.

Unfortunately, I don’t think there are any alternatives that crosspost directly to the myspace blog. If anybody reads this and knows of one, please let me know!

The author of this plugin has been MIA for a while. His site hasn’t had any updates in several months. I hope he comes back and updates it someday or maybe someone else will. Wish I had the expertise to get it back to operational myself ??

Does anybody know of an alternative?!?!?!?

…why didn’t I think of that :/

Thanks Ahmed ??

It seems the latest version is still the development version – there was a mix-up in the readme file – 0.9 is not a true stable release. According to Fred Townes, you can still use it as there has only been a couple of bugs reported so far, but you may want to revert to the previous version for stability. If you check the plugin page, you’ll see that it’s reverted back to 8.5 as the latest release.

https://twitter.com/w3edge

apologies to anyone who caught the v0.9 development release as a stable release. i didn't catch the mistake for a couple hours.

— W3 EDGE (@w3edge) June 17, 2010

I’m not too concerned with it. After all, wordpress 3.0 is about to drop any day now and that means there’s probably a new release of W3TC coming as well. Figured I’d wait for both of those and then tackle the problem fresh ??