Aha, it was in 1.3 we changed it to a constant.
2 2009-08-17 00:08:50
Re: Character count in posts? (5 replies, posted in General support (1.4))
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).
3 2009-08-14 12:14:40
Re: BMP not displaying as image in img tags (4 replies, posted in General support (1.2))
For one, the server is sending it as JPEG.
And why on earth would you use BMP?
4 2009-08-10 15:08:03
Re: Upgrade to 1.4 from 1.3 (9 replies, posted in General support (1.4))
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.
5 2009-08-10 12:34:43
Re: FluxBB 1.4-beta2 released (14 replies, posted in Announcements)
fluxbb-1.4-beta2 tag or changeset 1094.
6 2009-08-06 19:13:49
Re: Switching from fluxbb to another message board service (24 replies, posted in FluxBB discussion)
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.
7 2009-07-29 20:42:03
Re: Regarding the form submit disable thing (6 replies, posted in FluxBB discussion)
Hmm, indeed, only in some places if I remember correctly. Never mind 
8 2009-07-29 16:29:47
Re: Regarding the form submit disable thing (6 replies, posted in FluxBB discussion)
Well, actually, the CSRF token should already take care of it, it just needs to be caught with the proper message.
9 2009-07-29 11:22:08
Re: Switching from fluxbb to another message board service (24 replies, posted in FluxBB discussion)
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.
10 2009-07-22 13:12:21
Re: Change languages to none PHP files. (32 replies, posted in Feature requests)
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).
11 2009-07-21 19:50:39
Re: Cash logs, i made, i need to pull imgaward :) (24 replies, posted in General support (1.2))
So you actually managed to make two out of four fields that shouldn't be an int into an int, but not those that actually should be. Congratulations.
12 2009-07-21 00:50:24
Re: Cash logs, i made, i need to pull imgaward :) (24 replies, posted in General support (1.2))
Why on earth is everything there a text type?
A thousand DBAs just killed a puppy.
13 2009-07-21 00:49:10
Re: Updated to PHP 5.3.0 and I get Deprecated Problems (17 replies, posted in General support (1.2))
Error supression using @ is also quite slow, if I remember correctly.
14 2009-07-18 13:08:38
Re: Updated to PHP 5.3.0 and I get Deprecated Problems (17 replies, posted in General support (1.2))
We never claimed Flux to be compatible with PHP5.3, there have been a few big changes which would most likely result in us having to maintain two branches of the same version.
I haven't really been following PHP lately (5.3 was the last straw for me tbh, it's just pissing me off now), so I have no idea what the required changes would be. If someone feels like making a patch that could be nicely integrated into the current versions, feel free to post it.
16 2009-07-14 12:33:33
Re: cpu usage (4 replies, posted in General support (1.2))
Unless the site is running on a 486, there must be something else going on still. I just can't see any other possible way a stock FluxBB install generates that much CPU usage.
17 2009-07-13 13:55:40
Re: Discussion on 1.4 (44 replies, posted in Announcements)
And done in [1080].
18 2009-07-12 22:44:45
Re: Discussion on 1.4 (44 replies, posted in Announcements)
ridgerunner wrote:
That was an excellent read, thanks for that! I'll see about implementing and testing it tomorrow.
19 2009-07-12 13:09:59
Re: Discussion on 1.4 (44 replies, posted in Announcements)
ridgerunner wrote:
In that spirit, I'll be offering some positive contributions shortly...
Great, that's the way I like it 
20 2009-07-11 15:00:15
Re: Discussion on 1.4 (44 replies, posted in Announcements)
ridgerunner wrote:
elbekko wrote:... I'd like to bring part of this discussion to the community. ...
And yet when they respond, you simply disregard their opinion because they obviously don't know what they are talking about! I may be new to the Pun/Flux development community, but I am certainly not new to programming. I've been working as a software engineer since 1981 and have a LOT of experience that you might just want to cultivate - including expertise in regular expressions which (from looking at the code), you guys could use some help with. As I said before, the first 2 (non-trivial) regexs I looked at in detail in the 1.3 parser have errors. I found no such errors in the 1.2 code (of the ones I looked at - but those aren't perfect either).
But it sounds like you have already made up your minds.
Feel free to post improvements then, instead of just saying "no, this can't possbily be good."
As for personally attacking me, I really don't give a damn, but it doesn't really make your opinion any more valid (quite the opposite, in fact).
21 2009-07-11 12:48:27
Re: Discussion on 1.4 (44 replies, posted in Announcements)
ridgerunner wrote:
I vote no.
For starters its feature creep and you promised this would not happen. And besides, the 1.2 parser code is smaller, cleaner and much more readable than 1.3, particularly with regard to the implementation of regular expressions (e.g. Just take a look at the preparse_bbcode() function for comparison). The few regexes that I took a close look at in the 1.3 parser were poorly written at best. (This is one of the main reasons I abandoned using 1.3). Note that the 1.3 parser has twice the bloat (28KB vs 14KB) and yet is poorly commented.
The 1.2 code is superior IMHO. Its not broken, don't fix it!
Yet it isn't. For 1.3 we worked on making the parser faster, as it was the biggest slowdown in the whole code. We're now porting it to 1.4 (which is nearly done) to provide this speed boost. What you think of the code and what it actually is are very different things obviously.
And I'd hardly call it feature creep if you're replacing instead of adding.
22 2009-07-04 13:41:08
Re: Discussion on 1.4 (44 replies, posted in Announcements)
Yes, but as FSX said, there is also a slight issue with paragraphs that needs to be fixed. Still, the style changes would be very minor, and could probably be put in base.css so custom styles don't break.
23 2009-07-01 12:54:23
Re: Discussion on 1.4 (44 replies, posted in Announcements)
@Mpok:
Well, I don't see how a toolbar mod would break due to the inner workings of the parser changing. The BBCode won't change or anything, just how it is handled. Putting in the new parser is basically plug and play, and Paul has the code done already for a personal project.
Now, I can take a look at PunToolbar for you, but I have a feeling it won't break a thing. If it does, it's probably made in the wrong way
@sirena:
I wouldn't call it feature creep, it's just a few thoughts we want the opinion of the community on As I said, it should be basically plug and play, so no code other than the parser would change.
24 2009-06-30 17:38:29
Topic: Discussion on 1.4 (44 replies, posted in Announcements)
Right, since the next 1.4 release just might be close, us developers have been discussing a thing or two, and I'd like to bring part of this discussion to the community.
First up is the parser. We've been toying with the idea of implementing 1.3's parser in 1.4. It's cleaner, faster, and just overall better. The downside to this is that some minor style changes will need to be made, which may break user styles.
We'd really like your input on this 
25 2009-06-29 16:09:43
Re: help.php (5 replies, posted in Bug reports (1.4))
Because it isn't a smiley.