In Discourse v3.5.2, I’m encountering an issue when a user attempts to edit their signature under Account → Preferences → Profile. The user can “Enable Signature” and edit the “My Signature*”* text editor, and Discourse indicates that the changes have been saved. However, after refreshing the page, the data is not retained, as shown in the screenshot below.
AI-generated summary
Users are reporting that signature changes are not saving in Discourse v3.5.2, despite enabling signatures and editing the text field — changes disappear after refreshing the page. evenlo confirms the issue on their instance. However, j.jaffeux could not reproduce it and notes a fix was merged in September. Moin suggests the fix may not be included in the stable 3.5 branch because the plugin was pinned before the fix was merged. evenlo observes the plugin appears up to date in stable, implying the September fix may not have been backported. j.jaffeux confirms the plugin was pinned a few commits before the fix, explaining why it’s missing in v3.5.2. The issue appears to be a versioning mismatch between the plugin and Discourse stable branch.
I can confirm we are experiencing the same issue on our instance as well. Users are unable to save changes to their signatures in Discourse v3.5+
Looking forward to a resolution.
I just tried and I have no repro of this, it works for me.
I see we made a fix for this in september:
https://github.com/discourse/discourse-signatures/commit/675089accb6fa04843c9ee25942821be771d9199
Are you sure your plugin is up to date?
I think that fix was merged after the version of the plugin was pinned for 3.5 (stable) in the compatibility file. So, I think the plugin may be up to date for their version of Discourse.
It seems the plugin is up to date in its stable version. I suspect the fix released in September wasn’t included in the version we upgraded to.
Yes indeed the plugin has been pinned a few commits before:
https://github.com/discourse/discourse-signatures/commit/09488b45f4696e029ec245438fcab31abae60d85

