Sorry for off-topic but I have a question regarding native wp theme customizer.
1. Is there a way to increase width of customizer ? 2. Is there posibility to add tabs inside customizer ?
When it comes to standards and best practices Wordpress itself is great example of spaghetti code. Of course it shouldn’t be an excuse for writing bad code but I think it’s very easy to judge on somebody, without providing real solutions to solve problems in the community.
Can somebody explain me the hookworm thing ? The only thing I found on net is this
Question as above. If somebody buys gpl theme and make customization (images mainly), can somebody else take this customization ?
This is a market place. Authors want to sell, authors want to be different from the rest. And yes, it’s a good thing that we moving more towards the good practices and uses as WordPress.org intended, but this is still a market place: no place for happy opensource wordpress plugin packages for all to share so we all get themes with all the same shortcode happiness.edit: besides, most authors already share enough – which is a good thing at the level it’s going on now..
This has nothing to do with WordPress.org. This has to do with the great WordPress community, including the commercial market as a whole.
If you don’t know who I am, I am one of the co-founders of Gravity Forms. One of the most successful commercial WordPress plugins on the market. 99% of our support issues related to theme conflicts we encounter are caused by poorly developed ThemeForest themes. 99%. This is a fact.
I can tell you with 99% accuracy when one of our support team encounters a conflict caused by a poorly developed theme that the theme is from ThemeForest. Sadly i’m not exaggerating at all.
What ThemeForest authors that don’t know what they are doing don’t realize is how their work impacts others. Our company has wasted more money in support time dealing with issues caused by poorly developed ThemeForest themes than you’ve made in your entire time selling WordPress themes.
All this could be avoided by simply following best practices… guidelines being implemented by Envato now.
I don’t give a damn if this makes Theme Authors get in the good graces with WordPress.org or the open source communithy, what I give a damn is about ThemeForest themes not wasting my employees valuable time and my money paying them to support poorly developed themes.
A side effect of this is we help these customers fix these crap themes. And then they’ll never buy a ThemeForest theme again. This impacts ThemeForest and Envato. Not the author.Standards and guidelines help prevent situations like this. Quit fighting. Accept it. Find a way to work with it. Your work will be better for it. Envato is doing a good thing.
Could you elaborate ? Are these css namespacing issues or lack of standard wp hooks ? Could you share some examples ?