Problem about Kunena integration

We're looking into this. I'm assuming you're using Kunena 1.5? We tested extensively for 1.6, and left compatibility for the 1.5 version intact. However, just looking at the Kunena Profile Plugin, I can see we missed something.

We'll do some testing and let you know what we find. For now though, please keep it disabled. Sorry for the trouble.

Hey there! Sorry for the delayed response. We just uploaded a new profile plugin zip file, which has an updated Kunena profile plugin in it (v3.2.1). That should fix Kunena 1.5 support for Facebook integration, while keeping 1.6 support intact. Please try it out, and let us know your results.

As for 2 Login positions, it should work in both.. not sure why it isn't working. There's no reason it shouldn't. What method are you using to put the buttons on the site, JFBCLogin modules, {JFBCLogin} tags, or some combination? Let us know, and we'll help you figure out the problem.

Finally, can you let me know more about the IE error? I didn't see it on the page when I went to your forums. Is there anything I should do to make it happen, or just load a page? Also, what version of IE is it occuring in?

Thanks, and good luck!

I'd obviously start testing in IE to see if you can recreate the error. Disabling the things in JFBConnect that may have an impact are the JFBCSystem plugin and JFBCContent plugin. Turning those off basically disables all of Facebook's Javascript APIs. There may be some lingering {JFBCLogin} tags or other things that would appear on the site as placeholders for the Login with Facebook button and whatnot. However, this will let you know pretty quickly if we're the cause.

The error you mention above is much more serious and I think may be the main culprit. The line "MySQL server has gone away " basically means that communication to your MySQL server was disconnected. This can happen for numerous reasons (see below), but when it does, Joomla won't be able to function properly. Anything done until that point will basically be sent to the user's browser, but the remainder of the HTML document won't be generated. This means you'd have an open body tag (where the HTML goes) without a closing one and who knows how many more unclosed items. Browsers handle this to varying degrees, but none of them like it. Everything you describe above seems to indicate that this is what's happening - partial page loads, IE errors, etc

Causes:
* Server memory is running out. How much memory does your site have? You can see this in the Help -> System Info / PHP Information tab. Search for "memory_limit". It should be like 32M, 64M, 128M, etc.
* Some limit on MySQL queries from your hosting provider (unlikely)

Things to check:
* Go to Site -> Global Configuration, System Tab. Turn on "Debug System"
* Hit an offending page (even if it doesn't show the error at that time)
* At the bottom will be a ton of output in red. Mainly, look at the top and see how many queries were executed, how much memory was used, and how much time was taken for each step of rendering the page. Memory needs to be (well) under the number above. Queries should be less than 1000 (general number I pulled out of the air, but much lower is better), and time should be under ~2s. Feel free to paste that block (not all of the queries!) here, and we can help you decipher them.

I'd also recommend contacting your hosting company. Just mention the "MySQL server has gone away" error and ask what's up with that. It shouldn't ever happen. They may be able to help look at error logs and determine the cause.

Finally, why this may have happened around the time of upgrading JFBConnect... the new version does use slightly more memory and other resources. It's possible this 'tipped' your server into a bad area. It's not necessarily a failing of JFBConnect, just that it's the final straw. There are some things we can help to do to reduce these resources (both through settings and code), but then the next extension you install will likely have the same problems.. so that's not the best route. It's also possible that increased users, combined with more extensions since the last uptick in traffic, are the problem (more users equals more memory and database queries).

I really hope this helps get you started on debugging the problem. These things are never fun, and we'll help where we can.

Good luck!