× Joomla Facebook Connect support forum

Topic-icon API errors

Active Subscriptions:

None
15 years 9 months ago #4584 by jannis
API errors was created by jannis
I am trying to work through the basic set up of the API and having some troubles. I used the configuration guide to set up the API on Facebook but the tabs in Facebook did not match the guide. I could not find the Connect url in the application setup screens on Facebook. I suspect that FB has changed their layout since the configuration guide was written. I tried to wing it but I have obviously missed something.

Here is the error I am getting when trying to use the Connect feature:

API Error Code: 100
API Error Description: Invalid parameter
Error Message: next is not owned by the application.

I appreciate any help
The topic has been locked.
Support Specialist
15 years 9 months ago #4603 by alzander
Replied by alzander on topic API errors
Holy moly. They changed the interface slightly back in July, and we knew we needed to update the guide. However, I just looked again, and yes, it's completely different.

It looks like the main settings you'd need to ensure are correct are in the "Web Site" tab. Make sure website url and possibly base domain are set. If your site is located at www.example.com, you'd want:
URL: www.example.com
Base Domain: example.com

The reason the 'next' error is appearing above is generally when you redirect someone to Facebook to log in, Facebook requires that they be redirected back the application's website. We take care of telling Facebook where to redirect them back to, but if the URL or base domain doesn't match, you'll get that error.

Hope this helps, and we'll get on updating that guide! Thanks for pointing it out.
The topic has been locked.
Active Subscriptions:

None
15 years 8 months ago #5151 by fb_100001544208963
Replied by fb_100001544208963 on topic API errors
I am getting an error :

An error occurred with (my website name ). Please try again later.
API Error Code: 100
API Error Description: Invalid parameter
Error Message: Invalid permission

How to resolve this issue?
The topic has been locked.
Active Subscriptions:

None
15 years 8 months ago #5152 by fb_1023756288
Replied by fb_1023756288 on topic API errors
I am having the same issue and my main settings are correct. I also just got an error logging into your site with the facebook connect. It said that sourcecoast web development is having a problem
The topic has been locked.
Active Subscriptions:

None
15 years 8 months ago #5153 by fb_1023756288
Replied by fb_1023756288 on topic API errors
I am having the same issue and my main settings are correct.

I also just got an error logging into your site with the facebook connect. It said that sourcecoast web development is having a problem. It eventually logs me in just like what is happening on my site right now nightlifecure.com except i get the 100 error on my site.

Here is a screenshot of what I just saw.

Hopefully this is just because of some updates because I am getting the same issue on my phone's browser as well so I know it's not just my computer
File Attachment:
The topic has been locked.
Active Subscriptions:

None
15 years 8 months ago #5156 by sveltosss
Replied by sveltosss on topic API errors
Same issue here.
The topic has been locked.
Support Specialist
15 years 8 months ago #5158 by alzander
Replied by alzander on topic API errors
We're investigating. Not sure if Facebook changed something on there end, is down, or if there's an issue with JFBConnect. We'll keep you posted.
The topic has been locked.
Support Specialist
15 years 8 months ago #5159 by alzander
Replied by alzander on topic API errors
We just released 3.0.2 which fixes this problem. Facebook released a platform update (new javascript and code) last night which slightly tweaked how the login button works.

3.0.2 was planned to be released later today with numerous other minor bug-fixes, so we're still creating the changelog and other information. Please try to install it and let us know if you encounter any issues. This should hopefully be the last 3.0.x release. This will allow us to focus on the 3.1 release with new features.

Thanks for reporting the issue and sorry for the inconvenience.
The topic has been locked.