I've had this error in the past but cannot remember how it got resolved. Its showed up again after upgrading umbraco from v11 to v12. Whats also vexing is that it works, locally and on 1 azure webapp. When deployed to a second webapp (exactly the same configuration) we get the error described below.
Basically none of the editors are working in the backoffice and there is this js error. There is a controller error for any contentment editor on the doctype being edited at the time.
Error: [$controller:ctrlreg] http://errors.angularjs.org/1.8.3/$controller/ctrlreg?p0=Umbraco.Community.Contentment.DataEditors.ConfigurationEditor.Controller
at umbraco-backoffice-js.js.v638336437071827543:25:168
at umbraco-backoffice-js.js.v638336437071827543:117:19
at ea (umbraco-backoffice-js.js.v638336437071827543:99:20)
at p (umbraco-backoffice-js.js.v638336437071827543:90:355)
at g (umbraco-backoffice-js.js.v638336437071827543:84:186)
at umbraco-backoffice-js.js.v638336437071827543:83:311
at Object.link (umbraco-backoffice-js.js.v638336437071827543:321:432)
at umbraco-backoffice-js.js.v638336437071827543:35:134
at Ca (umbraco-backoffice-js.js.v638336437071827543:108:361)
at p (umbraco-backoffice-js.js.v638336437071827543:92:340) '<div ng-include="propertyEditorView">'
I've physically checked the content plugin files to ensure they are the same on each environment. The apps are in release mode and no redirects.
I haven't been able to reproduce this exact issue, but I'm aware that others have experienced this in the past too, so I'm unsure on how to go about resolving it (within Contentment itself).
Things to suggest trying would be...
Try deleting the Smidge\Cache folder, as something may have gone wrong during an upgrade or deployment.
Or, try adding the "bundleOptions": "Independent" option to Contentment's package.manifest file.
Angular error after upgrade
Hi
umbraco v12 contentment v4.5.0
I've had this error in the past but cannot remember how it got resolved. Its showed up again after upgrading umbraco from v11 to v12. Whats also vexing is that it works, locally and on 1 azure webapp. When deployed to a second webapp (exactly the same configuration) we get the error described below.
Basically none of the editors are working in the backoffice and there is this js error. There is a controller error for any contentment editor on the doctype being edited at the time.
I've physically checked the content plugin files to ensure they are the same on each environment. The apps are in release mode and no redirects.
Any ideas what I can try?
Thanks.
ok I see its possibly related to bundling...will investigate further.
excluding it from bundling has worked, not ideal but for now its fine.
re: https://our.umbraco.com/forum/using-umbraco-and-getting-started/108316-frontend-error-the-file-umbraco-backoffice-extensions-js-does-not-contain-any-reference-to-the-extension
Hi Sean,
I haven't been able to reproduce this exact issue, but I'm aware that others have experienced this in the past too, so I'm unsure on how to go about resolving it (within Contentment itself).
Things to suggest trying would be...
Try deleting the
Smidge\Cache
folder, as something may have gone wrong during an upgrade or deployment.Or, try adding the
"bundleOptions": "Independent"
option to Contentment'spackage.manifest
file.Failing that, I'm unsure. I'm open to suggestions from someone more knowledgably in the wider community.
Cheers,
- Lee
is working on a reply...