Topic-icon Upgrade SC Login and everything breaks...

Active Subscriptions:

None
9 years 8 months ago #45906 by miamiman
Admin logout error:
Fatal error: require(): Cannot redeclare class jfbcfactory in .../plugins/user/jfbconnectuser/jfbconnectuser.php on line 61

Front-end:
Double google authentication image (after downgrading SC Login to previous version) because 4.1.1 broke in back end.

File Attachment:


Front-end:
Invalid token upon login

Front-end:
Hangs attempting to log-out after successfully logging-in.

Any ideas?
The topic has been locked.
Support Specialist
9 years 8 months ago #45915 by alzander

Admin logout error:
Fatal error: require(): Cannot redeclare class jfbcfactory in .../plugins/user/jfbconnectuser/jfbconnectuser.php on line 61

That's not an issue we've heard of before. From looking at the code, it looks like the code that's throwing the error shouldn't be causing any problems, but also can be removed without any issues either. To remove, please edit the /plugins/user/jfbconnectuser/jfbconnectuser.php file. Around line 59, you'll see:
// Tell Facebook to delete session information stored for this user.
        $factoryFile = JPATH_ROOT . '/components/com_jfbconnect/libraries/factory.php';
        require_once($factoryFile);
Remove those lines and try again. Please let us know how that goes.

Front-end:
Double google authentication image (after downgrading SC Login to previous version) because 4.1.1 broke in back end.

SCLogin v4.0 is not meant to be used with JFBConnect v6.1. There is a completely new login button system with the 6.1 release that the older SCLogin module won't recognize. The new version allows for selecting the button image for each social network.

Front-end:
Invalid token upon login

Please try going to the Advanced Parameters area and disabling the Caching option.

Front-end:
Hangs attempting to log-out after successfully logging-in.

Are you clicking the "Logout" button, or is the attempt to logout not intentional? My guess is that it has to do with the require issue you mentino above.
The topic has been locked.
Active Subscriptions:

None
9 years 8 months ago - 9 years 8 months ago #45928 by miamiman
RESOLVED -

That's not an issue we've heard of before. From looking at the code, it looks like the code that's throwing the error shouldn't be causing any problems, but also can be removed without any issues either. To remove, please edit the /plugins/user/jfbconnectuser/jfbconnectuser.php file. Around line 59, you'll see:


UNRESOLVED 1 - Upgraded module (again) to SC Login 4.1.1 and it breaks the back-end per previous thread. Tried (again) changing the three bits of code without success.

Fatal error: Call to undefined method JFormFieldList::renderField() in .../modules/mod_sclogin/fields/jfbconnectsettings.php on line 49

UNRESOLVED 2 - I confirm that INVALID TOKEN is only for the joomla registration log-in from the SC Module (4.1.1) with the upgrade JFBConnect 6.1. Facebook login works correctly. Normal Joomla log-in module works correctly.

Any idea? Somewhat urgent.
Last edit: 9 years 8 months ago by miamiman.
The topic has been locked.
Support Specialist
9 years 8 months ago #45935 by alzander

UNRESOVLED 1 - Upgraded module (again) to SC Login 4.1.1 and it breaks the back-end per previous thread. Tried (again) changing the three bits of code without success.

We just did further testing to narrow things down. Although the Joomla documentation says that the renderField call is available "since 3.2", it's actually only available in 3.2.4 (or 3.3.0) and higher.

We installed 3.2.3 and tested updating the jfbconnectsettings.php file with the line of code below, and it worked:
if (version_compare(JVERSION, '3.2.3', '<='))
That change was made in the 3 spots. To be even more sure, you can simply replace the whole block with the following:
foreach ($form->getFieldsets() as $fiedsets => $fieldset)
            {
                $html[] = '<ul class="adminformlist">';
                foreach ($form->getFieldset($fieldset->name) as $field)
                {
                        $label = $field->getLabel();
                        $input = $field->getInput();
                        $html[] = '<li>' . $label . $input . '</li>';
                }
                $html[] = '</ul>';
            }
We added a bug to our tracker to update the code in the next release to fix the problem. The issue only occurs with Joomla 3.2.0-3.2.3. All other versions, including the newer 3.2.4 and all 3.3.x releases, are not affected. As always, we recommend using the latest release of Joomla for various reasons.

UNRESOVLED 2 - INVALID TOKEN is only for the joomla registration log-in from the SC Module after upgrading to 6.1. Facebook login works correctly.

Have you gone into the Advanced settings of the SCLogin module and disabled the caching option? If so, and you still have issues, can you try disabling the Joomla -> Global Configuration caching option and see if that fixes the problem? That's not meant to be a permanent solution, but will help narrow down the cause.

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

None
9 years 8 months ago #45963 by miamiman
Thank you Alex.

Both issues are resolved and both facebook and joomla log-in are working as expected.

Regards!
The topic has been locked.
Support Specialist
9 years 8 months ago #45981 by alzander
Fantastic. I'm assuming the code-change and the caching setting are what you needed to fix things? Just like to know so we have that info for the future.

Thanks,
Alex
The topic has been locked.