$12256 / $11500
At time of writing, I've made attempts to save changes to https://opengameart.org/node/51101/edit using Midori, Uzbl, and Firefox-esr.
I can and will provide more info later, but for now the trouble seems to be something on the OGA end of things rather than with me. Both Midori and Uzbl use Webkit2, but if Firefox, which I use sparingly as possible, also has trouble, then...
Anybody else having trouble?
This website's content is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
Works just fine for me. I was able to edit it without issue using chrome. (see revision history) I did get a warning about 'tags cannot be blank' though, so I added a few just to see if it would work. The tags were (originally?) blank and have since become a required field.
--Medicine StormYep, I see that. Thanks.
I've made more recent attempts, including one with Midori identifying as Chrome. Might it be something with my IP address being in a range which is blocked? An administrator could look to see if such is the case; anyways, because it seems that I am the only one having trouble, it is not very important.
What are the symptoms you're experiencing? It may have nothing to do with browser or IP. (if your IP was blocked you wouldn't be able to post here, either)
--Medicine StormI was also unable to edit any posts here, with the same results as when I attempted to edit the page for the audio files, so I'll include the information, which I promised, in this new comment:
I'm using a Debian installation of "midori"="0.5.11-ds1-2~bpo8+1", "uzbl"="0.0.0~git.20120514-1.1", and "firefox-esr"="60.8.0esr-1~deb8u1".
When I click the little “Save” link at the bottom, my browser receives a 500 error code — a 500, not a 5xx, to be clear, but which anyways isn't very specific.
Previously, I also had the same trouble posting a reply to the latest comment, though now it obviously went through.
I was finally able to edit the thing. I suspect that it was coughing at my use of either ASCII 0x27, rather than “'”, or ASCII 0x22 rather than “"”.
Seems that the “rich-text” editor is not automatically converting one or both of those … whichever is causing the trouble … for any of my browsers.
I hope this is helpful to you and any other admins!
It is helpful. The ASCII character thing is a known issue. If your browser is converting (or you're copy-pasting from a word-processor that converts) characters to non-keyboard versions (Like fancy curved quotes and apostrophies, like you mentioned. Em dash is another one it chokes on) it will give a blank white screen with error 500.
The rich-text box is more of a lower-middle-class-text box. Not as rich as I'd like.
--Medicine Storm