# Oeps na het updaten naar Discourse 2.9 vanwege de Discourse QA plugin

**URL:** https://meta.discourse.org/t/oops-after-updating-to-discouse-2-9-due-to-discourse-qa-plugin/217589
**Category:** Support
**Created:** [8 februari 2022 om 22:17 UTC](https://meta.discourse.org/t/oops-after-updating-to-discouse-2-9-due-to-discourse-qa-plugin/217589 "2022-02-08T22:17:40Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![yhmtsai](https://avatars.discourse-cdn.com/v4/letter/y/47e85d/32.png) [@yhmtsai](https://meta.discourse.org/u/yhmtsai)
#### Post date: [8 februari 2022 om 22:17 UTC](https://meta.discourse.org/t/oops-after-updating-to-discouse-2-9-due-to-discourse-qa-plugin/217589/1 "2022-02-08T22:17:40Z")

</div>

after update to discourse 2.9, when I login to discourse website, it gives Oops page.  
If no login, all are fine.

![image](https://global.discourse-cdn.com/meta/original/3X/7/a/7a136ecb6838fe171062dc4f2e2b7c032052750e.png)  
after restarting, it only takes 1s but it is still failed.

I got the following from rails/production.log

```plaintext
Started GET "/" for 46.223.162.135 at 2022-02-08 21:56:20 +0000
Processing by ListController#latest as HTML
Completed 500 Internal Server Error in 40ms (ActiveRecord: 0.0ms | Allocations: 12759)
NoMethodError (undefined method `>=' for nil:NilClass)
(eval):72:in `_fast_attributes'
app/controllers/application_controller.rb:605:in `preload_current_user_data'
app/controllers/application_controller.rb:411:in `preload_json'
app/controllers/application_controller.rb:387:in `block in with_resolved_locale'
app/controllers/application_controller.rb:387:in `with_resolved_locale'
lib/middleware/omniauth_bypass_middleware.rb:71:in `call'
lib/content_security_policy/middleware.rb:12:in `call'
lib/middleware/anonymous_cache.rb:356:in `call'
config/initializers/100-quiet_logger.rb:23:in `call'
config/initializers/100-silence_logger.rb:31:in `call'
lib/middleware/enforce_hostname.rb:23:in `call'
lib/middleware/request_tracker.rb:198:in `call'

```

safe-mode also happen.

Is there anything I can try or provide?

---

<div class="post-metadata">

### Author: ![yhmtsai](https://avatars.discourse-cdn.com/v4/letter/y/47e85d/32.png) [@yhmtsai](https://meta.discourse.org/u/yhmtsai)
#### Post date: [8 februari 2022 om 22:52 UTC](https://meta.discourse.org/t/oops-after-updating-to-discouse-2-9-due-to-discourse-qa-plugin/217589/2 "2022-02-08T22:52:47Z")

</div>

after I delete the QA plugin from app.yml, it works again.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [18 maart 2022 om 01:29 UTC](https://meta.discourse.org/t/oops-after-updating-to-discouse-2-9-due-to-discourse-qa-plugin/217589/3 "2022-03-18T01:29:37Z")

</div>

The Discourse Q&A plugin is in the process of being adopted by the Discourse team.

I recommend against installing it anywhere until @tgxworld makes the announcement that we are ready.

That said, it is very likely the error reported here is no longer an issue.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [17 april 2022 om 01:30 UTC](https://meta.discourse.org/t/oops-after-updating-to-discouse-2-9-due-to-discourse-qa-plugin/217589/4 "2022-04-17T01:30:09Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.