SC login breaks down in the backend on 4.1.1

Hmmm.. Looking at our code, we do a check to see what version of Joomla you're using in the block of code that is throwing that error. Currently, we look to see if Joomla 3.2.0 or higher is being used. If so, we do it the way that's failing for you. If it's lower, we do it an older way.

With a little research, it seems like the code works with Joomla 3.2.3 and higher, but not will likely fail with 3.2.0-3.2.2. I'm assuming you're on one of those versions.

If so, I'd first recommend upgrading Joomla. There's a few security and general bug-fixes in the 3.2.3/3.2.4 releases (or 3.3.0+ versions).

If that doesn't work, you can edit the file you mentioned. Around lines 38-51, you'll see 3 lines that look like:Update that to:That should correct the check for the proper versions.

I hope that helps, but if you have any other questions, just let me know.

Thanks,
Alex

The new JFBConnect has a much easier system to use your own custom images that work with the SCLogin module, the {JFBCLogin} tag and any other places where the buttons are inserted automatically.

To use, please copy your custom images to:
/media/sourcecoast/images/provider/facebook/ (or any other social network)

Then, in the JFBConnect -> Configuration area, you'll be able to select your new images as the default. In the SCLogin module, you can also use the Provider Images option and set a specific image for each provider. This allows you to use big images for more important networks, and smaller images for networks that aren't used as often, but you still want to make available.

I hope that helps,
Alex

We'll have to investigate the admin logout issue. That's the first we've heard of that problem.

As for the SCLogin issue, if you want to try the code change above, you should modify it to be <= (less than or equal) or change the version number to 3.2.4 like:That will make sure the older style method is used, which should definitely work. We'll have to double-check what version the renderField function was added, but my understanding was that it was definitely available in 3.2.3. I'm not sure why that error would be showing for you, in that case, though.

If you decide to upgrade again, please let us know how the above goes.

Thanks,
Alex

Glad to hear the new feature works for you. We're very happy about the new login button options and all the other features in the 6.1 release, as well as the great new things we're panning for later this year.

As always, if you need anything else, just let us know.

Thanks,
Alex