There are no visible groups

After I upgraded/rebuilt less than an hour ago. I am seeing the message in the title on visiting the group index page at /g.

I also can’t visit individual group pages as admin (they work okay in a private window without logging in). I get

Server Error

while trying to load [/groups/CTRG.json](https://domain.com/groups/CTRG.json)

Error code: 500 error

I see the following in logs:

NoMethodError (undefined method `notification_level' for "category-theory":String)
app/serializers/basic_group_serializer.rb:152:in `block (3 levels) in <class:BasicGroupSerializer>'
app/serializers/basic_group_serializer.rb:151:in `filter'
app/serializers/basic_group_serializer.rb:151:in `block (2 levels) in <class:BasicGroupSerializer>'
(eval):53:in `_fast_attributes'
app/controllers/application_controller.rb:438:in `serialize_data'
app/controllers/groups_controller.rb:93:in `index'
app/controllers/application_controller.rb:340:in `block in with_resolved_locale'
app/controllers/application_controller.rb:340:in `with_resolved_locale'
lib/middleware/omniauth_bypass_middleware.rb:68:in `call'
lib/content_security_policy/middleware.rb:12:in `call'
lib/middleware/anonymous_cache.rb:336: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:22:in `call'
lib/middleware/request_tracker.rb:176:in `call'

where category-theory is the name of a tag. I had set up group level notifications for that tag a few days ago.

Probably because of the recent change at https://github.com/discourse/discourse/commit/5ef9d4d5371d8bad557168de643a13a483be1ebc#diff-c96b511ee7c983981c1e144bfd00c3da cc: @tgxworld

1 Like

Per @tgxworld (it’s too late for him to investigate right now), the commit has been reverted.
https://github.com/discourse/discourse/commit/86764f3aac9297e0638cb0843d5f401b5e8f4205

Give it a bit for tests to run, once you see it on https://github.com/discourse/discourse/tree/tests-passed, go ahead and update!

5 Likes

The commit has been reverted and we’re working on another fix.

5 Likes