Discourse just hangs on “Saving…” and never does anything. I have tried writing other posts and they work just fine. I ran ./launcher rebuild app and still experience the same problem. There are no errors (that I see) in the logs.
Nope… it’s been around for 6 months and has a lot of posts in it. For what it’s worth, it will post neither as the first post in a new topic nor as a reply to an existing topic, regardless of category.
I suspect you have some kind of client “antivirus” that is ham-handedly detecting this as an exploit and interrupting the HTTP connection. Have seen it before!
(Assuming as @riking said him and another have been able to post it on try.discourse.org just fine)
I can post the entire post successfully EXCEPT when I include the first two lines in the text document at the top. If the first two lines are included, then it fails to post. If I try to post just the first line, removing the period and everything after it, then I can post. So it has something to do with the period, carriage return on the first line, or space/carriage return on the second line. If I start with the “1. Press…” from line 3 and grab the rest of the text, it posts without a problem.
Here’s the editor, stuck in “Saving…” before trying to submit the post.
I’m not sure? I typed the post in the Discourse edit window; nothing fancy. It seems like the failure is happening client-side. What’s the best way to see what Ember is up to when I click to post or when it’s trying and failing to save the post mid-edit?
I cannot repro it there. However, posting it there does reveal another bug, which I’ll post in a different topic.
I’ve rebuilt the app again, cleared caches, done hard browser resets, and it the post still will not post to the Discourse I manage. Oh, well… I’ll just change the text. If you have any other thoughts about debugging, I’m happy to do them to see what’s going on.
Perhaps. Weird that it’s restricted to whatever is in the first two lines of that text. I’ll keep looking at it to try to figure out what’s happening and I’ll see what happens when I’m not on the VPN tomorrow.