I’ve got a considerable number of players complaining they can’t login using the plugin. They say the click the “Unlock with Patreon”, then “Allow” and then return to the post without unlocking it (stuck in loop).
I can reproduce the issue since it works correctly on my testing account; however, I enabled WP debug some days ago to see if I could catch something and I noticed some errors there related to the plugin:
Versions of my plugins:
Patreon Wordpress: 3.0.2
Patron Plugin Pro by CodeBard: 1.0.9
Patreon Button, Widgets and Plugin by CodeBard: 2.0.4
Ubuntu 14 LTS
PHP: PHP 5.5.9-1ubuntu4.25 (cli)
Does anyone know something about this? Any tip will be highly appreciated.
Undefined var notice shouldnt have any effect.
Please first update your Patron Pro to the latest version, and make sure that your access credentials at Patreon API are correct and no token is listed as expired. All tokens must be fresh (none expired) and they must match what you put into the settings in your plugin admin at your WP site.
Hey, thanks for your reply. Isn’t 1.0.9 the latest version for Patron Pro? I didn’t get any update warning. About the tokens: we did check them and they’re fine.
1.1.0, 1.1.1 were out since a long while. 1.1.2 went out just today.
Also update your patreon wordpress version.
Oh, now the warning do appear:
A new version of Patron Plugin Pro is available! Please update your plugin to benefit from security fixes, bug fixes and new features. To update your plugin, click here.
However, the link is broken and show me “The link you followed has expired.”. It seems like I’ll need to update them manually…
Okay, plug-ins updated to the latest version. I just checked my debug log and still see an error:
[02-Jul-2018 19:54:28 UTC] PHP Notice: Undefined variable: check_user_email in /var/www/html/play/wp-content/plugins/patreon-wordpress/classes/patreon_login.php on line 178
IDN if this might or not be a problem.
Other message that has been appearing in the log:
[03-Jul-2018 03:30:37 UTC] PHP Warning: array_key_exists() expects parameter 2 to be array, null given in /var/www/html/play/wp-content/plugins/patreon-wordpress/classes/patreon_routing.php on line 247
Am I still have some users complaining about the “loop” in the log-in. All plugins are up to date, cache was flushed and Patreon client was refreshed just in case (it wasn’t expired). I’m clueless of what to do.
This seems to necessitate an on-site look.
Please arrange me an admin user/pass at your WP site, and FTP access if possible - and mail me at email@example.com
Also please let me know if we can do live code changes and tests at your site.
I sent the requested information. Thanks.
Same problem here:
Warning: array_key_exists() expects parameter 2 to be array, null given in /home2/ekhnaton/hornstown.com/2/wp-content/plugins/patreon-connect/classes/patreon_routing.php on line 247
Please let me know if you have any solutions Thx.
Notices and warnings should not be on at a production site. Please try turning them off and then checking out if the issue persists.
I am having a similar issue: I can login using my personal Patreon account, but when I try to use our creator account, I get the loop that Ricky described – just takes me back to the login screen.
Patreon Wordpress plugin is updated to version 1.1.2.
I’m not running the Patron Plugin Pro or Patreon Button, Widgets & Plugin.
In the current state, the plugin should not unlock content for creator accounts since a creator cant be a patron of himself/herself. So, it doesnt unlock content for creator accounts unless the account is linked to a WP admin account.
It seems it will be good if we added a message or just make the plugin unlock the content if someone is logged in as the creator, but not as a site admin.
Okay, so this is expected behavior at this point. I appreciate the information! I do agree it would be better if the plugin unlocked the content, or at least offered an informational message.
To all participating in this thread:
Please delete the existing Patreon WordPress on your site (deactivate first), then upload and activate the below package with oauth error reporting and see if it sheds any light on this issue by showing an error:
All who participated in this thread: API’s cloudflare settings were just readjusted by Patreon. Please check it out and see if you can reproduce the cloudflare-block.
To all participants of the thread: There were changes made at CloudFlare to address this issue just today.
Please try to reproduce the issue and let us know if it occurs, or if you are not able to reproduce it at all. Any input is appreciated.