Wedge

Yeah, took me a minute of staring at it thinking "WTF is wrong with you?" but it does make sense in the end :)

These things happen, and on a site that's known to be running alpha software, it's somewhere between allowed and expected. We know full well we've only just deployed Wedge and that we saw many, many things we weren't expecting. That's cool, because it gives us the opportunity to test things in a way we never would have locally, and we've seen bugs emerge out of it that we can fix, so that we get a better result at the end of the day.

To be brutally honest, I actually think it's gone better than I expected it to go, but that just goes to show how strong the work that everyone who's contributed has put in, be it in code, or the importer, or just with their thoughts and suggestions.Part of me is disappointed, because I thought so too, but the practical part of me (which is larger) was well aware that things hadn't been battle hardened or testing under pressure and that things were going to go wrong. At least they're going wrong here where we can evaluate them properly.It's cool where it is for now. We can always reorganise it later.I still sense we're going to have private areas in the future too, if only to discuss things like security matters that shouldn't be discussed publicly, and if I'm really honest, I like having a bit of space where we can open ideas quietly to close friends without broadcasting plans openly. It's not that I don't trust people, it's that I've noticed that stuff in the less public areas has a higher signal:noise ratio and tends to have more specific feedback about changes and suggestions.

There's no hurry :)

It's more a case of people reporting stuff that's broken, as they see it. You and I both know it'll all get sorted out in the end, it's just going to take a little bit of time to make that all happen - but it will get sorted out. The trick is to not let it get on top of us, which is why I'm looking to organise this board - so that we can assess what's done vs what hasn't been done yet, so that we can focus our time on what needs doing.

Yes, there's a lot to do - but we'll get there :)

:)

This should be applied when the next rollout of patches occurs, as it's applied as rev 1484.

OK, I've fixed this locally and will push it into the repository on my next commit (since I want to fix a few other things first)

We're the same, some of the changes were made months and months ago ;)

Yes, we are aware of this.

Pretty URLs breaks report to moderator, issue warning was broken but fixed by me this morning - but I don't currently have FTP access, and I want to leave the message here for debugging purposes, in case it's specific to the pretty URL in this topic.

It's also interesting to note that the *only* defence we have currently is my custom CAPTCHA, and this is still the first spam post since the move 3 days ago, we're not even using custom questions here at the present time.

@Dragooon, it's also the little ! icon under the user's name.

I've never had any problems with post drafts, it was only PM drafts that were being sent instead of being saved. Hopefully that should no longer be a problem :)