Topic-icon AceSEF + K2 + JFBConnect (Fb like button issue)

Active Subscriptions:

None
13 years 10 months ago #25159 by barkł
HI.
I have exactly same problem like Azwanz in this post www.sourcecoast.com/forums/jfbconnect/jf...s-not-recognize-page
I'v tried to change order of the plugins but it didn't help.
I used FB debug and I received info (see attachment)
Maybe you know the solution and how to fix this ?
I have tried to contact with Azwanz but so far no answer.

I contacted with AseSEF support they told me that something wrong is with my URLs.
They told me to turn off Global SEO and check my FBlike button.
When I disabled Glebal SEO my FBlikes button stop working correctly (no graphics, no description).
The same with JFBComments I have message under box "Warning: neurostrada.pl/index.php?option=com_k2&v...definicja&Itemid=148 is unreachable."
Maybe you know how to fix it and what is wrong with my URLs and why FBlike doesn't include graphic and descriptions ?

Best Regards
Bartosz Klosinski
The topic has been locked.
Support Specialist
13 years 10 months ago #25177 by alzander
Bartosz,
Sorry for the delay in getting to this post.

I'm not sure if Azwanz fixed the issue, and if he did, how he did it. Are you seeing this problem only on a specific page of your site, like he was in the post you linked? Or is it on every page?

As for ideas for the cause of the problems.. there's a few. For the Comment box that says it's unreachable, if you look at the Debug Tool for that page ( here ), it shows a response code of 206. The normal 'OK' response code is 200. We've heard of multiple types of issues like you mention and others when the web server is returning 206 codes. The 206 is used for an agressive caching/optimization scheme where the web server only returns a part of the page. It's up to the requester to fetch the rest of the page. While this may be good for speed or something, Facebook seems to have lots of issues with these types of pages. If you know what is causing the 206, you may want to try disabling it, even temporarily, and testing again.

Your image you attached is actually showing the Debug Tool throwing an error about the Response Code. I actually see a 206 value, but your image was showing a 403, which is a redirect. It's possible Facebook is detecting a redirect loop on that page somehow, but I can't see that.

Either way, it definitely seems to be something about the response code that is likely the problem. The only other idea I have is that it's the colon in the URL. While colons are widely used, even by Joomla, they are actually not a valid character for URLs. It's really only meant to be used at the beginning of URLs to separate 'state' information, like is the scheme http or https, is there a username/password required for the site, or is there a port number? A valid use of colons is [email protected]:20 (20 is the port).

Facebook may simply be having a hard time unencoding your URL with the colon in it. Can you check if pages on your site without colons have the same issue?

Hope that helps, and good luck,
Alex
The topic has been locked.