Required Conditional Sub-Fields Not Enforced

  • Resolved esd3104

    (@esd3104)


    8 months, 4 weeks ago

    With some more digging I have, I think, figured out that the problem with required fields is limited to the requirement of an optional/conditional field presented based on the response of a prior field.

    I have a number of required Yes/No type questions which, based on a Yes response give another conditional question which is required to give a response. This was working fine until recently.

    It seems the most recent PPOM updates no longer enforce the “Required” requirement when they are shown based on the response to the prior question triggering the conditional PPOM field to be shown and required.

    WC 8.6.1
    PPOM 32.0.12
    WP 6.4.3
    PHP 8.2.16

    In the image the Blue highlights are the main questions and the yellow highlights are the conditional required fields based on a response give to a blue question. Can be seen on this product on my stage site. https://stage.namgbr.org/product/new-renew-1-year-north-america/

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter esd3104

    (@esd3104)

    UPDATE

    After more testing I think I am also seeing what is described in https://www.ads-software.com/support/topic/multiple-selections-not-showing-in-cart/

    While debugging the error I tried putting in values for the conditional questions and then noticed that they are missing from the cart. I tried disabling all other plugins except WC and PPOM and the issue remains so seems to not be conflict. I tried rolling back through all versions to 32.0.2 and still the issue remains.

    Here’s the entries I made on my product page:

    After hitting add to cart you can see that none of the conditional fields are carried over to the cart, the data is just dropped/missing.

    Thread Starter esd3104

    (@esd3104)

    Additional images to assist. Basically if a field is conditional then it seems that (a) the plugin doesn’t enforce it being required and {b) and data response collected for a conditional field is dropped on add to cart and lost completely for the WC order.

    Plugin Support AndreeaR

    (@andreearadacina21)

    Hi @esd3104,

    We appreciate your cooperation in reporting the issue you’re encountering. We are sorry for the inconvenience, and we have confirmed the problem. A bug report has been created and forwarded to our product development team for review.

    What happens next?

    Our product team will evaluate the impact of this issue compared to other open bugs and upcoming features, and assign a priority level to the bug report.

    Our developers prioritize the highest-priority issues first, so we cannot provide a specific timeline for resolution at this time.
    If you have any additional information that may assist with prioritization or resolution, feel free to reply to this email.

    We will update you once the issue is addressed and a fix is released. You may also check the product’s changelog for updates and fixes included in each release.

    If you have any additional questions or concerns, please feel free to start a new thread. Again, we apologize for the inconvenience and thank you for your patience.

    Best regards,

    Andreea

    Plugin Support AndreeaR

    (@andreearadacina21)

    Hey @esd3104,

    I hope this message finds you well. I am pleased to inform you that we have recently released an update for PPOM. This update includes a resolution to the issue you reported.

    We appreciate your patience and support during this process. If you have any further questions or require assistance with the update, please do not hesitate to reach out.

    Wishing you a great day ahead!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Required Conditional Sub-Fields Not Enforced’ is closed to new replies.