# 💡 Patreon WordPress locking options guide

**URL:** <https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135>\
**Category:** Wordpress Plugin\
**Created:** [September 20, 2018, 9:03pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135 "2018-09-20T21:03:59Z")\
**Posts on this page:** 20\
**Page:** 4

<div class="post-metadata">

**Author:** ![Hexxet](https://avatars.discourse-cdn.com/v4/letter/h/ee7513/32.png) [@Hexxet](https://www.patreondevelopers.com/u/Hexxet)\
**Post date:** [January 20, 2023, 7:28pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/61 "2023-01-20T19:28:26Z")

</div>

I am using “WP Media Manager Lite” to have a folder structure in my Media library. But I deactivated all Plugins except for the Patreon plugin in one try and it still did nothing.  
(PS: I can lock posts perfectly fine. The problem really only occurs when trying to lock files in the Media Library)

---

<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:** [January 23, 2023, 10:47am UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/62 "2023-01-23T10:47:37Z")

</div>

Any plugin that changes the structure of the media folder in ways that WP does not do by default could cause issues with image locking. The plugin relies on the attachment being identifiable via standard WP functions and manipulate images through those functions. If those dont succeed in doing that, it would flop.

Give a try to reverting your WP to default media folder structure without that plugin - or you can alternatively set up a duplicate of your site in some random domain without that plugin and test if the locking works with your images. (You may have to set up the plugin at that domain for the second time).

---

<div class="post-metadata">

**Author:** ![Hexxet](https://avatars.discourse-cdn.com/v4/letter/h/ee7513/32.png) [@Hexxet](https://www.patreondevelopers.com/u/Hexxet)\
**Post date:** [January 23, 2023, 1:29pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/63 "2023-01-23T13:29:02Z")

</div>

I did deactivate that plugin when testing. Did once again, and uploaded a new image after deactivating it which I tried to lock. So, that one is not touched by the plugin in any way and the Plugin is not active → doesn’t work :(.

---

<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:** [January 25, 2023, 8:06pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/64 "2023-01-25T20:06:13Z")

</div>

If the plugin changed the media folder structure already, deactivating it wont revert it back. If you deactivate it, then upload a new image, and test image locking on it, that may provide some pointers. But old images should have been sorted by that plugin already so its unlikely that they may work.

---

<div class="post-metadata">

**Author:** ![Hexxet](https://avatars.discourse-cdn.com/v4/letter/h/ee7513/32.png) [@Hexxet](https://www.patreondevelopers.com/u/Hexxet)\
**Post date:** [January 25, 2023, 8:57pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/65 "2023-01-25T20:57:01Z")

</div>

Which is exactly what I did.  
One question: You speak of **Image locking** which is something special in your plugin correct? I’m talking about using the same UI there is to lock a whole post in my Media Library (since that UI it is displayed there). I do not have the checkbox Imagelock active in the plugin, as I think it’s only something to lock an image within a post or page.  
 → Are we talking about two different things? Or do I need to activate Image locking for the Media library UI to work?

---

<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:** [January 26, 2023, 3:45pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/66 "2023-01-26T15:45:37Z")

</div>

> I do not have the checkbox Imagelock active in the plugin

That is what enables image locking. Without that on, the interface in your media library wont work.

---

<div class="post-metadata">

**Author:** ![Hexxet](https://avatars.discourse-cdn.com/v4/letter/h/ee7513/32.png) [@Hexxet](https://www.patreondevelopers.com/u/Hexxet)\
**Post date:** [January 26, 2023, 5:50pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/67 "2023-01-26T17:50:40Z")

</div>

Okay. I did activate that checkbox now. Deactivated ALL plugins except the Patreon one, uploaded a NEW image to my media library and tried to add a Tier lock. Still the same result: No Patreon lock parameters are saved to the image, and the combo box resets to Everyone($ exact). [No Errors in the Browser Console]

I’ve found this error request here: [How to use image locking feature in Patreon WordPress plugin - #12 by elioscipioni](https://www.patreondevelopers.com/t/how-to-use-image-locking-feature-in-patreon-wordpress-plugin/461/12)  
I seem to have the same problem. But there is no solution found in that post either.  
Anyway, I just read there, that locking will not work for PDF or ZIP anyway, though that was 2 years ago. Does the locking only work for images or has this been extended by now? (Note that I did try with an image, but if it does not work for PDF and Zip I don’t think I’m interested in this feature anyway, even if it did work).

---

<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:** [January 31, 2023, 5:22pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/68 "2023-01-31T17:22:32Z")

</div>

If you are using any CDN (Jetpack, Cloudflare etc), image locking cant works since those CDNs copy the images, making image locking difficult.

And nope, currently the plugins dont support locking non-image files. That may be implemented in near future.

---

<div class="post-metadata">

**Author:** ![Hexxet](https://avatars.discourse-cdn.com/v4/letter/h/ee7513/32.png) [@Hexxet](https://www.patreondevelopers.com/u/Hexxet)\
**Post date:** [January 31, 2023, 6:07pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/69 "2023-01-31T18:07:36Z")

</div>

Ok.  
Consider my issue closed.  
I was really just looking for a possibility to lock zip/pdf file Url/downloads.  
If that gets implemented soon that would be brilliant.

---

<div class="post-metadata">

**Author:** ![Hexxet](https://avatars.discourse-cdn.com/v4/letter/h/ee7513/32.png) [@Hexxet](https://www.patreondevelopers.com/u/Hexxet)\
**Post date:** [February 2, 2023, 6:54pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/70 "2023-02-02T18:54:58Z")

</div>

Got another question about the " Require active membership at post date" functionality.  
You write, “_will require the user to have been a patron at the date or before your content was posted._”  
This kinda contradicts the name of the functionality… and I hope it is wrong.  
So Example… I do posts every month and lock them with that option. if I have a Patron who signed on with me for the first month of my campaign, and then unpledged. And then one year later he comes back. Does he have access to a whole year of content with paying only for two months?  
Please tell me this is not the case…

---

<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:** [February 3, 2023, 9:17pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/71 "2023-02-03T21:17:37Z")

</div>

If you use that feature, only patrons who were patrons with that tier at the date of that post and before will be able to access those posts. If they never canceled their pledge. New patrons from the same tier or higher tiers wont be able to access the post in any way whatsoever.

---

<div class="post-metadata">

**Author:** ![Hexxet](https://avatars.discourse-cdn.com/v4/letter/h/ee7513/32.png) [@Hexxet](https://www.patreondevelopers.com/u/Hexxet)\
**Post date:** [February 3, 2023, 10:19pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/72 "2023-02-03T22:19:12Z")

</div>

Phew, okay that’s good.🙂  
Just once more to verify what happens in such a case:

Patron P signed up with Tier T on 01.01.2022 and unsigns on 01.03.2022. Then later he signs up again on 01.06.2022 again with the same Tier and keeps being signed on.  
Now, when we look at the following three posts which are all posted for that Tier T:  
Post Po1 was created on 15.01.2022  
Post Po2 was created on 02.03.2022  
Post Po3 was created on 02.06.2022

I assume in this case Patron P would only have access to Post Po3. The other two posts would be locked for him since his new signup date 01.06.2022 is now relevant. Is that correct?

---

<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:** [February 4, 2023, 2:02pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/73 "2023-02-04T14:02:41Z")

</div>

> [@Hexxet](#):
>
> I assume in this case Patron P would only have access to Post Po3.

Yes that’s the case.

---

<div class="post-metadata">

**Author:** ![Hexxet](https://avatars.discourse-cdn.com/v4/letter/h/ee7513/32.png) [@Hexxet](https://www.patreondevelopers.com/u/Hexxet)\
**Post date:** [February 4, 2023, 2:44pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/74 "2023-02-04T14:44:37Z")

</div>

Okay, thanks for the quick answer 🙂  
I can work with that 🙂

---

<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:** [February 6, 2023, 5:09pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/75 "2023-02-06T17:09:39Z")

</div>

Note that you can also use the historic pledge locking option to make sure that only patrons who have pledged you that amount in total can access the content. It overrides all others. So a 1-month-old $10 patron wont be able to access a $20 content if its locked also from $20 historic pledge. But a 2-month old $10 patron, will be able to since the historic pledge requirement of $20 would be fulfilled.

---

<div class="post-metadata">

**Author:** ![Hexxet](https://avatars.discourse-cdn.com/v4/letter/h/ee7513/32.png) [@Hexxet](https://www.patreondevelopers.com/u/Hexxet)\
**Post date:** [February 6, 2023, 8:50pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/76 "2023-02-06T20:50:44Z")

</div>

Yes, thanks. That is exactly what I plan on doing 🙂

---

<div class="post-metadata">

**Author:** ![Hexxet](https://avatars.discourse-cdn.com/v4/letter/h/ee7513/32.png) [@Hexxet](https://www.patreondevelopers.com/u/Hexxet)\
**Post date:** [February 7, 2023, 8:10am UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/77 "2023-02-07T08:10:14Z")

</div>

Hello, two more questions sorry 🙂

1.) Is there a way for a Patron to find out his current life-time-support for me so he can predict when a certain post will get available to him? Either on Patreon or via this plugin?

2.) I’m on Subscription Billing, so I assume when I post something on 14.02.2023, advertise it, and somebody joins up fresh on 15.02.2023 he/she can not access this post if I’m using the historical pledge locking option. That’s correct, right?  
If that’s the case, Is there maybe an option somewhere (maybe in pro?) to define an offset so a Patron can actually access posts let’s say 4 days prior to his sign-on?

---

<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:** [February 7, 2023, 9:29pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/78 "2023-02-07T21:29:13Z")

</div>

When a patron that does not yet qualify for such a post visits that post, there should be some information in the interface text and footer that tells them how much is required. Though it may not be telling how long will it take.

---

<div class="post-metadata">

**Author:** ![Gravity\_Novels](https://avatars.discourse-cdn.com/v4/letter/g/96bed5/32.png) [@Gravity\_Novels](https://www.patreondevelopers.com/u/Gravity_Novels)\
**Post date:** [January 8, 2024, 11:05am UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/79 "2024-01-08T11:05:28Z")

</div>

So when i select patreon instead of showing that on frontend, its showing amount.

---

<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:** [January 9, 2024, 7:19pm UTC](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135/80 "2024-01-09T19:19:17Z")

</div>

You need to give a bit more detail there. Where do you select Patreon and how?

[Previous page](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135.md?page=3)

[Next page](https://www.patreondevelopers.com/t/patreon-wordpress-locking-options-guide/1135.md?page=5)
