Bug #9485
closedCreating a composite initially sends you to a page to add components that is empty
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1186974
Description of problem:
When creating a composite content view, you are sent initially to the page where you can add components, however this list is empty. Navigating to some other page (or tab) and back causes the list to be loaded properly.
javascript error seen:
TypeError: Cannot set property 'numSelected' of undefined
at new <anonymous> (http://abed.usersys.redhat.com:3000/assets/bastion/components/bst-table.directive.js?body=1:31:34)
at invoke (http://abed.usersys.redhat.com:3000/assets/bastion/angular/angular.js?body=1:3711:17)
at Object.instantiate (http://abed.usersys.redhat.com:3000/assets/bastion/angular/angular.js?body=1:3722:23)
at http://abed.usersys.redhat.com:3000/assets/bastion/angular/angular.js?body=1:6773:28
at http://abed.usersys.redhat.com:3000/assets/bastion/angular/angular.js?body=1:6186:34
at forEach (http://abed.usersys.redhat.com:3000/assets/bastion/angular/angular.js?body=1:311:20)
at nodeLinkFn (http://abed.usersys.redhat.com:3000/assets/bastion/angular/angular.js?body=1:6173:11)
Version-Release number of selected component (if applicable):
nightly
How reproducible:
always
Steps to Reproduce:
1. Have at least one Content view already published
2. Create a new composite content view
3. After hitting Save, you will be redirected to the page to add components
Actual results:
List is empty
Expected results:
List is populated
Additional info:
Updated by Eric Helms about 10 years ago
- Is duplicate of Bug #8834: When creating a composite content view, the components page is initially blank added
Updated by Eric Helms about 10 years ago
- Status changed from New to Duplicate
- Triaged changed from No to Yes
Updated by Eric Helms over 8 years ago
- Translation missing: en.field_release set to 166