× Joomla Facebook Connect support forum

Topic-icon Problems after updating to 4.01

Active Subscriptions:

None
12 years 7 months ago #13386 by getimo
I have problems after updating to jfbconnect 4.01.

- The login doesn't work anymore (deleting cookies, restarting bowser etc. didn't help). The fb popup opens and nothing happens. Closing the popup doesn't do anything.
- The performance of the like button in K2 got slower
- Since you're using now the correct SEF-Links for likes (fb) all likes of articles before the update are gone (I know that there's no better solution). Maybe you could use the original Joomla url for the likes and transcribe them later to the SEF...sorry, don't know too much about that.

Question:

- How can I downgrade to 4.0? (urgent)

Suggestions:

- Let us choose the social buttons which should be displayed - not all at once
- Please provide a changelog of altered files.
- Inform us about updates per Mail or RSS (maybe I didn't find it yet) :)
- After every update the translation files are overwritten - the user should be informed of that procedure.

Thank you in advance for the good support! I think improving the user experience would make your product even better.

getimo
The topic has been locked.
Support Specialist
12 years 7 months ago #13391 by alzander
Getimo,
The changes in 4.0.1 shouldn't have affected registration or login at all. Almost all changes were in the JFBCContent plugin (/plugins/content/jfbccontent.php).

As for the problems you're seeing, there's nothing I can see that should be causing the login problems. When I click the button, I'm successfully redirected to the component/jfbconnect/?view=loginregister page as expected. I didn't register an account, but I gladly can if you'd like. This was with Chrome on Windows. Can you try a different browser, or let us know what actually is happening when you try to log in? Pop up doesn't go away, doesn't show the login form, etc.

For K2 Like's going slower, that seems to be a Facebook issue right now. We're noticing them a little slower on a lot of sites (not necessarily JFBConnect, or even Joomla ones).

Yes, the switch to the K2 URLs isn't nice, but as you said, there isn't much of a better way. The reason we use the SEF URL is because that should be the best/final URL. If we use the original, non-SEF Joomla one, that can change a lot depending on ordering of parameters (which we can fix), as well as it may include an Itemid and other things that we can't correct for. Due to the recent release of 3.4 which had our initial K2 support less than a month ago, we made the decision to just fix the problem instead of implementing some weird work around that would work forward and back. It is unfortunate, and we apologize for the inconvenience.

For the suggestions:
* We agree with the selection of social buttons. That will be in a future release. If you want to always have one removed, we can point you to the line(s) of code to alter to do that (pretty easy).
* Changelog of altered files is difficult. This probably won't be done going forward as it's never been a common problem with bugs we have (and we're proactive about fixing what is found).
* A newsletter announcement for the 4.0 release is going out tomorrow. We always announce the minor (x.y) releases, but not always the bug-fix versions, as usually those fixes don't affect all users. We don't like going overboard with emails as any of our plugins, modules, or the main component does have updates regularly... it would get annoying fast :D

Finally, one thing I did notice was that on the Login/Register page, the welcome text is instead "COM_JFBCONNECT_THANKS_FOR_SIGNING_IN". You may want to check your com_jfbconnect.ini language file for that string. We'll also check to make sure it's in the German version we distribute.

Keep us posted on anything you find,
Alex
The topic has been locked.
Active Subscriptions:

None
12 years 7 months ago #13394 by getimo
Thank you Alex for the super rocket fast response!

I can confirm that the login does work with Firefox - not in Chrome (both Mac). Yesterday it worked. Now after the update it doesn't work anymore!? -> The popup of fb does open with a blank page (if already logged in into facebook). If I'm logged out from facebook and try to login on my site the login credentials can be entered but after clicking login the popup gets white and nothing happens. After closing the popup I noticed that chrome builds a connection to facebook which stops after a few seconds.

Regarding the German translattion: In Germany we have two ways of translations (format/informal). Maybe this could be extended by using two different language files. Since there's not much to translate I can provide you a (correct) translation. Some translation strings are...hmmm strange ;)

getimo
The topic has been locked.
Support Specialist
12 years 7 months ago #13398 by alzander
No problem for the help.. you know it's what we do :)

There really shouldn't be any reason that 4.0.1 functions any differently than 4.0.0. The changes simply weren't with that functionality. We had another user recently have a different issue with Chrome where the button wasn't showing at all. We recommended a few things, but deleting his history (not just cookies) was somehow the solution. For the full thread, including other suggestions we have which are good to test as well, can be found below:
www.sourcecoast.com/forums/jfbconnect/jf...ct-button?p=1#p13241

As for the German translation. The initial translation was provided by a user, but there have been times (new strings) where we've had to rely on Google Translate. If you want to post or email us better translations, we'd love to include them in the next release.

Hope the above helps, but if now, you know where we are.

Alex
The topic has been locked.
Active Subscriptions:

None
12 years 7 months ago #13416 by getimo
Thank you, the link helped me. I'll send you the translations in a few days - I have to change them because I customized them for my page.

getimo
The topic has been locked.
Support Specialist
12 years 7 months ago #13420 by alzander
It sounds like you got it to work in Chrome, which is fantastic. This is, unfortunately, a teething issue with the updated authentication logic we have in 4.0, but necessary overall.

If you run into any other issues, just let us know, and we'd love the translation whenever you can get it to us. We don't have any new releases planned for a bit, but will get it into the next one whenever that is.

Thanks,
Alex
The topic has been locked.