Mat Barrie

Best of luck in your new endeavours! Sometimes it’s time to move on and it’s just time to do it. Fingers crossed!

BLTYNR, it sounds like you're referring to "iMediaPro Radio" when you refer to the "free one with requests hooks". When iMediaPro was available, it wasn't free. It actually costed more than Anthony's, despite it being illegally rebranded Bouncy Radio. I wouldn't recommend using it, as you'd be liable to receive a warning from Anthony if you did. It also means your request hook from it might actually work without too many modifications, since it's the same product ;)

Again, do not want. It's an ACP link. It's not just yourself and your admins that use it, it's every IP.Board admin in the world. And no, we don't want yet another setting for whether the ACP link should open in a new window or the current one - it's hard enough finding anything now amongst the thousands of settings. Use your hook.

He means it's not your decision whether links open in a new window or not. It's the user's decision. The W3C seems to agree with this, since XHTML 1.0 and higher have explicitly removed pretty much any way of forcing a link to open in a new window. Since IPS likes IPB to validate against the HTML and CSS spec, they don't really like the "open in new window" thing. That said, there is a feature to enable links to open in a new window which uses a piece of javascript hackery, but personally I refuse to use any site that turns it on. Of course, on a complete tangent, I'm not sure whether he misunderstood you - I notice you said something about ACP links. Do you mean the "login to ACP" link in the black mod/admin bar at the top of the screen? I'm going to say I prefer it as is. If I click it, it's because I wanted to visit the ACP to the exclusion of the board. If I middle click it, then I wanted it in a new tab. If I control click it, I wanted it in a new window. If they set it to open in a new window, it actually removes options from the user/admin as they can no longer opt to open it in the current window. So that's a big "-1" from me to that suggestion.

Oh yeah, and the version of Minify you ship carks it quite horribly if you add any extra CSS files (check out Forcize skins sometime - they actually require you to upgrade Minify when installing any of their skins!)

Since so few people actually use them, I don't agree with shoving it back in again after they shoved it to the side due to lack of use. But, if you want to add it back yourself, go read http://community.invisionpower.com/resources/articles.html?record=449

You appear to have been upgraded to 3.0.5. I can virtually guarantee that if IPS upgraded you, they overwrote the chat files with the out of the box ones that support only ParaChat and AddonChat. Reinstall it.

That extra fee is an additional 100% Jaggi. Not something to scoff at. However if the OP is making money off their forum, and losing money when it's down, they should seriously consider it.

No. No it wouldn't. Remember, all BBCode is custom BBCode, so none of them are treated in any special fashion by the parser. What you're suggesting would require the post parser specifically look for media tags, which might fail if you happen to rename them or something, and parse it differently. That's bad.

Not really. You know how we've already got "don't parse other BBCode inside of this BBCode"? Just add an extra one, "don't parse this BBCode inside of other BBCode", because to be honest you probably don't want a video parsing inside of anything else.

Well, actually, that means that this is the first IPS application you've had trouble with. IP.Shoutbox is a community project. This means IPS' only involvement is lending special support to the developers, project hosting, and their name. It's not something that Brandon or Matt spend 8 hours a day working on.

Well they do have to go through QA... unless you want buggy software?

Enkidu: Presumably they mean they've called phone support three times. If I'm not mistaken, hosted customers do have phone support for critical issues. They're probably just not logged into the forums with the same email/password as the client area. CHMB; if you go into the client area and you don't see the email you sent them there as a ticket in the "Your Tickets" area, they don't have an open ticket in which case you'd need to resubmit it. Something that often catches people out (as stoo mentioned) is that after you click "Submit" on the ticket screen, you then have to scroll to the bottom and click submit again as it offers KB articles before it lets you submit your ticket.

Nah. I don't really click minus much. I don't really click plus much either, but meh.

No no, that's the only one I disagreed with. The bug with the status text is minor and not really annoying, same with the "please bear with us if you see display difficulties in our 2 year old site". But categorisation could do with a bit of an overhaul. The dashboard idea is definitely something I could get behind too - there's way too many clicks to most things, so it'd be handy to log in and go "oh, I need to renew blog. and my ticket has a reply".