Some settings aren't saving

Support
1

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’t saved). I looked this topic, but I don’t use Cloudflare. And the issue only happens for some settings.

I did some testing, apparently only settings with a textarea aren’t saved. Others are properly saved.

Any idea what could cause this odd issue?

Thanks,
Olivier

2 Likes
2

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?

1 Like
3

My guess would be some browser extension.

4

Sure! Here is an example:

Screenshot 2023-06-27 at 17.37.46@2x
Screenshot 2023-06-27 at 17.37.46@2x1212×252 6.36 KB

Another example:

Screenshot 2023-06-27 at 17.39.53@2x
Screenshot 2023-06-27 at 17.39.53@2x1224×414 16.9 KB

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 don’t think it’s related to a browser extension (as @pfaffman suggested).

2 Likes
5

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!

6

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

1 Like
9

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 described in Move your Discourse Instance to a Different Server.

2 Likes
10

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.

11

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

12

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.

4 Likes
13

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

2 Likes
14

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.