# Was some significant V1 change recently implemented? **URL:** \ **Category:** Wordpress Plugin\ **Created:** [January 14, 2020, 4:33pm UTC](https://www.patreondevelopers.com/t/was-some-significant-v1-change-recently-implemented/2614 "2020-01-14T16:33:15Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![umhoops](https://avatars.discourse-cdn.com/v4/letter/u/e9bcb4/32.png) [@umhoops](https://www.patreondevelopers.com/u/umhoops)\ **Post date:** [January 14, 2020, 4:33pm UTC](https://www.patreondevelopers.com/t/was-some-significant-v1-change-recently-implemented/2614/1 "2020-01-14T16:33:15Z")
I’ve been using an older version of the WP Plugin to log users in and for some reason now when logging in with Patreon my site is just creating a blank account with no email address and a short six character string. It is not tied to their email address or anything. Has the OAuth flow been changed somehow? ---
**Author:** ![umhoops](https://avatars.discourse-cdn.com/v4/letter/u/e9bcb4/32.png) [@umhoops](https://www.patreondevelopers.com/u/umhoops)\ **Post date:** [January 14, 2020, 4:50pm UTC](https://www.patreondevelopers.com/t/was-some-significant-v1-change-recently-implemented/2614/2 "2020-01-14T16:50:29Z")
Seems like this is the error: 2020/01/14 16:47:33 [error] 130355#130355: _11036872 FastCGI sent in stderr: “PHP message: PHP Warning: array\_key\_exists() expects parameter 2 to be array, null given in /www/\*\*\*\*\*\*\*\*\*\*\*\*\*\*/public/wp-content/plugins/patreon-wordpress/classes/patreon\_routing.php on line 103” while reading response header from upstream, client: \*\*\*\*\*, server: \*\*\*\*\*\*\*\*.com, request: “GET /patreon-authorization/?code=nwi79KeMFSAbbEzHLR6G7o98cThu76&state=8d00a29ac1e321c22178d63d9721f0d7 HTTP/1.0”, upstream: "fastcgi://unix:/var/run/php7.3-fpm-__ **.sock:", host: "** _\*.com", referrer: “[https://www.patreon.com/](https://www.patreon.com/)” ---
**Author:** ![codebard](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/codebard/32/14_2.png) [@codebard](https://www.patreondevelopers.com/u/codebard)\ **Post date:** [January 14, 2020, 6:51pm UTC](https://www.patreondevelopers.com/t/was-some-significant-v1-change-recently-implemented/2614/3 "2020-01-14T18:51:09Z")
Older version of the WP plugin will likely not work depending on how old the plugin is. Updating the plugin to the latest at WP repo would fix your problems. If you have 3rd party modifications relying on the old version of the plugin, you may need to update them to work with the latest one. ---
**Author:** ![umhoops](https://avatars.discourse-cdn.com/v4/letter/u/e9bcb4/32.png) [@umhoops](https://www.patreondevelopers.com/u/umhoops)\ **Post date:** [January 14, 2020, 6:55pm UTC](https://www.patreondevelopers.com/t/was-some-significant-v1-change-recently-implemented/2614/4 "2020-01-14T18:55:51Z")
FWIW for others having an issue. This appears to be caused my User Agent blocking on the Patreon API. Added this line to patreon\_oauth.php and at least users are logged in properly now. ``` curl_setopt($curl, CURLOPT_USERAGENT, "your user agent here"); ``` Confirmed here that this change was put in yesterday. @Jackie_Bow also confirmed that my IP had been being blocked. > [@Cloudflare IM NOT A ROBOT blocking API?!?](https://www.patreondevelopers.com/t/cloudflare-im-not-a-robot-blocking-api/2607/7): > > Hello All! I’m Jackie, Security Lead here at Patreon. Yesterday, we moved to challenge (serve Captcha) to requests that do not include a user agent. This is because historically, there have been a large number of badware or malware that omits user agents. Adding a proper user agent will circumvent this. We also serve captcha to suspected bad automated traffic. If you believe your legitimate app is being served captcha, we can work with you - feel free to privately message me here, and I’ll get b… ---
**Author:** ![codebard](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/codebard/32/14_2.png) [@codebard](https://www.patreondevelopers.com/u/codebard)\ **Post date:** [January 14, 2020, 7:02pm UTC](https://www.patreondevelopers.com/t/was-some-significant-v1-change-recently-implemented/2614/5 "2020-01-14T19:02:48Z")
Yes, that could cause problems - user agent was added to latest version of WP plugin a long time ago. Can you just update the plugin to latest? > **[Patreon WordPress](https://wordpress.org/plugins/patreon-connect/)** > > Connect your WordPress site and your Patreon to increase your patrons and pledges! > > With Patreon WordPress, you can bring Patreon features to your Wor … This would not only fix that problem and many potential ones, but also add new features. If you are unable to upgrade due to various modifications, just let me know and ill think of something to help you make the move. ---
**Author:** ![umhoops](https://avatars.discourse-cdn.com/v4/letter/u/e9bcb4/32.png) [@umhoops](https://www.patreondevelopers.com/u/umhoops)\ **Post date:** [January 14, 2020, 7:04pm UTC](https://www.patreondevelopers.com/t/was-some-significant-v1-change-recently-implemented/2614/6 "2020-01-14T19:04:03Z")
The issue I have with upgrading is that I’m using the original Patreon Connect: Patron Memberships plugin that syncs everything up with my Paid Memberships Pro status. ---
**Author:** ![codebard](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/codebard/32/14_2.png) [@codebard](https://www.patreondevelopers.com/u/codebard)\ **Post date:** [January 14, 2020, 7:13pm UTC](https://www.patreondevelopers.com/t/was-some-significant-v1-change-recently-implemented/2614/7 "2020-01-14T19:13:45Z")
Ah i see. Then you cant upgrade right away to latest version. Now, we are slowly adding compatibility with other plugins (including membership ones) to Patreon WordPress. Paid Memberships Pro compatibility is definitely going to happen in near future. If you keep following the plugin, you may upgrade to latest version easily in future. ---
**Author:** ![codebard](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/codebard/32/14_2.png) [@codebard](https://www.patreondevelopers.com/u/codebard)\ **Post date:** [May 15, 2020, 6:57pm UTC](https://www.patreondevelopers.com/t/was-some-significant-v1-change-recently-implemented/2614/8 "2020-05-15T18:57:35Z")
Im updating this thread to let you know that PW now has PMP compatibility. > [@Patreon WordPress is now compatible with Paid Memberships Pro](https://www.patreondevelopers.com/t/patreon-wordpress-is-now-compatible-with-paid-memberships-pro/2823): > > With version 1.5.0, Patreon WordPress is now compatible with Paid Memberships Pro. If you had PMP pro before, you can just install Patreon WordPress and have your patrons easily unlock content gated with PMP without needing to do anything else. It will just work out of the box. It also works the other way - PW gated content can be unlocked by a qualifying member from matching PMP tier assigned to any post/content. You can also gate posts/content with both plugins at the same time, and any user…