"Lost password" --> Error

Hello,

I am using the latest version of Joomla and CB.

If a user try to use the function "Forgot Login?" --> "Lost password" then it appears an error page:

0 - Call to a member function get() on string


The user login with username and password is working fine.



Greetings
Joerg

Enable debug mode and maximum error reporting in Joomla global configuration then provide the full error output. Without a filename and line number I've no idea where that error is coming from. If still not showing filename and line number in the error check server error logs for the same error.

Hello,

i activated the full error reporting, but it makes no sense.

Look at the screenshot.



Greetings
Joerg

Check server error log for same error. It should have what file and what line number it occurred in. Seams like it's likely a 3rd party conflict though. Do you have any 3rd party Joomla user plugins installed? If so try unpublishing them.

Hello,

thank you for your advice.

I had a very long chat with my provider.
The server error log was empty!

Then we changed the PHP version from 7.0.18 back to PHP 5.6.30.
Now the function "Lost password" worked without any error, but i don't received an Email with the new password....

Quotation from the chat:

Anastas K.: Thanks for checking it. What I can recommend you in this case will be to contact the developers of the community builder login module and ask them about the issue and what is the recommended PHP version for it. It looks like there is some kind of incompatibility of this module with the PHP version, or simply it is not configured to work correctly. As much as I wish to sort out the issue for you over the live chat, such problems are web development oriented and out of our scope as hosting service providers.

I rechanged the PHP version to 7.0.18.
Therefore i need your help now!


Greetings
Joerg.

We do not recommend PHP 7 at this time. This is due to incompatibilities in 3rd party libraries Guzzle and Imagine that we use. CB it self has no issues with PHP 7 that we are aware of. Without the line number and file for that error we've no way of tracking down the issue as we've no idea where it's coming from.