Stuff it everyone! But seriously, Happy Thanksgiving to all
Unzip the zip file you downloaded from CodeCanyon, and the installable zip should be found directly inside that.
edit, need to drink more coffee so I can read better
I’m thankful for all the awesome people I’ve met here on the Envato marketplaces. Customers, fellow authors and staff
if(sales === 0 && purchases === 0 && firstComment === ‘flagged’) autoDisableEntireThread();
For me, I figure that 70% of whatever they sell the support for is infinitely more money for me than the 100% of the $0 that I current charge for lifetime support. Don’t get me wrong, I’d love to have 90% instead of 70%, but like I said, it’s more money than I’m charging now. Like I said in my previous reply on here, I’d still love to see an actual support system solution implemented here for that 30% cut that they take.
I know lots of authors are comfortable with their own support systems, but when you look at this from a customer’s perspective it’s really a no-brainer in my opinion. For example, when a customer buys 10 items, they’re sent to 10 different support sites, where they have to create and keep track of 10 different logins, and then find and enter their purchase code information for all 10 sites.
The power to never need sleep!
Here’s the big question. When the SaaS customer contacts them for support do they send the customer to you??
Congrats Unodor Definitely wish I was in your shoes!
Wishing you the best Dan. Thanks for the great communication and improving the elite program
doesn’t maintain and run a general WP theme/plugin forum
This is a great idea. What takes up most author’s time is the fact that most customers seeking support have very poor troubleshooting skills. So the public forum could exist for this specific purpose. Some examples:
- Check to see if the customer is using the latest version of the plugin/theme, and provide information about how they can update.
- Teach the customer how to identify conflicts (temporarily deactivate other plugins, switch to TwentyFourteen, etc.)
- Remind customers that purging WP cache plugins often solves lots of issues.
- Identify and communicate front-end console errors to the customer.
- Identify and communicate broken HTML markup (often caused by custom filters).
So nothing specific to the actual product(s), but basic things that will teach customers how to troubleshoot their sites. Because the biggest support burden doesn’t come from the 10 customers who ask only 1 question. It comes from the 1 customer who asks 10. And it’s always the latter who has very poor troubleshooting skills.