@Natman : Thanks a lot for creating this thread.
I bet the badges were not reviewed by Kailoon or Ivor.
+1 for DesignNova’s suggestion above. I also think you need to allow authors to set the “Support Policy”, where we can add what all is covered is support and what is called a “customization”, this could be different for different items/authors.
We are looking for a Full Time Support Guru to join our team at our office in New Delhi, India.
Job Requirements :
1. Handle support requests on our Support forum/emails.
2. Handle small customization requests.
3. Report bugs & issues and add them to the issue log.
4. This is a full time job.
Desired skills :
2. PHP, HTML, CSS, JS (jQuery),
3. Experience with tools such as Firebug or Chrome Developer tools
4. Excellent troubleshooting skills
5. Good Communication skills
6. Willingness to learn
7. Focus on customer satisfaction
1. 8 Hours a day, 6 Days a week.
2. Work from Office/home as required.
If interested, please email at vibethemes [ @ ] gmail.com or PM with the following details:
1. Your coding level skills (previous experience or a link to your portfolio)
2. Your financial expectations
3. Your contact details
Another point worth mentioning : you can not use copyright images in your template. Keep in mind “Free” does not mean commercially usable.
Hello everyone, thank you for sharing your portfolio . We picked the winners and they are:
Braxas, Theme20, VibeThemes and Fuelthemes. Welcome to dribbble guys .
@fuelthemes please send us link to your dribbble profile so we can send you the invitation.
@braxas, please add draft button to your dribbble profile so we can send you invitation.
Yay ! this really means a lot.Thanks a ton !
+ 1 , we also did a small experiment with Google Adsense, mainly search related ads and the outcome was not as expected. I wonder if bigger advertising budgets make any difference.
WPWiseOwl saidWell, the previous response was out of frustration of not finding results on debugging the issues after almost 12 hours, we had long known that TinyMCE 4.0 will bring issues. If you simply browse around you’ll find that there are many many people facing similar issues and all the blame will be given to the Plugin/theme authors and developers. Worst part is that TinyMCE 4.0 is not backwards compatible, several functions have simply been renamed/changed without a fallback.
WP 3.9 is one of the most unstable updates by WordPress so far. It has also meant death for many plugins using TinyMCE. Popular plugins such as Ultimate TinyMCE (over 2 million downloads) have declared end of life.
WooCommerce have already said they are not going to update. refer link.
, the compat3x does not work (link), The WP codex isn’t updated refer link ..I wonder why was there such haste to release it, when it was already known that upgrading TinyMCE to 4.0 would have issues and considering the impact of this on # of websites
LOL. You’re quite the drama queen aren’t you?
First off, I know change is hard. However, v3.9 isn’t as unstable as you claim. The release date was well known in advance. There were months where you could have tested more / provided more input during the betas and RCs. If you failed to get sufficiently involved then don’t blame the WP team.
Apparently, you’re unaware of the fact that Ultimate TinyMCE has only been Eol ‘ed because it’s been replaced with this (so not really dead) ...
WooCommerce is the brand rather the company. Woothemes will continue to update WooCommerce and the built in WC ShortCode will still work (no site breakage).
However, the ShortCode generator may just be MIA for a while. I know this can be fixed because it was already fixed on another plugin. It’s a TinyMCE issue rather than a WP one anyhow. If you’d done any amount of decent testing before release, you’d probably have already fixed it by now.So, the sky is not falling and it’s really just your own stuff need fixing. They’re only dead if you decide to abandon them in their current state.