sparkweb

Can you look in the database in the wp_post_meta table and tell me what these fields look like? Is the name cuztom and the value serialized? If so, it might just be a case of needing to pass in pre-serialized content.

In the past when it hasn’t worked, I’ve found that it’s because of another plugin basically taking over the oEmbed process so it never gets to work. The first way to test this would be to disable all plugins except for this one and see if it works. Then start reenabling them until it doesn’t work any more to see which one is causing the problem. Some themes might be grabby with the oEmbed as well.

It should work. You just need to figure out how WooCommerce is saving this data (what the custom field is called) and then target that custom field with the updated data. You might look in the database or through the WooCommerce core code.

Although this might be better to just override it this way: http://wordpress.stackexchange.com/questions/119087/woocommerce-change-default-setting-is-sold-individualy-function

@zpro, would you mind helping me troubleshoot? When I ran into a problem before it was another plugin (Jetpack) that was taking over the oembed process. Would you mind sharing your list of installed plugins with me? I’d definitely like to fix this for you. Feel free to email me web -at- sparkweb [dot] net if you want to take the conversation off of this thread.

Thanks,
David

Put this in your theme’s functions.php file:

add_filters("hyrv_extra_querystring_parameters", "my_hyrv_extra_querystring_parameters");
function my_hyrv_extra_querystring_parameters($source) {
    return $source . "autoplay=1&wmode=opaque&showinfo=0&modestbranding=0&";
}

It should work with hidden fields – I can’t imagine why it wouldn’t. You’d just enter the name like “_hidden_field” and the new value. It should work fine. Let me know if you have any trouble with it.

You could try something like

if (get_post_type($post_id) == "post") {
...
}