I would like to ask, is this prompt normal?
1 Like
chapoi
February 11, 2026, 8:33pm
2
Most people here don’t speak Chinese so it’s hard to tell. It would be helpful to translate necessary info in English when asking for support on this forum.
1 Like
Moin
February 11, 2026, 8:43pm
3
The error is “The requested URL or resource could not be found.”
But without context on what @sniper756 was doing when that appeared, that doesn’t help.
Sorry, my description was unclear. I will now upload a screen recording video for feedback.
The page is located at: admin/config/upcoming-changes
As soon as I select “Admins Only,” it throws an error: “An error occurred: The requested URL or resource was not found.”
1 Like
chapoi
February 12, 2026, 7:08am
5
This has nothing to do with the new foundation styling changes, so moved it in its own topic.
1 Like
chapoi
February 12, 2026, 7:09am
6
@rishabh can the free plan not use the upcoming changes maybe?
1 Like
Moin
February 12, 2026, 8:56am
7
Maybe it’s not upcoming changes in general, but upcoming changes affecting the Foundation theme, because that’s not available.
chapoi
February 12, 2026, 8:58am
8
Could be, regardless I’d like to keep the other topic focussed on feedback for the actual theme styling changes. We can figure this issue out separately.
chapoi
February 12, 2026, 9:32am
10
Just tried it out and can’t repro.
Can you try it in safe mode @sniper756 , just to be sure? And is there anything in the console when you trigger the error?
1 Like
Moin
February 12, 2026, 9:37am
11
I think I have a repro. I see the same, and my forum is not on the free plan. It feels like it’s related to the group names being translated. Enabling it for everyone worked, but “staff” failed.
I need to get to my laptop to check the browser console.
chapoi
February 12, 2026, 9:39am
12
So, your interface language is set to something else and then it triggers? Tried that and still nothing.
Or some other way of translating?
2 Likes
rishabh
February 12, 2026, 9:41am
13
Same, no repro on a stock Free site and the page works fine for me.
Moin
February 12, 2026, 9:41am
14
The names of the default groups, like staff, are based on the forum’s default language, not the interface language (and after changing that, you need to trigger the ensure DB consistency job, or wait until it runs automatically).
1 Like
Moin
February 12, 2026, 9:46am
15
Not sure this is helpful:
PUT https://my-forum.discourse.group/admin/config/upcoming-changes/groups 404 (Not Found)
send @ jquery.js:9940
ajax @ jquery.js:9521
o @ ajax.js:216
x @ ajax.js:229
saveGroups @ upcoming-change-item.gjs:127
enabledForChanged @ upcoming-change-item.gjs:247
await in enabledForChanged
handleInput @ d-select.gjs:40
handleMouseUp_ @ unknown
Instead of “staff-only” the result is “everyone”
The error doesn’t match the interface language. It’s the German version of
Moin
February 12, 2026, 9:58am
16
Since the group’s name is “team” on my forum, it doesn’t surprise me that this fails.
Is it possible to refer to the IDs instead of names?
@sniper756 Does it work for you if you select the group manually by using the last option in the dropdown?
For me selecting “Specific group(s)” and then the staff / team group worked
1 Like
chapoi
February 12, 2026, 10:01am
17
Ok thanks for getting the repro. Moved this to bug. @martin
4 Likes
I’ve been working and just got off work, so I have time to check the reply now. It seems it’s already being resolved. Discourse is very efficient, I like it a lot.
1 Like
I just tried it, and the official discourse.group is normal. The issue is with the Discourse I deployed on my own VPS.
martin
(Martin Brennan)
February 13, 2026, 5:26am
22
Thanks for the reproduction Moin, I wasn’t aware that automatic group names could be changed in this way. Fix is here:
main ← issue/uc-staff-localization-group
merged 11:07PM - 24 Feb 26 UTC
We have a "Staff" option for upcoming change items that was sending
the `staff`… group name to the server. I had assumed that our automatic
groups could not be renamed, but this is not the case. If your
`default_locale` for your site is changed, the automatic group names
change via `Group.refresh_automatic_groups!` in a background job.
This means that if you change your `default_locale` to `de` (German),
the `staff` group becomes `Team`, and the upcoming changes that are set
to "Staff" will now be looking for the `staff` group, which no longer
exists, causing errors.
This commit fixes the issue by always using the localized staff
automatic group name, both for the value of the dropdown, and in
successs messsages etc.
c.f.
https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/16
4 Likes