Log in | Register
  1. Forum
  3. Discontinued Products
  5. JFBConnect v8.x Support (Joomla 3 Only) (CLOSED)
  7. De-Authorization Callback URL

Topic-icon De-Authorization Callback URL

Active Subscriptions:

None
11 years 10 months ago #45637 by lightstyle
Hi Alex,

Until a couple of weeks ago Facebook was blocking our url. I am not sure if it was a complain to Facebook or the fact that McAfee had flagged us as risky/malicious website.

To resolve it I managed to reach Facebook via their advertising program and was told the case was being forward to the proper department in US. At the same time I have requested McAfee to review their rating. We are now marked as clean with McAfee and all other scans and can post our url on our Facebook page.

I then went to run JFB Connect Auto Tune and have managed to create a FB App (couldn't before) but I still cannot publish the De-Authorization Callback URL. JFB says: Facebook API Error: Your message couldn't be sent because it includes content that other people on Facebook have reported as abusive.

I have tried to add the url via Facebook but even though it has accepted every other field/url it still says: This url has been identified as malicious and/or abusive.

Any bright ideas?

Thanks,
Andre
The topic has been locked.
Support Specialist
11 years 10 months ago #45644 by alzander

I then went to run JFB Connect Auto Tune and have managed to create a FB App (couldn't before) but I still cannot publish the De-Authorization Callback URL. JFB says: Facebook API Error: Your message couldn't be sent because it includes content that other people on Facebook have reported as abusive.

I have tried to add the url via Facebook but even though it has accepted every other field/url it still says: This url has been identified as malicious and/or abusive.

When you try on the Developer page from Facebook, is it only the De-authorization Callback URL that throws that error, or do other settings like Website URL, Domain, Page Tab URL (if set) also throw that error?

Unfortunately, JFBConnect can't get around any blocks that Facebook has imposed for your app. If you can't set it through the developer area either, its definitely an indicator that they are blocking your site (or IP) for some reason.

Let me know what settings specifically can't be set, and we'll help however we can. Please understand that we're very limited in what we could do though.

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

None
11 years 10 months ago #45661 by lightstyle
Hi Alex,

Only the De-authorization Callback URL throws that error. All other settings have been accepted and shows as green under JFB's autotune.
The topic has been locked.
Support Specialist
11 years 10 months ago #45707 by alzander
Sorry for the delayed response. I'm not sure why the de-auth callback url would throw that error. The only thing I can suggest is trying to set the URL just to your home page, to see what happens. Mainly that will help diagnose if it's something with the query string (unlikely) or the domain itself.

Honestly, it's not a big deal. The de-auth callback URL is only set by JFBConnect so that Facebook can alert your site if a user has deleted your app. That will show up in the JFBConnect -> Usermap area as "Authorized". It's really only good for some analytics, as we don't use that value for anything else within JFBConnect.

Bottom line: If all other features work as you expect, I wouldn't worry about the de-authorization callback URL.

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

None
11 years 10 months ago #45711 by lightstyle
Hi Alex,

Facebook has accepted homepage URL. Once I add index.php?option=com_jfbconnect&task=deauthorizeUser it throws error message. Good to know that de-auth callback URL is not a big deal, but thought I'd might let you know how it went anyway.

In the mneantime should I leave Deauthorize Callback URL empty or with homepage URL?

Thanks,
Andre
The topic has been locked.
Support Specialist
11 years 10 months ago #45719 by alzander
Andre,
Strange that the query string is what's causing the issues. We haven't heard of that at all before and are not sure what would be causing that. You could do some more testing, like with just "index.php" and then adding each param of the query string, if you care.

If you don't care about the little checkbox for "Authorized" in the usermap, I'd just leave the De-Auth callback URL blank and be done with it.

Please let me know if you need anything else, and thanks for your patience,
Alex
The topic has been locked.
  1. Forum
  3. Discontinued Products
  5. JFBConnect v8.x Support (Joomla 3 Only) (CLOSED)
  7. De-Authorization Callback URL
From the Blog
Facebook | Twitter | LinkedIn | Blog RSS