Welcome the Technical Support section. Help us in assisting you by providing us with a concise and descriptive elaboration of your issues. Be specific and if possible, provide us with a step-by-step instruction in replicating your problem.
'Fatal error: Call to a member function' message & failed registration
ISSUE SUMMARY: We have had some new users complain that they can't register, as they are getting this message:
Fatal error: Call to a member function get() on a non-object in XXXXXXXXXXX/components/com_community/controllers/register.php on line 809
I have now found that many people have reported this on the Jomsocial forum over the last year, but the responses from support seem to be different. Please could you tell us what the issue is and what is the solution? We have not changed anything on our website recently, and we have had lots of users register in recent months. We are still running 4.0.9, as we are currently testing 4.1.4 on our dev site (and we need to upgrade that to 4.1.6 too).
This issue really complicated, this issue can be caused by :
- 3rd party plugin user
- 3rd party component like JSPT
- 3rd party cache
- session issue
- cache issue
So you need investigate it carefully, and make sure you dont have any 3rd party when test this.
Multiple users have been reporting this problem for many months, who will all have different third party plugins.
Maybe I am wrong, but why would there be a session issue or cache issue when someone first comes to our website to register? They have probably never visited before.
We do not think we have any Third Party plugins that would be affecting the registration page.
Also, why would a 3rd party plugin affect only that registration page and not other pages on our site?
I think Jomsocial needs to investigate this problem more deeply, as a lot of people have reported it.
Please can you have a look and see if you see what the problem has been?
anyway, have you set the session handler to none and set the session lifetime to the bigger value?
And the most of this issue actually caused by 3rd party, some of 3rd party use the session token during the registration.
long time ago we set this issue as a bug, and there is a solution for this
www.jomsocial.com/forum/installation/258...n-popup-again#128527
most of customers report this issue months ago, and until now we never faced the same issue anymore, especially which the issue no-one caused by our code :)