Forums

Yes, it's limited by the database. You could change the message field to MEDIUMTEXT, and along with that either a constant in common.php or the check in post.php (I can't remember which one it is, sorry).

Indeed, that's probably the best thing to do.

The base URL is in the config table in the database, as was the case in 1.2. Set it manually and clear the cache files.

On that note, the upgrade script should probably take care of that.

1.4 isn't far off, beta 2 should appear one of these days. After that we'll provide support and bugfixes for 1.4, and seriously think 2.0 through before we start on anything.

Hmm, indeed, only in some places if I remember correctly. Never mind

Saying how things are under the hood will probably just stir up controversy, but anyway...

There is nobody in charge really. We have a discussion about most things, between the (active) developers and the team.
I haven't seen Connor around in a while. Some time ago I had some contact with him, promising he'd tell me how to use his release script. A bit later I wrote my own because he didn't send anything. I realise he could be very busy, so I'm not blaming anyone here.

The direction the project takes is still largely governed by FluxBB's goals, but I do admit I've put my foot down about a thing or two that smelled like feature creep in 1.4.

I don't see what's so hard about parsing the language files A very simple regex should be able to handle that (#$(.+?) \= "(.+?)"# or something).

Error supression using @ is also quite slow, if I remember correctly.

I'm not really a fan of adding any more features to 1.4 atm, especially when it comes to permissions etc.

As for the reports, it's a bit of a basic moderation log. But an option in the maintenance section to purge them might be nice.

Fixed in [1081].

And done in [1080].