"Categorie opslaan" knop blijft grijs als categorie aangepaste permissies heeft

Fout
,
1

I edited the topic’s title to point out the exact issue, see the replies for details

When editing category settings, the save button is and stays greyed out.

Oddly, the button will magically be active again if we alter the category color inputs, either by changing the category color input, or by clicking the text color input, then the category color input.

The button is never not greyed out for categories that don’t have default permissions settings (everyone can read, post and create), or are pre-seeded categories.

I may have missed some subtleties about this bug, but this is what I experience.

Discourse version: 3.6.0.beta1-dev(0fa102b838)

Safe mode doesn’t fix the issue.

2 likes
2

FWIW Looking at your first video the text colour is set as #FFF which I don’t think passes the validation for the field (it needs to be 6 characters or more):

Having that too short would grey out the save button.

2 likes
3

Wow. This is the issue. The pre-seeded categories thing doesn’t exist, the text color was set to #FFFFFF in this one category.

If I set #FFFFFF as the text color category, then the problem vanishes.

/admin/logs/staff_action_logs shows that I never set the text colors to #FFF. It was the default value. It was a migration from vBulletin to Discourse, if it’s of some importance.

Perhaps the import script set the value to #FFF, avoiding the validation script and creating this bug (though I’m not sure at all import scripts set colors…). :person_shrugging:

1 like
4

I think someone else tripped over this recently as well - Access to category after 10 posts (automatic group membership)

I think that was a migration too. I’m not sure if some magic could be added to autocorrect obvious ones as part of the category save?

2 likes
5

Ik heb hetzelfde probleem op andere gemigreerde forums van phpBB, die zo oud zijn als 2018 tot minder dan een jaar geleden.

Het lijkt erop dat in gemigreerde forums alleen de categorieën die door de scripts zijn aangemaakt, hun kleur op #FFF hebben ingesteld. Dus ik vermoed dat er een onderliggend probleem is om op te lossen dat elke importer beïnvloedt.

2 likes
6

I think the issue can be fixed by changing this line:

By replacing FFF with FFFFFF.

1 like
7

Darn. I should have waited until October 1st

2 likes