💡 Patreon WordPress 1.2.4 Beta is available

#1

We are providing upcoming 1.2.4 version of the Patreon WordPress plugin to interested creators for testing.

This version highlights are:

  • Your integration will now acquire and use Patreon avatars of your users if they have a Patreon avatar and they dont already have an avatar at your WP site
  • A semi-important issue which may have forced re-acquisition of API credentials, leading to potential issues with post lock input boxes getting locked was fixed

Full changelog:

= 1.2.4 =

  • Plugin now automatically acquires Patreon avatar of Patreon users and uses it if they dont already have an avatar
  • Addressed reports of client credentials being deleted and forcibly refreshed
  • A rare issue which could cause spammy but harmless accounts being created when Patreon API was returning HTML was addressed
  • Unused remove_fetch_creator_id was removed

To install the 1.2.4 beta, just deactivate+delete your existing Patreon WordPress, and upload and activate the package below:

Your settings, info, locked posts will all stay the same.

When you install, the version will show 1.2.3, despite it is 1.2.4 beta. This will allow you to upgrade it easily from your plugin admin, later when 1.2.4 is actually released.

To revert back to 1.2.3, you can just deactivate/delete the 1.2.4 beta package you installed, and just install 1.2.3 from your plugin admin via WP org repository.

Any feedback and questions welcome!

Installed but content access looping back to the allow screen
Difficulties with Post Locking
#2

So this beta version uploaded and took the place without any issues. On the first try, it did something new and asked for access to the user profile. Once that permission was granted, it would go to a login option for “login with patreon,” “login with wordpress.” The user chose “login with patreon” and it took the user back to asking for access to the profile again.

So, I deleted the client token and started from scratch. Didn’t help. Am I doing something wrong? I’m just filling in the information and copying it over to the wordpress site. I’m not sure how I could be doing something wrong.

Thank you for your help so far.
SDW

#3

Once that permission was granted, it would go to a login option for “login with patreon,” “login with wordpress.”

Where does your user start the process from? From a locked post’s unlock button? Or, a ‘login with Patreon’ button in a login screen?

#4

From a locked post on wordpress. We have also tried to start at patreon and click on a link internally to push them into wordpress.

#5

So then the user is asked access, asked to pledge, and when he does that, is he returned back to your site?

#6

No, it cycles back to asking for access again.

#7

This may be due to some cookie situation at the browser of the user.

You can debug this more efficiently in the below fashion:

Create a new Patreon account with a new email. Then using another browser, pledge and login to your WP site with this new Patreon user. Just putting in a $1 locked test post and trying to unlock it will do.

This will allow determining if the issue is specific to that patron, or a general issue.

#8

Did you solve this issue?

#9

1.2.4 has just been released at WordPress.org repo:

#10

Not yet. It’s happening to every user at the moment. I’ve been busy and haven’t attempted to try anything else once all my users said they couldn’t access the site. Definitely not a cookie issue. I’m led to believe it’s something I’m doing, but I don’t know what that could be since it’s pretty much a copy and paste project. I’ll keep looking and let you know.

#11

You can check if you have any plugins that involve or modify cookies. Also, any oAuth plugins. If you have one, it may be taking over oauth procedure and you may need configuring it to recognize Patreon’s oauth.

Also ensure that caching does not interfere with the process - your site’s cache plugin, or host caching may be configured to show cached pages to even logged in users. Or there may be opcode cache in the server which may be interfering with the way pages rendered.

#12

Hello again,

I’ve had a web designer look at this and he can’t figure out why it’s still looping. The only thing I can figure out is that the subscriber MUST have a wordpress login. They do not. My goal was for them to have as few steps as possible. So, click from patreon, unlock on wordpress, read the webpage. Am I seeing this correctly? They have to make a wordpress login in order for this to work?

#13

Can you describe details of looping?

Do they click unlock, go through unlock flow, and then land back at your post but it is still locked?

Or something else?

#14

They click unlock, approve, login with patreon, approve, login with patreon, approve, login with patreon…neverending cycle. It never actually goes to Patreon or back to my site.

#15

So it never goes back to your site.

Is it the same when you yourself try with a test patron account?

#16

I don’t have a test patron account. I’ve used 3 different patron accounts to try and login and yes, it does it with all of them.

#17

I did make one of them sign up for a wordpress login, and that worked, but that wasn’t something I had anticipated needing to do.

#18

Can you check if ’ Enable strict oAuth’ option is enabled in your plugin settings…

#19

Ok so here’s a good update. And then a problem still lol

The Auth box was not checked that you asked me for.

Here was the issue: Before I found this plugin, I was using my beta testers to figure things out and had created them a wordpress login. So when they were trying to log in, the handoff was seeing that they had a wordpress login and wanted to authenticate them that way. I deleted all those and it works now…sort of…

I’ve had to walk them all through logging in because it never kicks them into my site. Here’s what we’re having to do: Unlock with patreon, allow patreon access, login to patreon (this leaves them on my patreon site to sign up which is great for people that haven’t yet, however, those that have are stuck here. I have to then tell them to click the link again and then it goes here), allow patreon, and finally to the page they were supposed to see.

This is ok for now because it’s just my beta group, but once I launch, I’m not going to have time to walk everyone through this. Have you seen this problem before and is there an easy fix?

#20

Which link is that? Allow Patreon is supposed to happen.