Bug #30361
closedChanging a Content View on a single Content Host twice throws an angular error but works still
Description
When changing a Content View on a single Content Host, after changing it once, then going back and changing it again we get an Angular JS error and my message does not show up. This exists in master and downstream on 6.7
bastion.debug-3be20f16e0c6ea4f2e1ee7b02d33fe5c40c5c91a92984387734152afe3f1e4e6.js:32303 TypeError: v2.contentViews is not a function
at fn (eval at compile (bastion.debug-3be20f16e0c6ea4f2e1ee7b02d33fe5c40c5c91a92984387734152afe3f1e4e6.js:1), <anonymous>:4:156)
at Scope.destination.<computed> [as handleOptions] (bastion.debug-3be20f16e0c6ea4f2e1ee7b02d33fe5c40c5c91a92984387734152afe3f1e4e6.js:28143)
at Scope.$scope.edit (bastion.debug-3be20f16e0c6ea4f2e1ee7b02d33fe5c40c5c91a92984387734152afe3f1e4e6.js:98367)
at fn (eval at compile (bastion.debug-3be20f16e0c6ea4f2e1ee7b02d33fe5c40c5c91a92984387734152afe3f1e4e6.js:1), <anonymous>:4:132)
at callback (bastion.debug-3be20f16e0c6ea4f2e1ee7b02d33fe5c40c5c91a92984387734152afe3f1e4e6.js:45687)
at Scope.$eval (bastion.debug-3be20f16e0c6ea4f2e1ee7b02d33fe5c40c5c91a92984387734152afe3f1e4e6.js:36129)
at Scope.$apply (bastion.debug-3be20f16e0c6ea4f2e1ee7b02d33fe5c40c5c91a92984387734152afe3f1e4e6.js:36228)
at HTMLDivElement.<anonymous> (bastion.debug-3be20f16e0c6ea4f2e1ee7b02d33fe5c40c5c91a92984387734152afe3f1e4e6.js:45691)
at HTMLDivElement.dispatch (foreman-vendor.bundle-v4.11.1-development-8f1002a20f1552db88e3.js:327442)
at HTMLDivElement.elemData.handle (foreman-vendor.bundle-v4.11.1-development-8f1002a20f1552db88e3.js:327254)