HTML issues with 3.13.1 Update

  • Resolved hokua

    (@hokua)


    2 years, 10 months ago

    Hi Richard,

    First, thanks for all of your effort with this plugin. We find it invaluable for what we need.

    After updating to 3.13.1, our page layout below the Payeezy form appears broken. I discovered that the #other_amount div doesn’t close. I was able to test and fix this by adding a close </div> to line 866 in the wp-payeezy-pay.php plugin file.

    While troubleshooting the issue, I also found that there are a number of validation errors on the #payeezy-amount related to the type, placeholder, autocomplete, and required attributes. Not sure if these will cause problems, but figured I’d let you know.

    I’ll stay tuned for an update before I continue on to update my version.

    Thanks again.

    • This topic was modified 2 years, 10 months ago by hokua.
    • This topic was modified 2 years, 10 months ago by hokua.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Richard Rottman

    (@rickrottman)

    2 years, 10 months ago

    Thank you so much Brian!

    I just committed an updated version (3.15) that should take care of the issues. I appreciate you letting me know about them. I wish I knew how the invalid type of “num” happened instead of “number.”

    Thanks again!

    Thread Starter hokua

    (@hokua)

    2 years, 10 months ago

    You are most welcome! And it was very gracious of you to thank me on the plugin update.

    I applied the update and did notice that our layout was still broken. I see the closing div for #other_amount on line 409, but the one inside the $mode2 if/else block is missing. Adding a close div on line 361 fixed it for me.

    I did notice that the get_file_contents function threw a bunch of errors in my local environment, but I believe it’s because my local SSL couldn’t be verified for some reason. It isn’t happening in production, so not worrying about it as it’s probably just a setting on my end. I only mention it in case it helps someone else who may also experience the errors.

    Thanks again!

    • This reply was modified 2 years, 10 months ago by hokua.
    • This reply was modified 2 years, 10 months ago by hokua.
    Plugin Author Richard Rottman

    (@rickrottman)

    2 years, 10 months ago

    I went ahead and added a closing div to line 361. The theme I’m using for testing (Astra) never showed a problem. After I added the closing div to line 361, the published form looked the same. Weird.

    The reason I added the get_file_contents is because I wanted to make the code easier to read. Moving the CSS and the dropdowns to separate files made things a lot easier for me to read.

    Thanks again for letting me know. I appreciate the feedback!

    Thread Starter hokua

    (@hokua)

    2 years, 10 months ago

    Hey Richard,

    Thanks for the quick update on this! I applied the latest patch and everything looks and works great.

    Completely understand using get_file_contents. Makes perfect sense. I’m confident any warnings on my end are specific to my local SSL setup.

    Thanks again,
    Brian

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘HTML issues with 3.13.1 Update’ is closed to new replies.