I vote no on Sharepoint. It’s slow, overly complicated and just plain awful to work with IMO . I don’t miss it. Never heard of Orchard though. No offense meant, just my 2 cents.
There’s some good ideas here. I’m hopeful they’re not simply discarded because implementing anything remotely resembling something here seems “hard”.
Often (but not always) anything worth doing is NOT easy. I think that depending on execution, it could be worth it to authors but Envato might indeed decide it’s not worth it for them. It’d likely benefit Authors, Purchasers and Visitors more than Envato. However, making those groups happier might end up benefitting Envato more than they know potentially.
I’d like to see a home page section of most recently updated items (not unlike how “new” items are displayed potentially?). Would be (re-)purchasers might think an item is too old to still be supported after a while. Keeping the items that are updated on a semi-regular basis would make authors compete for that home page space.
It might also help balance the traffic between new / old items. Old items that don’t get updated somewhat deserved to be forgotten about. The author can then decide how much time they would like to put into any particular product. The more an item gets updated, the more often it’s featured.
I’ll leave it to Envato to decide how to sort the listing, what constitutes an updates, etc. However, authors that submit updates that are mere (undocumented) bug fixes with nothing else should be given a lower rank, of course IMO . There will be some who may try to game the system but that shouldn’t stop Envato from doing something like this at all.
I’d like to think that if this were implemented that then the mostly reasons a product would die is that an author gave up / stopped updating it?
I can somewhat feel your pain. If you’ve ever submitted an app to Apple (for iOS) like I have (even recently), you know that Apple is often (in my experiences) just as inconsistent with it’s reviewing. I let my developer account lapse this year but I still hear complaints from other developers. This is one particular attribute of Apple that no one needs to copy.
I’ve sadly seen many of what I’d consider (take that for what you will) to be ThemeMonster quality themes instead of the often superior ThemeForest quality. That’s just my opinion but as a buyer, I’ve been made somewhat afraid of what I’ve been seeing. Please don’t pollute the forest.
All support inquiries like this should initially be directed at the author unless support isn’t being offered. In this case, the author is offering support. That isn’t really what these forums are for.
So when you request support, you’ll want to say whether you’re using the HTML template or the WP theme. That wasn’t clear n your post. One could make assumptions from your post but I won’t. You might also include the OS, browser and version of each to speed things along.
Author email / contact page: http://themeforest.net/user/two2twelve (must be logged in to see “Email” area)
Author support site: http://themes.two2twelve.com/support/
I found this information on the item’s product page. So you can always visit them if you want for more information.
After these avenues have been exhausted and still don’t resolve your issue then you can come back here. Good luck!
So it’s Chrome but it’s not Chrome at the same time. It’s quite far from perfect IMO . It’s a decent browser on nearly every other platform beside iOS. Having Chrome on iOS in this form may just contribute further to browser fragmentation IMO but we’ll have to see about that.