Patrons being told to pledge again to gain access


#1

Hi

I’ve just added the Patreon Wordpress plugin to my website fifascoutingtips.com. I’ve made one post patron-only. However, when my patrons click the login button to unlock the content, they’re taken to Patreon and told to pledge in order to gain access, even though they have already pledged.

Is there any way to fix this so that they get the correct login box and can gain access?

I should add that even I can’t see the post or log in to unlock it.

Thanks.


#2

If they are not logged in, they would be taken to the pledge flow normally.

Now with pledge again to get access - you mean every time they try to unlock, they get asked to pledge again?


#3

Sorry for the delay, I didn’t have internet access for a few days.

Yes, they click the button to log in with Patreon and get taken to a page on the Patreon website where they are asked to pledge again.

Thanks,

Alex


#4

So this happens on the login/connect with patreon button, but it doesnt happen with the ‘unlock with patreon’ button that are on locked posts?


#5

As far as I can tell it happened in both situations. I know one of my patrons managed to fix it by allowing Patreon access to his profile, but I don’t know how he got to that situation in the first place without being looped back and asked to pay again.

If that makes sense!


#6

If its ok, please arrange a new admin account for me - with a strong password - and mail it to ozgur@c.patreon.com . I’ll check this on-site. This extra account should be deleted after debug is complete.


#7

How was this resolved? Having the same issue.


#8

Where are you hosted? At WordPress.com?


#9

WP via commercial hosting service (1&1).


#10

Similarly - if possible, please arrange a Wp admin account for me (with complex password) and mail me at ozgur@c.patreon.com . Along with site name, wp admin login url etc.


#11

To all who posted 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:


#12

To all who posted 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.


#13

To all experiencing this issue:

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.