Topic-icon White page New JFBConnect V4.2

Active Subscriptions:

None
12 years 5 days ago #21779 by guygoo
I got a white page after attempting the update from 4.1 - 4.2 and had to roll back.
I right clicked the white page in the browser and could see the # 1 which I guess is a clue to the problem?
I've made sure there's plenty of php assigned memory.

I'd be grateful to hear from the forum before attempting to install again :)

Cheers!
The topic has been locked.
Active Subscriptions:

None
12 years 5 days ago #21782 by guygoo
I'm a glutton for punishment and couldn't wait to try installing the update again :)

This time around I disabled JFBConnect 4.2.1 before attempting the upgrade to the latest version 4.2 and guess what, it actually worked!
However, the check extension insall is telling me JomSocial - FB Wall 4.1.0 - 4.2.0 This extension is installed and published. The package does not appear to be installing JomSocial - FB Wall 4.2.0. This is suppose to be installed with the main component or am I misunderstanding this? If so where do I locate it?

Thanks in advance!
The topic has been locked.
Support Specialist
12 years 5 days ago #21785 by alzander
Guy,
Very sorry for the delay, especially when you run into critical problems like that.

A white page error, obviously, is a bad thing, but glad to hear you got it going. For this release, you need to have upgraded both JLinked and JFBConnect, since there are some dependencies between the two that need to be up-to-date. If you installed JLinked after your first post, but before JFBConnect again, that's likely what 'fixed' the issue. If you haven't installed the newest JLinked yet, you should.

Regarding the JomSocial FB Wall extension, that's in the main zip file, and it's called 'plg_community_jfbcjsactivity....zip'. Install that, and you should be good to go.

The installation packaging is now the worst part of the JFBConnect experience. We understand that, and it will be our priority to fix with the next big release. Sorry for the inconvenience!

Alex
The topic has been locked.
Active Subscriptions:

None
12 years 5 days ago #21793 by guygoo
Thanks Alex,

I understand it's not always straightforward and these mishaps can happen.
I've managed to fiddle around and install everything and now I'm testing to see it's working OK. Looks good so far :)

Cheers!
The topic has been locked.
Support Specialist
12 years 4 days ago #21801 by alzander
Glad to hear it's going smoothly.. so far :)

Keep us posted if you run into any issues or have any sort of feedback for us.

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

None
12 years 22 hours ago #21978 by hoisau

alzander wrote: A white page error, obviously, is a bad thing, but glad to hear you got it going. For this release, you need to have upgraded both JLinked and JFBConnect, since there are some dependencies between the two that need to be up-to-date. If you installed JLinked after your first post, but before JFBConnect again, that's likely what 'fixed' the issue. If you haven't installed the newest JLinked yet, you should.

The installation packaging is now the worst part of the JFBConnect experience. We understand that, and it will be our priority to fix with the next big release. Sorry for the inconvenience!


So you need to have JLinked if you want to upgrade to JFBConnect 4.2?

When is the next big release that will fix the installation packaging issue?
The topic has been locked.
Support Specialist
12 years 22 hours ago #21980 by alzander
Hoi,
There is no installation packaging issue that we're aware of. Our installation process just isn't as smooth as we'd like it to be (installing multiple files and keeping everything up to date is a hassle). However, the process works.

You do -not- need JLinked installed for JFBConenct to work. However, if you do use both JLinked and JFBConnect, you'll need to be running the latest of both releases (v1.2 of JLinked and v4.2 of JFBConnect), or else there can be issues. JFBConnect v4.2 on it's own is just fine.

Hope that explains,
Alex
The topic has been locked.
Active Subscriptions:

None
11 years 11 months ago #22147 by [email protected]
I'm afraid I am getting the White page when its supposed to redirect to the site. The popup happens, says Facebook is logging me in, which is actually does do, but I have manually hit the root URL to see that it worked. This is a fairly virgin site with very little to screw it up. Its not got a lot of crazy extensions but is running JomSocial.

NOTE TO SELF: WHEN UPGRADING A JOOMLA EXTENSION WITH ALL OF THESE BELLS AND WHISTLES, REMEMBER TO UPLOAD ALL OF THE OTHER PARTS, NOT JUST THE CORE EXTENSIONS.

It's working now. Duh. Hope my idiocy helps somebody else's idiocy. Be sure to update all of the various other bits and pieces and not just stop at the core extension for JFBConnect.
The topic has been locked.
Active Subscriptions:

None
11 years 11 months ago #22148 by guygoo
Another thing that might be worth noting with issues causing white pages is not enough memory allocated for php. Apparently Jomsocial needs a fair amount of memory.
The topic has been locked.
Support Specialist
11 years 11 months ago #22157 by alzander
jw,
Yeah, as mentioned above, our upgrade (and installation) process is due for some improvements to make things a bit more streamlined. Sorry for the troubles, and glad you figured out the problem.

Guy,
You're definitely correct that memory issues are a common cause of white page errors. Even more annoyingly, the error can be thrown in any component.. it's just whenever some extension is executing, if it's the one that asks for that last byte of memory, it's the one that looks broke. JFBConnect has been designed to be very conservative. Pages on SourceCoast.com generally take between 10-14MB to load, including all extensions. JFBConnect generally adds about 2-4MB to page loads.
JomSocial can add between 10-40. That's not to say they are inefficient. Just that on some pages, information about hundreds of users could be loaded, and that needs to be something the server is prepared for.

Anyways, hope all is going well with your sites,
Alex
The topic has been locked.