Wedge

That suggests then that we might want to remove the body text in every case from PM notifications and just be done with it? Not even making it optional, allows for editing after sending - until it has been read, of course.

Plus that then gains the benefit by default of not having messages sent by return email to the admin...

I've never heard of MD5 being slow, neither SHA1.

Re first post: it's actually bad UI for those people who are using a desktop because it's a link that doesn't go anywhere and it actually feels broken.

Second post... if the top levels are clickable in the admin panel, where would they go? For some things, like Plugins, going to the first menu item is OK but for some things - like Configuration - going to the first item is actually probably more confusing.

I also need to check whether there's a performance impact when moving from a text to a mediumtext but I don't believe there is.

Should definitely hash it all the time, I'm just trying to figure out the best way to do this since there's already an MD5 hash in the filename as it is.

I'm thinking about this one again.

The grand plan is that attachments, avatars and media, these places all have write access anyway. Plugins, smileys, etc. won't have that access but will do it via the FTP passthrough (as discussed elsewhere) which means there won't be permissions issues, but also where we won't be using native file operations anyway.

Result is that there's very few places this can actually be done meaningfully, except perhaps as a change to the file cache (since the same flock processing should still be possible)

Is this still happening? I cannot reproduce it on my system, not even with different cache systems being used.