Topic-icon Fatal Error

Active Subscriptions:

None
10 years 4 months ago #43969 by dkerridge
Fatal Error was created by dkerridge
I'm a new user finding their way with JFBconnect and liking it, also using SCLogin - Still some things to be sorted out with latter since only LinkedIn login has worked.

Problem: Updated to Joomla 3.3 and no problem with JFBconnect 6.0.5 (part from above), but have just installed 6.0.6 and site killed with error message "Fatal error: Class 'FRoute' not found in /home/...../...../modules/mod_sclogin/mod_sclogin.php on line 35" the only thing showing on screen apart from website logo. Have gone back to using standard Joomla login module as backup to get things working again. (using PHP version 5.3.21). Help!
The topic has been locked.
Support Specialist
10 years 4 months ago #43975 by alzander
Replied by alzander on topic Fatal Error
If you're seeing an error about FRoute, it means you've set the "Registration Component" to "EasySocial" in the SCLogin module settings. That shouldn't throw an error like that, but obviously, something strange is happening. Can you let me know:
* Are you using EasySocial?
* If so, what version?

For now, if you set "Registration Component" to "Joomla", the error should go away while we figure out the cause of the above.

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

None
10 years 4 months ago #43983 by mh1
Replied by mh1 on topic Fatal Error
Just to chip in here Alex to let you know that I was receiving the exact same error earlier today and as you know, I am using EasySocial.
The topic has been locked.
Support Specialist
10 years 4 months ago #43987 by alzander
Replied by alzander on topic Fatal Error
Can you let me know what version of EasySocial you're using? Again, the Registration Component setting of "Joomla" should fix this issue as well.. though we obviously want to fix the problem for the next release.

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

None
10 years 4 months ago #43995 by mh1
Replied by mh1 on topic Fatal Error
Hi Alex, the latest version: 1.2.10

This version added the ability to specify your own root path folder for photos and avatars, which I took advantage of. Could it be that SCLogin is looking in the old place for avatars?

Instead of: /media/com_easycocial/avatars mine is now /media/social/avatars

From the change log at stackideas.com/changelog/easysocial:

Added settings to configure avatars storage path.

Added storage path settings for photos.

The topic has been locked.
Active Subscriptions:

None
10 years 3 months ago #44347 by dkerridge
Replied by dkerridge on topic Fatal Error
Sorry, Alex,

Have been away from this for a while. Just checked your reply. I actually re-installed everything, tried again and the problem just went away, I'm sorry but can't explain it to help chase bugs and don't want to duplicate it!

I am using Easy Social (v 1.2.14) in JFBConnect registration field.

BTW, have been able to make registration work for a few as test case, but not on my own logins to test what happens with Facebook, Google and LinkedIn login. Got message that I was log gin in with Facebook, then taken to registration page (easy social), filled in fields, hit continue and just brought straight back to same page with nothing else happening. Came here, checked forum - Just changed over to JFBConnect Registration Component and now auto login using Facebook button is working as well.

Thanks for help, sorry for late reply.

David
The topic has been locked.
Support Specialist
10 years 3 months ago #44358 by alzander
Replied by alzander on topic Fatal Error
David,
I'm glad to hear things seem to be working for you now. I'm not sure why the links were causing a fatal error before and aren't now. In the next SCLogin release, we have an update to our code which should prevent the fatal errors in all cases (if you want/need that change now, just let me know).

As for the registration using the EasySocial component, that *should* work as well, of course. We do a lot of testing with that registration flow to make sure that social logins can work while using the registration path of other extensions. If you register normally through EasySocial, I'm assuming you're not running into those problems... it's only when you do the social registration with JFBConnect?

Either way, if you're satisfied with using the JFBConnect registration flow, that's great. If you need more help, just let me know and we'll do what we can.

mh1,
Sorry for not getting back to your question earlier. The changes you mention shouldn't have been causing the problem. We use EasySocial's API to fetch the user's avatar, and those calls were updated with their latest release to respect their own configuration values.

If you are still having the fatal error and want the fix that we're implementing in the next release of SCLogin that should fix it, please let me know. We'll gladly post it. It's very simple.

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

None
10 years 3 months ago #44456 by dkerridge
Replied by dkerridge on topic Fatal Error
Alex,

Thanks. Using JFBConnect registration with no problems. When I get back to it I might try Easysocial registration again to keep everything synced. For now, will wait for new version.

Thanks again for help.

David
The topic has been locked.
Support Specialist
10 years 3 months ago #44473 by alzander
Replied by alzander on topic Fatal Error
David,
Great to hear things are working for you. Of course, if you run into other issues or have any questions, just let me know!

Thanks,
Alex
The topic has been locked.