Out of the box, Restrict Content Pro requires members to enter a username when registering. This makes sense because RCP uses the built-in WordPress user database, and the username is a requirement. However, we often see people wanting to use the email address as the username, and they want to know how to remove the username field from the registration form. This is pretty easy to do with just a few lines of code. Let’s take a look.
Restrict Content Pro allows members to upgrade or downgrade their subscriptions, but sometimes people ask for ways to tweak the way it works. Sometimes they want to: prevent members from downgrading to cheaper subscriptions, prevent members from upgrading to more expensive subscriptions, prevent members from changing their subscriptions at all, or prevent members from getting a prorated credit when switching their subscriptions. Let’s take a look at the ways to handle all these scenarios.
When a website visitor doesn’t have access to restricted content, Restrict Content Pro has two settings to control the message that is shown: one for content that requires a paid subscription, and one for content that requires a free subscription. This works great for people who want fine-grained control over the upsell messages they show to people without an active subscription, but sometimes they want a custom message for a specific page to further refine their upsell messaging. Let’s look at how that can be done.
When I was still actively involved in the day-to-day support for Easy Digital Downloads (EDD), two questions I saw quite often was how to charge vendors to publish products in the Front-end Submissions (FES) extension and how to limit the number of products they can publish. After moving from Easy Digital Downloads to Restrict Content Pro (RCP), I still saw our EDD team talking about people asking for it. There’s not a way built into FES to do this, so after replying to a late night support ticket for RCP, I decided to create a way to do it.
2015 was great. 2016 here I come.
There are lots of ways you can contribute to WordPress. Many people that use it contribute in some way, even if it’s simply reporting a bug. I’ve contributed by reporting bugs, editing and improving documentation on the Codex, helping out in the support forums, fighting for what I think is right on Trac, giving away free themes and plugins, and probably other things I’m forgetting right now.
Now I’m a “core” contributor.
This means that code I wrote was accepted into WordPress itself and is now released to the public. That code is now running on over 1.6 million sites at this time of this post. WordPress 4.4 was released yesterday.
That number will continue to increase for years. Pretty cool.
Craftsmanship is at an all-time low.