Topic-icon App Temporarily Unavailable, Runtime errors

Active Subscriptions:

None
14 years 5 months ago #17825 by stewan
Hello,
Due to unknown availability of mod_jfbclogin and mod_jfbcinvite in JFBConnect Extension Check, I looked up how these two modules appeared on web page.
File Attachment:

It came up with the following error message.
'App Temporarily Unavailable
Runtime errors:
serverfbml 'action' attribute must be within the application's connect url'

How can I fix it?

Stephen Wang
File Attachment:
The topic has been locked.
Support Specialist
14 years 5 months ago #17834 by alzander
Stephen,
Thanks for pointing out the unknown availability thing. We updated the versions so your Overview area should show the correct last version of JFBCLogin and JFBCInvite. Sorry about the confusion there. The reason it was removed is because in the 4.1.0 release of JFBConnect, both of those modules have been replaced:
SCLogin - Replaces JFBCLogin and is a unified login module for JFBConnect and JLinked.
JFBCRequest - Replaces JFBCInvite. Uses the new Requests features of Facebook, and is vastly improved over the old Invite module.( See Demo )

I'm not sure why the JFBCInvite module was throwing that error. Is that on one of our sites, or on yours? If you need help fixing it, we still do support that module, so just let us know.

For more information on the 4.1 release, especially regarding the new Requests stuff, see:
JFBConnect v4.1 Announcement Blog Post
JFBConnect v4.1 Changelog

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

None
14 years 4 months ago #17867 by stewan
Hi, Alex:
The error message of JFBCInvite is from my site www.ustart.biz/. Is that causing by lacking of SSL of my site for Facebook canvas? Please take a look of my early Beta site and advise.

Thanks

Stephen
The topic has been locked.
Support Specialist
14 years 4 months ago #17871 by alzander
Stephen,
The reason you're seeing that error is because you haven't updated the parameters for the JFBCInvite module. The 2 URLs that are specified in the parameters must be for pages on your site.. currently, they're set to www.yoursite.com/. Update those to be www.ustart.biz/ and that should fix the issue.

That error is due to a basic check by Facebook to make sure you don't send the user to a malicious page on accepting an invite or after sending them.

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

None
14 years 4 months ago #17931 by stewan
Hello, Alex:
It does work! No more error message appeared. Thanks for the advise.

Stephen
The topic has been locked.
Support Specialist
14 years 4 months ago #17934 by alzander
Fantastic! Glad to hear that got it going for you. I would still recommend installing and playing with JFBConnect 4.1 with it's new requests feature. The invite module is likely to stop functioning on June 30th this year, per some upcoming changes that Facebook has announced. Until then, it should work just fine though.

Good luck,
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 4 months ago #17960 by stewan
Hi, Alex:
I got it upgraded to JFBConnect 4.1 including SCLogin. It runs perfectly smooth. Thanks for reminding.

Stephen
The topic has been locked.
Support Specialist
14 years 4 months ago #17963 by alzander
Stephen,
Glad to hear it. Not sure exactly when you upgraded, but we just released v4.1.1 of JFBConnect last night. It has some minor bug-fixes from 4.1.0, but if you're not having issues, it's not required to move to it.

Anyways, best of luck, and should you need anything else, just let us know!

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

None
14 years 4 months ago #17998 by stewan
Hello, Alex:
I got the latest version up and running. JFBConnect Extension Check showed installed version with everything 4.1.1 and SCLogin with v1.0.2. Now I may work on the web site content. Thanks for the great support.

Have a nice weekend!

Stephen
The topic has been locked.
Support Specialist
14 years 4 months ago #18000 by alzander
Awesome. You have a great weekend too!

Alex
The topic has been locked.