× Joomla Facebook Connect support forum

Topic-icon Integration stopped working after moving site

Active Subscriptions:

None
14 years 4 months ago #18189 by fabram
My website was moved from an additional domain to a single account in the same server. No changes in the configuration files were done. However, the integration stopped working. I use K2 and Addthis sharing tools. When I click to share on Facebook no image or description comes up. The comment module is also not working.
In the following link all og properties are set right, but I get error code 406 when using Facebook debugger
www.capimgrosso.net/noticias/noticias-lo...do-de-novo?-n%C3%A3o
On the comment module at the bottom of the article the link always comes up pointing to the same category "educação"no matter in which category the article is listed and says it is not available
Attention: www.capimgrosso.net/educacao/item/3669-e...012-tudo-de-novo?-is not available.
Please help
The topic has been locked.
Support Specialist
14 years 4 months ago #18201 by alzander
Fabio,
URLs should not have question marks in them, unless it's to specify a query string. If you look at pages from your site that don't use a ? (or have it at the end of the URL), things seem fine:
http://www.capimgrosso.net/noticias/noticias-locais/fabio-ramos/item/3658-samuel-celestino-contra-brasileiro
http://www.capimgrosso.net/noticias/noticias-locais/fabio-ramos/item/3660-o-que-pensam-os-prefeitur%C3%A1veis?
Facebook is simply having trouble understanding what that URL is, and isn't able to decipher it. Things like that will also cause problems for search engines and anything else that automatically scans your content. I'm not sure what SEF extension you're using, but it shouldn't be generating the ? in the middle of a URL like that. You may need to exclude ?, but you may need to explicitly force it from using the ? in the URL.

My guess is that you were having this issue on the site before the transfer, but didn't notice it with the URLs you were testing.

Hope that helps,
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 4 months ago #18217 by fabram
Alex,

It doesn't matter how the URLs look, the problem appears in all URLs on my site and started right after the move. I have reinstalled the component, tested making changes to SEO options and htaccess and nothing solves it.
I am using SimplemSEO plugin
The topic has been locked.
Support Specialist
14 years 4 months ago #18224 by alzander
Fabio,
Did a little more research. I think I found the problem. Your HTML structure isn't correct. If you look at the source HTML on the page, at the very top, you'll see the first tag is <head> then <html>. It should be the other way around. I think Facebook simply can't parse your page at all, and is therefore throwing the 406 error, which translates into "Not Acceptable".

Fix that, and hopefully you'll be good to go.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 4 months ago #18253 by fabram
Hi Alex,

I believe you tested my site when I was trying a fix I found at another forum. The positions of the <head> and <html> tags were not the cause of the problem. They are back in the right positions and problem persists on every URL on my site. I just made a clean install of Joomla, updated the template and JAT3 plugin, went back to original Joomla .htaccess file and nothing works. Cant understand what is going on.
Can you check my tags again and see what can be done? Right now I am not using SimpleSEO plugin
Thanks
The topic has been locked.
Support Specialist
14 years 4 months ago #18260 by alzander
Fabio,
I'm honestly not sure then. It seems like Facebook simply doesn't like something that's configured about your server. Browsers are much more lenient about the data they accept. Automated tools can be very specific in what the expect to see.

Looking at your page, response headers, and everything else we've checked, things all look correct. Is there anyway to look at the old server (through IP address or some other domain name) that you can see if the Debug Tool is able to accurately look at the page? It can even be a different domain, just want to see if the overall server has an issue, or just your slice of it. That will help to determine if it's difference in the domain configurations or something else. I've used some other automated tools, and they all report the page is good.

Unfortunately, I don't think this is a JFBConnect issue at all and is more on Facebook's end. The best I can say, if doing a domain to domain comparison doesn't help, the next step would be that you'd have to contact Facebook to see if they could investigate. There's simply not much we can do on our end since everything does look right from what we see.

Alex
The topic has been locked.
Active Subscriptions:

None
14 years 4 months ago #18294 by fabram
Alex,

I did a new install of Joomla and installed JFBConnect. Still, it does not work. Can you check my settings again?
www.capimgrosso.net
The topic has been locked.
Support Specialist
14 years 4 months ago #18297 by alzander
Fabio,
I looked at the page and quickly at your configuration in the admin area. Again, I don't think there's anything wrong with Joomla on up. I think it's more of a server issue. You mentioned you moved from another server (or within the same server). Have you checked if pages on the 'old' server (even if from a different site) have this issue with Facebook? I don't know what could be incorrectly configured at the server (Apache) level, but it seems like it's specific to that, not the Joomla installation itself.

Please test from the 'old' server and do a comparison however you can. Hopefully, something will come to light which will help us figure out why Facebook is treating the domain on the 'new' server differently.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 4 months ago #18414 by fabram
Problem was solved by server administrator. Thanks
The topic has been locked.
Support Specialist
14 years 4 months ago #18420 by alzander
Fabio,
Very glad to hear it. I really didn't think it was anything we could fix, but I hate pointing the finger elsewhere. It's not something we do often.. in this case, it seemed correct though.

If you have any information on the server change that broke (and fixed) the issue, we'd love to have it for future reference.

Thanks for your patience and debugging of the issue though,
Alex
The topic has been locked.