-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.0.X, 7.1.X, Master
-
Fix Version/s: 7.0.0 DXP FP64, 7.0.X, 7.1.10 DXP FP4, 7.1.10.1 SP1, 7.1.2 CE GA3, 7.1.X, Master
-
Component/s: Frontend Infrastructure
-
Branch Version/s:7.1.x, 7.0.x
-
Backported to Branch:Committed
-
Story Points:0.25
-
Fix Priority:3
-
Git Pull Request:
Steps to reproduce:
- Start a 7.1 bundle with Fix Pack 2
- Create a structure with two text fields (name them field1 and field2), make field2 repeatable
- Create a template for the structure to display those fields
- Create a Web Content article1 using that Structure, type "AAA" in field1 and "One" in field2
- Create another Web Content article2 using the Structure, type "BBB" in field1 and "Two" in field2, then add another field2, type "Three" in it, then add another field2 and type "Four" in it
- Create a new Page
- Put an Asset Publisher there
- Go to its configuration - > Source -> Asset Type
- Choose Web Content Article -> your structure
- Turn Filter by field on, click on Select
- See that all fields are displayed properly
- Go back to configuration. On Source set Filter by Field (Yes). Select field1 and insert "AAA". Apply. Save.
- See that only Web Content1 is visible like it is expected
- Back to configuration -> filter by field, select field2 and insert "Four".
- Try to apply
Expected behavior: Filter can be applied and saved
Actual behavior: Filter cannot be applied/saved and an error message shows up in the browser's console
aui.js:1441 Uncaught Error: DDNodeScroll: Invalid Node Given: .lfr-form-content
at YUI.error (aui.js:1441)
at NS.setter (dd-scroll.js:391)
at NS._setAttrVal (attribute-core.js:851)
at NS._setAttr (attribute-core.js:657)
at NS.set (attribute-observable.js:69)
at NS.addAttr (attribute-core.js:455)
at NS._addLazyAttr (attribute-core.js:530)
at NS._getAttr (attribute-core.js:743)
at NS.get (attribute-core.js:490)
at NS.initializer (dd-scroll.js:403)