Terms and Conditions naming convention

  • Resolved Payment Plugins

    (@mrclayton)


    1 year, 5 months ago

    Hi Germanized Team,

    It looks like in a recent update that was released, the terms and conditions checkbox was given a display:none style attribute and a new field with name="legal" was added.

    That is causing some issues with our PayPal plugin as the terms and conditions field is validated before the PayPal button can be clicked. No click event is registered for the terms hidden field. Here is a screenshot showing the change in the html.

    View post on imgur.com

    Can you provide an explanation of why the naming convention was changed in this latest update? It looks like there is a way to change this back to the WooCommerce naming convention via the Germanized settings.

    Kind Regards

Viewing 1 replies (of 1 total)
  • Plugin Author vendidero

    (@vendidero)

    Hi there,

    there was no change in the naming conventions. This is the exact same name as the Woo core uses. Germanized is using a separate checkbox (which is not hidden) right from the start. The hidden (core) checkbox’ checked prop is synced with the Germanized checkbox.

    The only difference between the old and the new Germanized version is that we do not automatically trigger a change event when setting the checked prop of the hidden checkbox. We do mimic jQuery’s core behavior here as jQuery does not trigger a change event for a hidden field. This is due to compatibility issues with other plugins that wait for changes on input fields to refresh the checkout (which might result in infinite loops).

    Cheers

Viewing 1 replies (of 1 total)
  • The topic ‘Terms and Conditions naming convention’ is closed to new replies.