# Membership Login Button

**URL:** <https://www.patreondevelopers.com/t/membership-login-button/2282>\
**Category:** Wordpress Plugin\
**Created:** [September 26, 2019, 2:33pm UTC](https://www.patreondevelopers.com/t/membership-login-button/2282 "2019-09-26T14:33:50Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![samdamico](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/samdamico/32/1060_2.png) [@samdamico](https://www.patreondevelopers.com/u/samdamico)\
**Post date:** [September 26, 2019, 2:33pm UTC](https://www.patreondevelopers.com/t/membership-login-button/2282/1 "2019-09-26T14:33:50Z")

</div>

I’m using the Patron Pro plugin.  
Is there a way that I can create a “Log In” button on my website that allows Patrons to log in to Patreon via that login button on my website?

I’m hoping the effect would be;

1. Those who use the login button get access to the content appropriate for their tier level.
2. They get redirected to a “Members Main Page” on my website that serves as a directory to various tier levels.

Thank you.

---

<div class="post-metadata">

**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:** [September 26, 2019, 3:09pm UTC](https://www.patreondevelopers.com/t/membership-login-button/2282/2 "2019-09-26T15:09:50Z")

</div>

1 - The unlock buttons which appear when you lock any content via PW or Patron Pro would accomplish most of that - login, pledge, redirect, content accessible. Additionally Patron Pro’s gating shortcode does that as well.

Also you can use the [patreon\_login\_button] shortcode of PW to print out a login button which will allow anyone to login with Patreon. In post content.

PW also adds this button to login forms. So any proper login form that you put anywhere should show normal user/pass login, and also Patreon login.

2 - Redirection now is something that should be done on WP side. There are many redirection plugins to do these in custom fashion. You can use a condition to identify patrons via the metas added for them and you can redirect them to a patron page whenever they log in via normal login.

Its not recommended to wholesale redirect patrons since it would break the smooth unlock flow that patrons use to unlock your content. This also is a good flow to gain new patrons via your content.

---

<div class="post-metadata">

**Author:** ![samdamico](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/samdamico/32/1060_2.png) [@samdamico](https://www.patreondevelopers.com/u/samdamico)\
**Post date:** [September 26, 2019, 3:17pm UTC](https://www.patreondevelopers.com/t/membership-login-button/2282/3 "2019-09-26T15:17:29Z")

</div>

Thank you, CB.  
My apologies for my newbieness.  
What’s PW?

---

<div class="post-metadata">

**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:** [September 26, 2019, 4:05pm UTC](https://www.patreondevelopers.com/t/membership-login-button/2282/4 "2019-09-26T16:05:13Z")

</div>

PW = Patreon WordPress the official free plugin. Patron Pro is a premium addon to the official plugin.

---

<div class="post-metadata">

**Author:** ![samdamico](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/samdamico/32/1060_2.png) [@samdamico](https://www.patreondevelopers.com/u/samdamico)\
**Post date:** [September 26, 2019, 4:44pm UTC](https://www.patreondevelopers.com/t/membership-login-button/2282/5 "2019-09-26T16:44:34Z")

</div>

Thank you, CB.  
I’m using the Patron Pro addon.  
I got it because I like the feature of being able to use shortcodes to make selected content within a post “Patron Only”.

---

<div class="post-metadata">

**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:** [September 26, 2019, 4:56pm UTC](https://www.patreondevelopers.com/t/membership-login-button/2282/6 "2019-09-26T16:56:08Z")

</div>

Great! Please remember that you can post support tickets at [Codebard.com](http://Codebard.com) to get premium support (free) for Patron Pro issues…

---

<div class="post-metadata">

**Author:** ![samdamico](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/samdamico/32/1060_2.png) [@samdamico](https://www.patreondevelopers.com/u/samdamico)\
**Post date:** [September 26, 2019, 7:04pm UTC](https://www.patreondevelopers.com/t/membership-login-button/2282/7 "2019-09-26T19:04:25Z")

</div>

Thank you. Would you prefer us to contact you via [Codebard.com](http://Codebard.com)?

---

<div class="post-metadata">

**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:** [September 26, 2019, 8:03pm UTC](https://www.patreondevelopers.com/t/membership-login-button/2282/8 "2019-09-26T20:03:19Z")

</div>

For Patron Pro cases in general, it would be more efficient yeah.

---

<div class="post-metadata">

**Author:** ![samdamico](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/samdamico/32/1060_2.png) [@samdamico](https://www.patreondevelopers.com/u/samdamico)\
**Post date:** [September 26, 2019, 8:14pm UTC](https://www.patreondevelopers.com/t/membership-login-button/2282/9 "2019-09-26T20:14:54Z")

</div>

Ok.  
Could we finish the Patron Pr issue we have going on in a seperate thread here?

---

<div class="post-metadata">

**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:** [September 27, 2019, 12:13pm UTC](https://www.patreondevelopers.com/t/membership-login-button/2282/10 "2019-09-27T12:13:22Z")

</div>

Either works - if its sufficiently different from what we discussed, better in a ticket.
