Hi, I searched the forum but I couldn’t find an answer to help me solve an issue with my freshly installed Discourse instance (with the DigitalOcean image). So basically, the problem is that some settings in Customize aren’t properly saved (the green confirmation button works, but the changes aren…

Looks like you were affected by this bug: Translation fields not working If you update Discourse it should be fixed now, thanks for letting us know.

Hi Olivier, Note that the Digital Ocean one-click install isn’t supported here and we always advise following the standard install . :slight_smile: Can you provide one or several examples of settings names that won’t be saved?

My guess would be some browser extension.

Sure! Here is an example: [Screenshot 2023-06-27 at 17.37.46@2x] Another example: [Screenshot 2023-06-27 at 17.39.53@2x] None of the two text fields save when I update them. I tried to modify these fields in Edge, Safari and in DiscourseHub, it always fails. As I tried in different browser, I…

Also, I had no idea only one install type was officially supported. Is it easy/possible to reinstall my instance following the official install guide and not losing the work I already done with it? I have a bunch of plugins and already some content I would prefer not to lose. Thanks!

I can repro the issue in two other components. It’s the same as Translation fields not working - #2 by Canapin .

If you know how to edit app.yml to change plugins and rebuild, the biggest problems with the DO installation are resolved. It’s pretty close to the standard install except it skips discourse-setup. When you have cause to move to a new droplet, then you can do a standard install and move as describe…

I have a test instance that is set in English. Updating these fields in the test instance works, which adds more credence to the hypothesis that something with translation is buggy.

Thanks for the pointer, it seems to be quite easy!

I have updated Discourse, can confirm the bug is gone. Thanks for the terrific work!

Certains paramètres ne sont pas sauvegardés

Soutien

Canapin (Coin-coin le Canapin) Juin 27, 2023, 3:50 6

Je peux reproduire le problème dans deux autres composants. C’est la même chose que Theme Translation fields not working - #2 by Canapin.

Sujet		Réponses	Vues
None of the settings are saving Support	6	416	Juillet 20, 2023
Settings revert back on their own Support unsupported-install	24	1634	Octobre 2, 2019
I cant save the settings in all theme components Support	2	499	Novembre 5, 2019
Custom User fields not saving Bug	19	2274	Octobre 5, 2017
Theme Translation fields not working Bug	3	591	Juillet 1, 2023

Certains paramètres ne sont pas sauvegardés

Sujets connexes