
What exactly did we want to achieve beyond just keeping Restrict Content Pro alive? I chose the last of the three options and, over the last five months, my team and I have been working to revitalize the product that was once the majority of my monthly revenue. It has a long way to go but we’re making significant progress and I’d like to share some of the journey with you now.Īmong the very first steps was to set goals. I could let it die a slow, drawn out death, I could sell it, or I could work to bring it back to life and let it kick ass again. I continued to let Restrict Content Pro dwindle for nearly two years before making a decision. I had several options. In 2014, however, I began to lose touch with the plugin as my other two big projects, Easy Digital Downloads and AffiliateWP, dominated more and more of my time. I updated it constantly and continued to push it further and further. For the first two years, the plugin thrived. I heavily relied on the plugin for my own site and thus had a greater commitment to it than the large plugins that came before.

It was not my first big plugin, nor even the second, but it was the first one that I developed a more intimate relationship with. Four and a half years ago, I released Restrict Content Pro on Code.
