after upgrade to 2.0 on a J3.3.3 when accessing the reg form in the front end:
Fatal error: Cannot access protected property CB\Database\Table\FieldTable::$_db in components\com_comprofiler\plugin\user\plug_cbpasswordstrength\cbpasswordstrength.php on line 20
Warning: array_keys() expects parameter 1 to be array, null given in libraries\CBLib\CB\Legacy\cbPluginHandler.php on line 1057
Warning: Invalid argument supplied for foreach() in libraries\CBLib\CB\Legacy\cbPluginHandler.php on line 1057
I know, these last two are just warnings but still should be addressed I'd say. They are still anoying during development when you have error reporting switched on.
carin wrote: after upgrade to 2.0 on a J3.3.3 when accessing the reg form in the front end:
Fatal error: Cannot access protected property CB\Database\Table\FieldTable::$_db in components\com_comprofiler\plugin\user\plug_cbpasswordstrength\cbpasswordstrength.php on line 20
Warning: array_keys() expects parameter 1 to be array, null given in libraries\CBLib\CB\Legacy\cbPluginHandler.php on line 1057
Warning: Invalid argument supplied for foreach() in libraries\CBLib\CB\Legacy\cbPluginHandler.php on line 1057
I know, these last two are just warnings but still should be addressed I'd say. They are still anoying during development when you have error reporting switched on.
cheers
Ha - I had also seen this during my upgrade tests and reported it to but neglected to open a tracker item so it fell through - thanks for reporting here.
Quick solution is to unpublish the password strength plugin you had installed on the CB 191 site you upgraded from.
You should be able to do this from your CB 2.0 RC CB plugin Manager area.
This specific functionality has been built-in now in CB 2.0 core.
Althoufh I did that already I never got my site back to work so I had to revert to 1.9.1. 80% of the plugins were disabled or had an exclamation mark which no one knows it means. I only hope when the stable 2.0 comes out next year it can upgrade properly.
nant