Quote:
Originally Posted by CyberSEO
Are you kidding on me? No, really? 
- When exactly WordPress has added these "shortcode api"? In version 2.5? The freeware plugin you are referring to was written years before it. How could it use something which wasn't even implemented in WP?
- The most important thing to me is to keep all versions of the plugin compatible. If I switch it to WordPress shortcode API, it automatically became incompatible with the old versions, so all my customers will lost their video embeds right after the update. How dumb you must be to fuck your customers (almost 9k downloads from WP repository and who knows how many from my site directly) for your ego only?
How exactly do you think this new WordPress shortcode API works? You will be shocked but they also use regular expressions and they are far more complicated than the one used in KVS FLV Player and KVS Player Pro. I mean this one: "'\[flv:(.*?)\]'ie" - oh, it's sooooo complicated, ah? 
You mean it requires flash and doesn't work with HTML5? Yes Sir, you are absolutely right. As I told you earlier, the freeware KVS FLV Player plugin was written years before the HTML5 has became an essential standard. In other words: it's frickin old and I'm going to update it right today. |
What happens if I want to use your player with a custom field?
that is why the shortcode api is handy, since you arent doing a shortcode using the api, you cant run do_shortcode on the get_post_meta, so if i want to use the player how would i use it with a custom field? unless you have a way of doing that.
not saying the plugin is bad or anything, just a matter of trying to use it with a wp custom field wont work, unless you can somehow apply_filters with the_content on the custom field?
