WeepingLiberty, did you click the edit button, or did you use backspace (or equivalent) to go back? That system with helpful errors looks wonderful... hmm... just got an idea... would it be possible to program it to so that uncooperative BBcodes (i.e. ones not written correctly) are marked out somehow? Say a shiny red (or some other color)? (in the submitted/previewed post?

> WeepingLiberty, did you click the edit button, or did you use backspace (or equivalent) to go back? > > That system with helpful errors looks wonderful... > hmm... just got an idea... would it be possible to program it to so that uncooperative BBcodes (i.e. ones not written correctly) are marked out somehow? Say a shiny red (or some other color)? (in the submitted/previewed post? Yes, I clicked the edit button on a posted response, made my changes and then clicked the save button. I then remembered that I forgot something so I clicked the edit button again, only to have the previous edit disappear on me when I did so. I originally thought that it might just have been that I clicked it without refreshing the page or leaving and coming back... However a little bit ago I returned just to test it... Every time I hit the edit button on a post I've already edited, my changes from before are erased. I have no idea why.

Hey WeepingLiberty, You can help verify your issue by looking at the debug output in your browser's console. - When you click "Edit", your browser makes a request to `/posts/<POST_ID>/raw` to fetch the current text. It then prints out the result to the console. - When you click "Save" on the edit-form, your browser sends the update to the server and receives the updated-post. It then prints out the updated-post to the console. To illustrate, here's my browser console while updating the text of [this post](http://www.roleplayerguild.com/topics/75355/posts/ooc#post-2332647) from "test3" to "test4":  - When I clicked "Edit", it made that GET request and then print out "test3". - When I changed the text and clicked "Save", you can see that it made the PUT request and printed out the updated post with: text: "test4" There's definitely an issue if the updated-post readout comes back with the same pre-edit text.

> hmm... just got an idea... would it be possible to program it to so that uncooperative BBcodes (i.e. ones not written correctly) are marked out somehow? Say a shiny red (or some other color)? (in the submitted/previewed post? Hmm, I could see that being useful when you're dealing with a lot of BBCode, like when building a [table] by hand: [table] [row] [cell]foo[/cell] [cell]bar[/cell] [cell]qux[/cell] [/row] [row] [cell]1[/cell] [cell]3[/cell] [cell]5[/clel] [/row] [row] [cell]2[/cell] [cell]4[/cell] [cell]6[/cell] [/row] [table] (See the typo?) Though that kind of polish tends to be pretty expensive in terms of opportunity cost.

it did take a bit of searching to find the clel indeed. not sure whether it would be easier to program it to show up post-submission, in preview, as a popup when pressing submit, or even in the typing window itself as you write. that's how we view our role... We come up with lofty ideas of questionable value, the people who know the stuff shoot them down with heavy anti-air batteries when they're not workable.

> it did take a bit of searching to find the clel indeed. > > not sure whether it would be easier to program it to show up post-submission, in preview, as a popup when pressing submit, or even in the typing window itself as you write. > > that's how we view our role... We come up with lofty ideas of questionable value, the people who know the stuff shoot them down with heavy anti-air batteries when they're not workable. At least Mahz has the benefit of being in charge of the whole shebang, and can afford to do that. If this was a job, and we were the client, the developer would be hard pressed to explain why such a thing was not in the client's best interest (Customer is always right, and all that jazz).

In the older version, whenever you started a new RP the first post was and OOC. Now it's an IC. Why the change?

> In the older version, whenever you started a new RP the first post was and OOC. Now it's an IC. Why the change? I fixed that days ago. New RPs should put the first post under OOC. If they still start as IC, either Mahz hasn't pushed the changes onto the site yet, or something very odd is happening.

This server is days behind the tip of the codebase. I was hoping to fit BBCode into the release. If it looks like I won't be able to push BBCode til the weekend, then I'll push a release tonight with assorted fixes.

we suspect that people would be very happy even with the BBcodes done so far for the next push, mahz. Then the lovely gems of the extra ones you've not yet finished with can be a later bonus. The formatting of longer posts will be far less of a pain with even that.

Can't access the site on my desktop.

> Can't access the site on my desktop. It it fixed now? Possibly related to <http://www.roleplayerguild.com/topics/75462/posts/ooc>.

Quick question on the dev guild, mahz... Is the post counter there disabled? It looks stuck on 360 posts.

Any idea how to make hiders or strikethrough fonts?

Both of those work on the dev guild, BingTheWing. They'll be implemented with the BBcode upgrade. Oh, and mahz... The thingamajig counting all posts on the guild is static, not updating with new posts.

This site refuses to load altogether on my main computer, even though it was working fine 2 days ago. What happened? Just tried it on IE, and now the site will load (IE only) but there is no option to log in.

Try to clear browser caches. can't guarantee it'll help, but it might. If that doesn't work, wait for Mahz to offer help. Or someone else, of course.

That was the first thing I tried. Didn't help.

Nothing to see here. Move along. 

Fixed now? I had tried to force HTTP->HTTPS (secure) connections through <https://www.cloudflare.com/>, but it was just not working for some people, so I shut it all off. I'll have to enable secure connections the right way.