-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Smidge JS conflict with Umbraco Deploy and Umbraco Forms dashboards #5
Comments
@hfloyd thanks for reporting. Somehow GitHub neglected to send me a notification about this issue, so I've only just seen it now. It's possible that there is a small syntax error somewhere in my package, which then only is a problem when the JS is minified. I will look into this 😉 |
By changing the environment of my test site from Development to Production, I can reproduce the issue. I bet it's caused by my attempt at cache busting here: I can't remember why I added this. I think Smidge will append the timestamp of the file when running in development mode, and if so, there is no reason for me to also attempting to bust the cache 🤪 |
Hi Anders! I'm not sure how Smidge is working, but it's possible that Umbraco is not using the bundler at all when |
This should now be fixed in v1.0.0-beta006. Thanks for reporting 👍 |
Yay! Fixed ✔ |
This might only be an issue on sites with Umbraco Deploy/Umbraco Forms installed. I came across it on Umbraco Cloud, where on the live environment the "Deploy" and "Forms" dashboards weren't loading and were throwing Console errors. The Limbo dashboard was loading, but not showing the data.
This was the information provided to me by Umbraco Cloud Support:
The specific Console errors:
Clicking the related error link https://code.angularjs.org/1.8.0/docs/error/$controller/ctrlreg?p0=Limbo.Umbraco.ModelsBuilder.Dashboard.Controller
Shows:
I'm not sure if there is something wrong in the Limbo CSS/JS or something in the bundling instructions for those files which is causing an issue...
The text was updated successfully, but these errors were encountered: