Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
7.0.X, 7.1.X, 7.2.X, Master
-
7.2.x, 7.1.x, 7.0.x
-
Committed
-
2
Description
Default value of Indexable field setting for new structures should be configurable from System settings
This setting will allow to disable this Indexable field setting by default to avoid the Elasticsearch "Limit of total fields being exceeded" error
Steps to Reproduce:
- Add Structure in Web Content
- Add any type of field, notice the 'Indexable' property is defaulted to yes option
- Save test structure with a field
- (Master/7.2.x) Go to Control Panel > Configuration > System Settings > Web Content > Administration (7.1.x/7.0.x) Go to Control Panel > Configuration > System Settings > Dynamic Data Mapping > Dynamic Data Mapping Web
- Check to see the option that says: Structure Fields Indexable Enable
- Uncheck 'Structure Fields Indexable Enable'
- Go back to Web Content > Structures
- Clear cache
- Add new structure
- Add any type of field, notice the 'Indexable' property is defaulted to no
Expected Result:
- Unchecked 'Structure Fields Indexable Enable' sets the default value of property 'Indexable' to no
- Checked 'Structure Fields Indexable Enable' sets the default value of property 'Indexable' to yes
Actual Result:
Step 5: There is no option for 'Structure Fields Indexable Enable'
Attachments
Issue Links
- causes
-
LPS-103386 Unchecking "Structure Fields Indexable Enable" does not set the default value to no for a field in Structure
- Closed
- demands
-
LPS-103224 Elasticsearch "Limit of total fields has been exceeded" error is produced if you have a lot of DDM Structures
- Closed
- relates
-
LPS-125376 As a web content Admin, I want the default value of the Searchable property to follow the behavior defined in system settings
-
- Closed
-