# Site kapot door ember 5 upgrade **URL:** https://meta.discourse.org/t/site-broken-due-to-ember-5-upgrade/297213 **Category:** Development **Created:** [28 februari 2024 om 20:55 UTC](https://meta.discourse.org/t/site-broken-due-to-ember-5-upgrade/297213 "2024-02-28T20:55:42Z") **Posts on this page:** 1 **Showing post:** 12
### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david) #### Post date: [29 februari 2024 om 10:22 UTC](https://meta.discourse.org/t/site-broken-due-to-ember-5-upgrade/297213/12 "2024-02-29T10:22:33Z")
Yup, I agree with @RGJ. Based on the ‘Ember not found’ error mentioned above, the most likely issue is the ‘ember-global’ deprecation. More details on that [here](https://deprecations.emberjs.com/v3.x#toc_ember-global) (linked from [the original announcement](https://meta.discourse.org/t/preparing-for-discourses-upgrade-to-ember-5/287211)). In these plugins, it looks like that’s being used for `Ember.Component`, and also for some `Ember.computed.*` calls. Here are a couple of quick PRs. It’s possible there are other issues which will reveal themselves after this fix is made, but I don’t see anything obvious skimming through the JS code. - [Resolve ember-global deprecation by davidtaylorhq · Pull Request #3 · featheredtoast/discourse-pushover-notifications · GitHub](https://github.com/featheredtoast/discourse-pushover-notifications/pull/3) - [Resolve ember-global deprecation by davidtaylorhq · Pull Request #1 · Sprachprofi/discourse-fcm-notifications · GitHub](https://github.com/Sprachprofi/discourse-fcm-notifications/pull/1) Thanks for the feedback on the rollout process! We’re constantly working to strike the right balance between progress and stability. We’ll definitely be taking what we’ve learned from this rollout and apply it to future upgrade/refactoring projects. --- _[View the full topic](https://meta.discourse.org/t/site-broken-due-to-ember-5-upgrade/297213)._