Don’t forget that Internet Explorer 8, 9, and 10 are a requirement for all ThemeForest themes so if the theme you purchased doesn’t work in them, you can get a refund. Don’t spend more of your money on something that should come with the theme as part of the marketplace policies.
Don’t confuse a buyers. It’s not a true.
A gift for a real man
greenshady saidI guess you’re 2.3 themes don’t have as many features and custom made solutions as most of current themes here, so I woudn’t go that far. My point is that there were 6 Release Candidates so plenty of time to check all themes and fix what’s needed.
greenshady saidYeah, because authors live in future and they just come here to make themes for 5 versions in advance… Seriously, if something is made to work on 3.4 and when you bought it, it never said it’ll work with future versions, you don’t come here crying and go all-caps rage on authors because your template doesn’t work after you updated WP without even bothering to find out whether the template is compatible with latest version of WP or not. Though I don’t know how goes this whole migration thing with WP, but this was generally speaking…
Message to buyers: If you get an error when updating your theme, it most likely means your theme author done something wrong. You should not need to get confirmation from your theme author that it’s okay to update your copy of WordPress.
I’ve coded themes for WordPress 2.3 that still work to this day with WordPress 3.5. I’ve been doing this thing a lot longer than most people here, so don’t feed me some line about not living in the future.
WordPress builds in backwards compatibility for everything. It also properly deprecates functions so that authors have many, many versions to update their code.
If your theme is properly coded, it will not break when WordPress updates. That’s why we have standards set in place to avoid this sort of problem.
I.e. Contact with the theme author. It’s a public forum