-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Open
Labels
Area: ContentComponent: WidgetIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P3May be fixed according to the position in the backlog.May be fixed according to the position in the backlog.Progress: ready for devReported on 2.4.xIndicates original Magento version for the Issue report.Indicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchThe issue has been reproduced on latest 2.4-develop branch
Description
Preconditions
- Magento 2.3.1 EE with sample data installed
- PHP 7.2
Steps to reproduce
- Open any CMS page
- In "Content" field add a Catalog Products List widget with settings:
Title = title
Number of Products to Display = azaza (or any other non-numeric value)
Display Page Control = No
Other settings have default values - Save the widget
- Save the CMS page
- Go to the CMS page
Expected result
Step 3:
Validation error appears as widget is saved due to incorrect input
Actual result
Step 5:
Exception: A non-numeric value encountered
http://dl4.joxi.net/drive/2019/06/26/0023/4040/1548232/32/4a91df8f78.jpg
Additional Information
- no exception now but validation should be Usage of non-numeric value for "Number of Products to Display" setting in "Catalog Products List" widget leads to an exception #23422 (comment)
Metadata
Metadata
Assignees
Labels
Area: ContentComponent: WidgetIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P3May be fixed according to the position in the backlog.May be fixed according to the position in the backlog.Progress: ready for devReported on 2.4.xIndicates original Magento version for the Issue report.Indicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchThe issue has been reproduced on latest 2.4-develop branch