Thank you very much for the reply!
Yes I can see how this use case would be seen as a customization request. I am working on finding a solution independently and am happy to share more details.
If there is a simple way to have the html code for the product groups generated inside the single-content-product template or something it would enable the adding of unique classes and IDs to the input and label fields, which the user can then add their own CSS and JS logic to.
Of particular interest, this can allow users to assign different default values for different products that use the same fields, disabling and enabling fields based on the status of other inputs, and a lot more that I can see having wide appeal as features.
I have tried to implement a solution you can see here (the “chest center” and “precious stone” field and values give a good example of newly introduced logic), by copying the html that the plugin generated, pasting it into my page template, then setting the display of the original html to none. It works on the client side, however the fields do not validate or carry over now to the cart or checkout page.
I am trying to read through the product.php file and the templates in the frontend directory to see how I might enable them to be validated like the originally generated fields, but am not having success applying the rules to validate the fields on checkout.
If there is a quick solution you can see from your perspective – it would be hugely appreciated and unlock a ton of potential that this plugin can have. Even just pointing me in the right direction would be a huge help – I’ll be sure to come back on here to share if I find a solution of course ??
Thank you very much!
Evan
-
This reply was modified 5 years, 2 months ago by
Evan.