sonne

Dear Jules,

submitting only visible fields is not an option since our forms are pretty huge and we only show parts of the form in multiple steps to make it easier for the user. By the way, this is how I handle it on shorter forms, where I only validate the visible fields.

In the meantime, we switched the method how we preset / prepopulate the field values. The values are empty now and set by javascript after the form has loaded. So it should be fine with your plugin now.

Again, thank you for your help and your usefull plugin!

Dear Jules,

sorry for my late reply. Indeed it is pretty similar to what you wrote. I wasn’t aware you could filter out / hide the email content in a similar way as done on the frontend, but…

Unfortunatelly, it won’t work for us for two reasons.

Some details for you to understand what we are doing: Our form is really huge, with many dependencies, etc. After it is submitted, an email (acutally two) are sent with the data formatted in a different way than on the frontend. Also, the data is saved to a database. So there are two problems with just using a group to hide content in the mail:

– I just can not hide blocks in the email since the data is structured differently.

– The data is saved to a database and the unwanted/hidden values are still present

So that’s why the fields need to be cleared/purged.

Is there any chance you’ll add that purge feature? My other option is to check all dependencies and clear all relevant fields accordingly, which I’d really love to avoid.

Thank you very much for your fast help!

Dear Jules,

that’s a valid point, acutally I’ll just need input fields to be purged since these values are preset on the server side, that is before the form is loaded.

Perfekt! Klappt.

Vielen lieben Dank Dennis!

UPDATE:
Although I have not received any feedback from DHL they must have noticed my post. Since Version 1.3.15 the tracking can be turned off now.

And when you’re at it, please consider adding an option to evaluate the sale price as well.

At the moment, it sorts only by the normal price. Even if a product with variations has a lower (sale) price on a specific variation than the normal lowest price of another variant.

Thank you!

workaround:
I just found out, that you can circumvent this issue by specifying URLs without the protocol. So if you write //www.xxx.yy instead of https://www.xxx.yy your links don’t get parsed and hence broken.

Can somebody else please also verify this?!

I have to thank you for your prompt reply.

Let me know if there is something I can test on an affected device.

If you dare, do the following modifications until a new version is available. This will remove the warning message as well as fix a problem when adding product bundles to the shopping cart.

classes/admin-form.php – approx. on line 20
look for:
function wcpb_add_product_bundle_type( $ptypes, $ptype ) {

replace (just remove the 2nd var) with:
function wcpb_add_product_bundle_type( $ptypes ) {

in classes/product-form.php – approx on line 143

look for:
$added_to_cart[] = $product_id;

replace with:
$added_to_cart[$product_id] = $quantity;