I have Jomsocial and PayPlans and everytime I log using my social media account, the next page is blank and the account is not directed to the next subscription page.
Can you explain again how do integrate JFBConnect and SCLogin witth Jomsocial and PayPlans in detail please.
I have configured as per this document (http://www.readybytes.net/payplans/docu … nect.html) but the same problems are coming up.
When I use any of the social media icons, it gets redirected to a blank page.
I see that the last time you ran Autotune, it was for 6.0.3, which was released a year and a half ago. That version is extremely outdated and will actually no longer work for some social networks such as Facebook anymore, as their API's are constantly changing. I'm not surprised there are issues.
Generally a blank page indicates a PHP error. Please turn on Error Reporting in the Joomla Global Configuration and let us know what the error is. If it's something obvious, that can help narrow down the problem. However, as I mentioned a very old version is likely to have other issues, even if we help you to get through this one.
Thank you for your response.
Here is the error reading that i am getting:
Strict Standards: Declaration of JFBConnectProfileDataProxy::bindData() should be compatible with Joomla\Registry\Registry::bindData($parent, $data, $recursive = true, $allowNull = true) in (root)/components/com_jfbconnect/libraries/profile.php on line 119 Warning: Cannot modify header information - headers already sent by (output started at (root)/components/com_jfbconnect/libraries/profile.php:119) in (root)/components/com_jfbconnect/controllers/login.php on line 33 Warning: Invalid argument supplied for foreach() in (root)/components/com_xipt/models/profiletypes.php on line 73 Deprecated: Non-static method XiptHelperUtils::getInfo() should not be called statically, assuming $this from incompatible context in (root)/plugins/community/xipt_community/xipt_community.php on line 270
That error is because you are using a very old version of JFBConnect that was built for a much earlier version of Joomla. The issue above was fixed when Joomla 3.2 was released. You can try the workaround posted here which may fix that issue, but I'm sure you'll run into others as Melissa posted above.