Not possible to edit wiki articles with system user

Product Support

AI-generated summary

suteroun reported that editing wiki article content with the system user in Discourse 3.2.0.beta5-dev fails with a “Error 422” and a console error indicating invalid JSON. While headings can be edited and new articles can be created and later edited by the system user, existing content edits are blocked. JammyDodger suggested this may relate to group-allowed settings interfering with the system user, and recommended updating the site via the /upgrade page as a potential fix. suteroun confirmed the issue was resolved after updating.

1

I wanted to make changes to a wiki with the system user, but I can only change headings, not content. Here I get an error message in the console and in the browser “Error 422”. I could already rule out that it is due to the new content, as I can save it with a normal user. It is also not the article itself, others cannot be saved either.

What works, however, is to create a new article with the system user, and it is then possible to edit it afterwards.

Discourse 3.2.0.beta5-dev

error in console:

ajax-error.js:35 SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
    at Function.parse [as parseJSON] (<anonymous>)
    at l (ajax-error.js:31:20)
    at c (ajax-error.js:74:10)
    at ajax-error.js:83:11
    at _ (rsvp.js:434:1)
    at y (rsvp.js:420:1)
    at m (rsvp.js:369:1)
    at invoke (backburner.js.js:282:1)
    at h.flush (backburner.js.js:197:1)
    at p.flush (backburner.js.js:358:1)
    at B._end (backburner.js.js:798:1)
    at B.end (backburner.js.js:589:1)
    at B._run (backburner.js.js:842:1)
    at B.run (backburner.js.js:624:1)
    at e.run (index.js:75:1)
    at t.error (ajax.js:148:7)
    at l (jquery.js:3223:31)
    at Object.fireWith [as rejectWith] (jquery.js:3353:7)
    at T (jquery.js:9629:14)
    at XMLHttpRequest.<anonymous> (jquery.js:9888:9)
l @ ajax-error.js:35
c @ ajax-error.js:74
(anonymous) @ ajax-error.js:83
_ @ rsvp.js:434
y @ rsvp.js:420
m @ rsvp.js:369
invoke @ backburner.js.js:282
flush @ backburner.js.js:197
flush @ backburner.js.js:358
_end @ backburner.js.js:798
end @ backburner.js.js:589
_run @ backburner.js.js:842
run @ backburner.js.js:624
e.run @ index.js:75
t.error @ ajax.js:148
l @ jquery.js:3223
fireWith @ jquery.js:3353
T @ jquery.js:9629
(anonymous) @ jquery.js:9888
load (async)
send @ jquery.js:9907
ajax @ jquery.js:9521
f @ ajax.js:173
(anonymous) @ rsvp.js:457
k @ rsvp.js:913
k @ ajax.js:192
update @ rest.js:119
update @ store.js:197
update @ rest.js:30
save @ rest.js:89
(anonymous) @ composer.js:1011
_ @ rsvp.js:434
y @ rsvp.js:420
invoke @ backburner.js.js:282
flush @ backburner.js.js:197
flush @ backburner.js.js:358
_end @ backburner.js.js:798
end @ backburner.js.js:589
_run @ backburner.js.js:842
run @ backburner.js.js:624
e.run @ index.js:75
t.success @ ajax.js:118
l @ jquery.js:3223
fireWith @ jquery.js:3353
T @ jquery.js:9627
(anonymous) @ jquery.js:9888
load (async)
send @ jquery.js:9907
ajax @ jquery.js:9521
f @ ajax.js:173
(anonymous) @ rsvp.js:457
k @ rsvp.js:913
k @ ajax.js:192
update @ topic.js:722
(anonymous) @ composer.js:983
_ @ rsvp.js:434
(anonymous) @ rsvp.js:489
invoke @ backburner.js.js:282
flush @ backburner.js.js:197
flush @ backburner.js.js:358
_end @ backburner.js.js:798
B._boundAutorunEnd @ backburner.js.js:523
Promise.then (async)
n @ backburner.js.js:26
flush @ index.js:40
_scheduleAutorun @ backburner.js.js:964
_ensureInstance @ backburner.js.js:955
ensureInstance @ backburner.js.js:767
scheduleRevalidate @ index.js:3337
dirtyTag @ validator.js:368
T @ validator.js:440
M @ index.js:485
D @ index.js:521
Ae @ index.js:1796
Ce @ index.js:1772
set @ observable.js:23
save @ composer.js:1022
saveAction @ composer.js:822
_triggerAction @ d-button.js:115
click @ d-button.js:87
2

Ah, this could be another one where the new group-allowed settings aren’t playing nice with the system user. I think there has been a temporary fix put in place while a firmer solution is being worked on. Could you update your site from your /upgrade page and see if you still get the same issues?

3

It works for me. Thank you.