Josef Wittmann

Allows you to upload a set of coupon codes you want to distribute to your users. Each coupon is assumed to be used only once.
You can manage multiple sets of coupons from different sources.
Your users are shown a popup next time they visit the site. They have are only shown the coupon after clicking a button, to ensure interest.
<h4>Usage</h4>
After installing, you’ll find a new menu item in the admin area near the bottom called ‘Coupons’. All administration is done from there.
There are coupons and (coupon) groups. 
Each coupon belongs to exactly one group and has a value and expiry date. 
A group contains many coupons and defines the template that is shown to the users within a popup. By default, only logged in users can get coupons.
Start by creating a new group. Give it an unique name and write out the template. 
There are four buttons in the editor, which mark the speical areas for the popup. Highlight the according text and press the button to mark it up.
<ul>
<li>Action button: When this button is clicked, the coupon’s value will be fetched from the backend and displayed.</li>
<li>Success area: This area is hidden until the coupon is fetched from the backend.</li>
<li>Coupon value: This area will be replaced with the coupon’s value. Make sure to not include trailing whitespace, otherwise it may look ugly.</li>
<li>Expiry date: This area will be replaced with the coupon’s expiry date. Make sure to not include trailing whitespace, otherwise it may look ugly.</li>
</ul>
Save the group and add some coupons. You can add multiple coupons with the same expiry date. Just make sure that every coupon gets its own line (empty lines are ignored).
Now you’re ready to go. But you may want to have a look at the default settings. There you can adjust delays between events to not spam your users.
<h4>Customization</h4>
Most of the user-facing customization can be done in the group editor. If you want to change the users which should be able to get coupons, you can hook into the <code>unique_coupons_user_is_authorized_for_coupons</code> filter. Currently, there is no way to distribute coupons to anonymous users (keeping track is done server-side). So even if you allow this through this filter, it will not work.
<h4>Shortcomings/Bugs</h4>
<ul>
<li>For now, data from this plugin will stay around after deleting it.</li>
<li>You can’t explicitly filter when the popup shouldn’t be shown. The best workaround is to hook into <code>unique_coupons_user_is_authorized_for_coupons</code>.</li>
</ul>
<h4>Contributing</h4>
The source code is hosted on <a href="https://github.com/Josef37/unique-coupons" rel="nofollow ugc">Josef37/unique-coupons</a>. 
Feel free to create a new issue, when you have questions or feature requests, or consider making a pull request. 
There is a separate <a href="https://github.com/Josef37/unique-coupons/blob/main/README_DEV.md" rel="nofollow ugc">developer README</a>, which helps you set up the development environment.
If this plugin helped you in any way, I’d like to hear your feedback.

Unique Coupons

derekheld

Personal Library allows you to restrict users to seeing their own media uploads. The plugin works by filtering all requests for attachments.
<ul>
<li>Administrators will always see all attachments</li>
<li>Enable or disable access to all uploads for the following roles: contributor, author, editor.</li>
</ul>

Personal Library

Restricts users to managing/using their own attachments only.

Unique Coupons vs Personal Library