ActionView::Template::Error (no implicit conversion of Array into String) I recreated the login Oops Page error issue that seems to only affects admins and in some case other staff accounts, but in this case Admin acc, but only admin accs that are pre “git hang” by simply attempting another login. …

@merefield @Ed_S @Falco the only instance of this error I can find that is similar is here Error "no implicit conversion of Array into String" when using Gemini AI analysis on posts with images maybe I should have posted this topic in the Contribute > Bug section?

Kind of looks like something to do with presenting the upcoming changes - that’s something only admins would see. According to ask.discourse.com The entire feature is controlled by a hidden site setting called enable_upcoming_changes, set to false in a Rails console: SiteSetting.enable_upcoming_…

Thanks, I ran that command in rails console but it told me “command not found” :thinking: Ok tried that command and got this response: discourse(prod):001> SiteSetting.enable_upcoming_changes = false (discourse):1:in '<main>': undefined method 'enable_upcoming_changes=' for class SiteSetting (NoM…

ok sorry turns out the llm gave me outdated info. here are some commands I have tried and used. tabulate the admin users and the value of their setting for upcoming changes: # docker exec -it app rails r 'User.where(admin: true).each { |u| puts "#{u.id} #{u.username} #{u.user_option.enable_upcomi…

I always get a bit disoriented, so by root shell you mean going in via ./launcher enter app and the rails c?

Ok, the output: -1 system true No old or new admins, discobot or nobody else is tabulated. Maybe that’s the issue, it needs to be applied/turned on for the admin user in question, if so how to find it’s id?

Ok I ran the command again and found the id it’s 1, so the same setup. However when I input the below and run it, it’s showing => true x=1;User.find(x).user_option.update!(enable_upcoming_change_available_notifications: !User.find(x).user_option.enable_upcoming_change_available_notifications) We …

I suppose I should have gone for a simpler approach… # docker exec -it app rails r 'x=1;User.find(x).user_option.update!(enable_upcoming_change_available_notifications: false)' and similar. Not sure why I didn’t think of it that way.

I’m in the app and rails c, I paste that in and it outputs => true However, I checked it and it has flipped to false in the tabulated output. I tried the log in, but still hitting the Oops, maybe I need to rebuild?

Let me backtrack… what I was doing there was trying to change the admin preferences in the hope that the code which throws the exception wouldn’t need to run. But what we really want is to see if there’s a code bug which needs fixing, or something odd in your database which shouldn’t be there. Or …

Git-Hang und Admin/Mod-Benutzerkonten: Oops-Fehlerseite

Unterstützung Installation

Ed_S (Ed S) 2. Oktober 2026 um 11:02 21

Ja, ich glaube, das ist das Problem. Die LLM sagt, der Code verarbeitet eine Liste von Einträgen nicht gut, daher der 500er-Fehler.

Thema		Antworten	Aufrufe
Error for logged in users and Git hang Support	34	690	28. September 2026
Lost all categories and admin access Support	10	425	21. Juni 2024
40 Fatals and 7 Errors in recent logs Support	12	1854	17. Februar 2017
Locked out of my forum after restore Support	19	702	27. Januar 2025
The discourse stopped working with error 500 Internal Server Error Bug	1	3135	7. März 2017

Git-Hang und Admin/Mod-Benutzerkonten: Oops-Fehlerseite

Verwandte Themen