I’m writing a blog post/series/presentation about this topic currently, but here’s a TL;DR on WordPress workflow in a team from an answer I provided on Reddit.
When managing dozens of WordPress sites for dozens of different users, streamlining the support process using an excellent help desk system quickly becomes a priority.
If you are not familiar with Zendesk, it’s a help desk / ticketing system on steroids allowing you to manage support requests, setup response macros, manage a knowledge base, and more.
My Admin Zendesk Help Widget plugin (ya … bad name) utilizes Zendesk’s web widget which you can configure via a simple plugin settings page. Customizing the widget is easy in your Zendesk dashboard – you can change the colors, position of the Help button, and much more. Information about the current logged in user auto populates the fields and when a user submits a support requests it shows you what page the request was made from in the Zendesk ticket.
Installing, activating, and configuring the plugin can be done in 60 seconds. All you need is a Zendesk account and to know your subdomain (that will make sense if you have already signed up).
TL;DR – I wrote a WordPress plugin to add Terms and Conditions to the registration form when using the Restrict Content Pro plugin .
I just recently built a WordPress membership site using the Restrict Content Pro plugin and a few add-ons. However since they were taking money (via Stripe) in the registration process the user wanted a terms and conditions checkbox to ensure the customer knew what they were getting with the membership.
I figured this might come in handy so I built and released a plugin for it.
Upon installation and activation, you will see a new submenu item under “Restrict” called “Terms”.
Under “Terms” you will see a simple admin settings page that allows you to set the label for the Terms and Conditions checkbox that shows up on the registration form as well as the link to your terms and conditions (whether that’s a page on your site or a PDF on a CDN).
Plugin code on Github: Restrict Content Pro Terms and Conditions
Install via WordPress Plugin repo: Restrict Content Pro – Terms and Conditions
A few notes… the ‘PostType’ property of the Post class can be set to either “post” or “page” depending on which WordPress type you want to publish. And the ‘Status’ property can be set to either “publish” or “draft” depending on whether you want to publish your new post/page right away or not. In the future I’d like to make these enums or something extendable. But WordPress has them as strings so you can define new ones (ie Custom Post Types) on your own.
Keep in mind this class is merely a simple example. In most cases you might want this in a service layer where you can inject the WordPressSiteConfig class as you need it.
If you are in Central Iowa and love WordPress – please let me know if you’d like to attend a monthly user group. I am currently organizing an early 2015 launch – gathering interest and getting some direction from other user group organizers.