Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
IPCommerceFan Posted March 14, 2022 Posted March 14, 2022 4.6.10 all customizations disabled default theme I'm not sure how long this has existed, however I've encountered it while working on an application that adds custom validation to the package form. Steps to reproduce: Create a custom text field, set it to Required, and assign it to a package= On the front end, view packages in List View. This adds a "Choose Options" button Click Choose Options, do not fill out any fields, and try to add to cart A new element will be added below the form each time "Add to cart" is clicked, instead of showing that the required field was not filled out If the field is filled out and add to cart is clicked, all the extra elements disappear and you can proceed to checkout: Without reloading the page - If you click Continue Shopping, and try to Add to Cart without entering anything in the field, you get this: If we add some instrumentation to listen in on \IPS\Helpers\Form::values() , we see that the "form_required" error is being added to the element, but is just not displaying correctly via the template: Validation works great when accessing the package directly (via Grid view), or when updating the purchase form in the client area. It is only when the form is generated by the 'Choose Options' button that it behaves this way. Frankly I don't use List view - I've considered just disabling it as an option - but I imagine some customers might prefer it, so please let me know if I can do or add anything to help get this resolved.
Jim M Posted March 14, 2022 Posted March 14, 2022 Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release. DudeThatsErin, IPCommerceFan and SeNioR- 1 2
Solution Marc Posted August 8, 2022 Solution Posted August 8, 2022 This has been resolved in the recently released 4.7..1 version of the platform. Please upgrade to that version if you are experiencing this issue, and if you still have any problems, please let us know. IPCommerceFan 1
Recommended Posts