# Issue with enabling upcoming changes

**URL:** https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881
**Category:** Bug
**Tags:** translation, upcoming-changes
**Created:** [February 11, 2026, 6:06pm UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881 "2026-02-11T18:06:09Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![sniper756](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sniper756/32/545002_2.png) [@sniper756](https://meta.discourse.org/u/sniper756)
#### Post date: [February 11, 2026, 6:06pm UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/1 "2026-02-11T18:06:09Z")

</div>

![screenshot_20260212_014233](https://global.discourse-cdn.com/meta/original/4X/9/d/a/9da604a74d6762743973c15185b828b16d63f0d6.jpeg)

I would like to ask, is this prompt normal?

---

<div class="post-metadata">

### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [February 11, 2026, 8:33pm UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/2 "2026-02-11T20:33:35Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [February 11, 2026, 8:43pm UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/3 "2026-02-11T20:43:02Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![sniper756](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sniper756/32/545002_2.png) [@sniper756](https://meta.discourse.org/u/sniper756)
#### Post date: [February 12, 2026, 3:16am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/4 "2026-02-12T03:16:49Z")

</div>

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.”

---

<div class="post-metadata">

### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [February 12, 2026, 7:08am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/5 "2026-02-12T07:08:42Z")

</div>

This has nothing to do with the new foundation styling changes, so moved it in its own topic.

---

<div class="post-metadata">

### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [February 12, 2026, 7:09am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/6 "2026-02-12T07:09:31Z")

</div>

@rishabh can the free plan not use the upcoming changes maybe?

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [February 12, 2026, 8:56am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/7 "2026-02-12T08:56:15Z")

</div>

Maybe it’s not upcoming changes in general, but upcoming changes affecting the Foundation theme, because that’s not available.

---

<div class="post-metadata">

### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [February 12, 2026, 8:58am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/8 "2026-02-12T08:58:24Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [February 12, 2026, 9:32am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/10 "2026-02-12T09:32:30Z")

</div>

> [@chapoi](#):
>
> can the free plan not use the upcoming changes maybe?

Just tried it out and can’t repro.

Can you try it in [safe mode](https://meta.discourse.org/t/53504?silent=true) @sniper756, just to be sure? And is there anything in the console when you trigger the error?

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [February 12, 2026, 9:37am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/11 "2026-02-12T09:37:30Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [February 12, 2026, 9:39am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/12 "2026-02-12T09:39:53Z")

</div>

So, your interface language is set to something else and then it triggers? Tried that and still nothing.

Or some other way of translating?

---

<div class="post-metadata">

### Author: ![rishabh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rishabh/32/179446_2.png) [@rishabh](https://meta.discourse.org/u/rishabh)
#### Post date: [February 12, 2026, 9:41am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/13 "2026-02-12T09:41:22Z")

</div>

> [@chapoi](#):
>
> > [@chapoi](#):
> >
> > can the free plan not use the upcoming changes maybe?
> 
> Just tried it out and can’t repro.

Same, no repro on a stock Free site and the page works fine for me.

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [February 12, 2026, 9:41am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/14 "2026-02-12T09:41:46Z")

</div>

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).

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [February 12, 2026, 9:46am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/15 "2026-02-12T09:46:33Z")

</div>

Not sure this is helpful:

```plaintext
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](#):
>
> “The requested URL or resource could not be found.”

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [February 12, 2026, 9:58am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/16 "2026-02-12T09:58:20Z")

</div>

![image](https://global.discourse-cdn.com/meta/original/4X/d/9/1/d91f9629ba8ed763651d8dd10c13f528edb3a414.png)  
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

---

<div class="post-metadata">

### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [February 12, 2026, 10:01am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/17 "2026-02-12T10:01:08Z")

</div>

Ok thanks for getting the repro. Moved this to bug. @martin

---

<div class="post-metadata">

### Author: ![sniper756](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sniper756/32/545002_2.png) [@sniper756](https://meta.discourse.org/u/sniper756)
#### Post date: [February 12, 2026, 11:34am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/18 "2026-02-12T11:34:18Z")

</div>

Yes ~~~~~~~~~~

---

<div class="post-metadata">

### Author: ![sniper756](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sniper756/32/545002_2.png) [@sniper756](https://meta.discourse.org/u/sniper756)
#### Post date: [February 12, 2026, 11:35am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/19 "2026-02-12T11:35:10Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![sniper756](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sniper756/32/545002_2.png) [@sniper756](https://meta.discourse.org/u/sniper756)
#### Post date: [February 12, 2026, 11:36am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/20 "2026-02-12T11:36:30Z")

</div>

I just tried it, and the official discourse.group is normal. The issue is with the Discourse I deployed on my own VPS.

---

<div class="post-metadata">

### Author: ![martin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/martin/32/491371_2.png) [@martin](https://meta.discourse.org/u/martin)
#### Post date: [February 13, 2026, 5:26am UTC](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881/22 "2026-02-13T05:26:29Z")

</div>

Thanks for the reproduction Moin, I wasn’t aware that automatic group names could be changed in this way. Fix is here:

[https://github.com/discourse/discourse/pull/37797](https://github.com/discourse/discourse/pull/37797)

[Next page](https://meta.discourse.org/t/issue-with-enabling-upcoming-changes/395881.md?page=2)
