Wedge

I'd argue that generally there's no such thing as a good time for anything, just a collection of variably less bad times, but in this case I'll make an exception; there's always a good time to give up smoking, and it's always 'today' because it'll be better for you in the long run.

Add an id_topic to the poll table (with key as suggested) and repurpose the existing id_poll field as a tinyint to say whether or not there is a poll attached to the current topic. It's the fastest way of dealing with this.I've never verified this, but my reading of the rather-vague documentation in MySQL suggests that when using UTF-8 that's actually storing UTF-8 characters, you store them based on the actual number of characters, not the number of bytes. (Certainly it makes reference to CHAR(10) fields in UTF-8 tables taking 30 bytes, as it has to account for 3 bytes per character) This suggests we'd still end up with 255 characters' worth of question even when using multibyte characters, but this needs verification to be sure.There's a world of difference between 'could really benefit' and 'might be useful', and actually the only ones that stand out in my head as being useful are things like the topic subject. I'm not sure that most fields which are varchar(255) would actually benefit.Interesting idea, though I'm not worried about it at present, that's what beta is for, right? :P

The odds of attachments being modified is slim, but should not be ruled out. It's one of those things that is a necessary risk.index.php will when it's called in a DirectoryIndex capacity (i.e. /cache/ or /cache/data/ only) but actual .php files otherwise should be neutered by this in /cache/.htaccess:

But it's not protected on IIS or nginx.That's because any requests made are caught by the 404 handler. That's still not a risk in itself though.Hmm, that's a valid vector - but I was thinking more of the PHP side, wherein everything in /cache/data is rebuilt periodically.

Yes, I was talking SFTP in the truest sense of SSH-FTP (as opposed to FTPS), and it's a *much* more sane approach (none of this virtual path crap), but you're right, most shared hosts don't offer it, ironically they'd be the ones who would best benefit from having it available.

The whole fundamental problem that is attempting to be solved here is how to, essentially, secure files that are intended to be executed within something that's conceptually the sandbox of user permissions without having to have them owned by the webserver and without having to have them worry about umasks or anything else; if it is conceptually the same as uploading via FTP it will inherit your account and so on - this is primarily FOR shared hosts.

Eh, I've gone back over the FTP class in SMF/Wedge, and I think I'm going to end up doing the same thing, the whole shebang manually, because I can't rely on any of the easier methods. Though I'm not quite sure whether I should attempt to use IPv4 first and only then fail over to IPv6 if that doesn't work, or attempt IPv6 first and try and catch what happens after.I stand corrected as far as GoDaddy and DreamHost are concerned, having just double checked that (since I couldn't believe they'd use a proper protocol for all standard customers)

I guess I'm just very sceptical as far as these things are concerned, simply because I've seen too many people burned in the past.

The problem then to deal with is how to get people to understand about SFTP credentials, because I doubt most people have heard of it, and just for fun, there's also FTPS which is a very different thing all together.

I'd also note that it does rule out 000webhosting.com who only offers a single FTP account for the free service, which is what most of their forum customers tend to use.

Aside from the fact I don't see how you get from that bbcode to the layout shown, it isn't that hard to add to Wedge but definitely not as core.

As long as it lets me style the bars like I'm suggesting, it's all good.

Sure it's already recorded, it just needs displaying.

Regarding vB, it is similar to SMF/Wedge, just you have different coloured bars, one bar red, one purple, one blue etc. All I'm saying is to add classes to differentiate the bars, for style purposes.