Jaynesh saidI believe the idea is that themes in future should play nicely with all WP themes, including ones from WP.org and other sites. Therefore enforcing a naming convention wouldn’t work for obvious reasons.
aleluja saidNothing is left to luck here. If TF can enforce plugins they can enforce standards for naming.
Well until there are standards for the naming it should’t be let to luck. I (and themeforest and wordpress community) don’t want to take a risk between losing access to data and having everything work nicely. I agree it would be super-awesome but currently it’s just too risky.
Having a standard naming convention for CPTs is a discussion that until now haven’t reached any consensus in WP community (as far as I know). Although leading developers are all for it.
ThemeForest is in a position where she could take the lead.
The biggest problem I see is that each theme can take a different approach when handling Custom Fields and Meta Boxes. But, as long as it is not serialized data, after switching themes, the user should be able to access the previous data in the default Custom Fields meta box.A couple of discussions at [wp-hackers] and a great quote
Basically a plugin using Custom Post Types should follow Postel’s Law: “be conservative in what you do, be liberal in what you accept from others”http://wordpress-hackers.1065353.n5.nabble.com/Custom-Post-Types-and-pending-incompatibilities-td24661i20.html#a24674
ZOMG, huge step for ThemeForest!
Proper enqueue of jQuery is a must. I can’t count the number of times where I wanted to physically attack* theme authors for the bugs they caused.
(*please, NSA, I don’t have the means nor the will to do this, it’s a joke, ok?)
Haven’t read all this thread, but I’d like to suggest a “Certified” stamp of some sort for the themes which passed the requirements.
Long life to all TF creative bunch