Read my post above yours. I made it clearer since both of you didn't understand.

Ah, well then this isn't the right place to be asking for that. You should submit a request to ourl.ca/request

Oh, I thought that was just a heading for Recent unread or Recent replies.

If you click on the main part that opens the sub menu, it takes you to recent posts. The sub menu is for those pages.

Quote from: Hayleia on March 23, 2014, 03:51:50 am

Indeed, it is a lot better like that
The only differences with the old feature are:

• clicking on the title of the topic in that list opens the topic at its beginning instead of opening it at the last post (what opens at the last post is the button on the right)
• it only lists 20 posts

But that's already great, don't worry, I am not complaining, just listing differences :)

Actually if you check carefully:

*1: To get around that, you can click one of the page numbers at the bottom and if, for example, you see 1-2-3...98-99-100, clicking the ... will expand the page list. Also, in the last post column, there's a small icon leading to the latest post.
*2: I think 20 depends of your forum settings, because I have it set to 50 in my account settings. Also, for me there are 296 pages of topics (going all the way back to 2005), so in fact the New posts list now lists about 15000 topics :P (or more if you're admin)

I have 862 pages >.>

On the topic of Axe documentation...

We used to have an Axe wiki, where this kind of stuff (tutorials and “better” documentation) can be found. Mediawiki needed to be updated 24/7 though, and things got messy so fast (spambot fiesta!) that it was eventually shut down.

(See: http://www.omnimaga.org/news/axe-parser-wiki-opens-its-doors/msg220368/#msg220368)

I don’t think we’ll ever put up another wiki again (unless it’s some other wiki software, NOT Mediawiki). But if you’re really interested in improving documentation, you can either modify the current one (that one HTML file), or get your hands messy by creating another one!

Sphinx (http://sphinx-doc.org/) is a documentation format that creates pretty documentation from simple markup. LOTS of projects use it, and although it is a little overkill for a project like Axe, you can certainly use it to provide meatier details about Axe, including tutorials and the likes. I’d love to see a https://axe.readthedocs.org/ one day!

EDIT: Looks like thep ninja'd me!

Nothing wrong with mediawiki, you just have to secure it properly. It's what the largest wiki in the world uses after all (Wikipedia).

They are shrouded in a cloud of possibilities.  Which are endless, but what I think is a good example is needed for each one with all possible arguments.
And the arguments could be colorized to make sence of what is required for the command to work and whats not. Some commands leand themselves to this in the descriptions but some do not. One such example is pxl-on and then you have Bitmap which gives you the options but doesnt tell you how to make bmp in the option.

bmp files are pretty standard. http://en.wikipedia.org/wiki/BMP_file_format I'd assume that it's a sequential piece of data in which bits with a value of 1 turns the pixel on and 0 off.

It does reconnect. I killed the bot earlier and hand it restart (It automatically restarts 30 seconds after any bot crash (That cooldown should be less IMO)).

it should in theory - if every single thread dies

Err.... so that's what is causing all the connections... You should change that up so that it only uses one mysql connection and the thread with that doesn't die

Seems like two links are still broken on that post.

Seems to actually be a problem with ourl.ca causing a redirection loop. I'll fix that up.

Incrementing everything by 100000 to prevent overlaps then remapping old ID links to new ones would have been the ideal scenario for other sites, but the debate is closed by now since what's done is done.

You keep saying that, but in all honesty, that would cause all sorts of problems down the road. Out of all the solutions this one is the one that causes less impact overall in the future. All the other "solutions" are just bandaids that temporarily fix the problem. If I've learned anything as a professional web developer, temporary solutions are never the best option. It's better to spend the money now to solve something, even if it causes a few temporary issues that can easily be resolved then to put in a bandaid that will cost more to fix in the long run.

EDIT: FYI - I literally am a professional web developer. It is literally my job.