Error - Joomla\Registry\Registry::loadArray(): Argument #1 ($array) must be of t

Thanks for the credentials, they really helped us dig in quickly.

The issue you're having isn't related to JFBConnect. The problem is actually with the Sendy - User plugin. I'm unsure why it's throwing that message, but when I disable the Sendy plugin, the error goes away.

We have not done any testing with Sendy on Joomla 4, though we don't think there should be any issues with it. I would recommend checking your API keys and Sendy installation to make sure there's not a simple configuration error between the 2 that is causing the issue.

Please test with the Sendy plugin disabled to verify the issue goes away and let us know if you're able to narrow anything down further with Sendy itself. We're planning to verify our Sendy integration with Joomla 4 over the coming weeks as well.

Thanks,
Alex

Thanks for letting us know your status. Yes, the changes above will be in the next release of JFBConnect, so you won't have to re-implement them.

We're investigating the changes for Sendy now as well and will keep you posted.

Thanks,
Alex

We made some updates to Sendy to improve compatibility with Joomla 4. I don't think any were required as Joomla 4 has backward compatibility with most of the changes we made.

We installed the newest version on your site and still received the same HTTP SSL error when trying to activate a user. Then, we changed the URL to our Sendy installation and updated the API key and list ID temporarily. When registering using our list, we did not see the error.

That leads me to believe there's some sort of server configuration issue with Sendy or Joomla making the HTTPS calls. I'm not sure if we are able to fix this on our end as I don't think it's a code issue with our plugin.

I hope the above helps give some pointers on where to look, but sorry I don't have a specific answer for you.

Thanks,
Alex

Brian,
The code-fix we provided above is *not* included in the latest release. It's not something we'd set permanently for everyone, but we could add an option to enable a 'fallback mode' for it to help fix your site and any others that may run into the same problem.

However, the "Application Not Configured" message makes me think the above code-change isn't the problem. If you're getting that message, communication with Google seems to be working, but something in the Google app is probably not setup right.

Here's my suggested path forward:
* Implement the code change above and see if that fixes things. If so, let us know and we can add that option to the next release. That should fix you up going forward.
* If not, leave the code change in place and double-check your Google Application settings. If everything looks right, try creating one more Google App following our Google App Setup Guide step by step.
** If the 'new' key works, that indicates there is an issue with some setting in your original app. Find it and fix it.
** If the 'new' app still fails (ideally in the same way), let us know and we can FTP into your site to add more debug code and narrow down what else may be happening.

Thanks,
Alex

To follow up on that, some of the changes were made but 1 code change was not (as Alex mentioned). It's below so you don't have to guess which one to re-add.

Please edit the following file:
/components/com_jfbconnect/libraries/joomla/http/transport/curl.php
Around line 44, you'll see:

After that line, add the following: