Forums

The guy probably wanted to have a personal life and the way FluxBB took up his time that wasn't possible so he had to choose.
Good for him that he chose to have a life and we can only be grateful for the patience and dedication he had in the past.

As far as I'm concerned, I don't see what the drama is. FluxBB is on a feature-freeze state so no added features, only bug solving.
For me it's usable right now, the only stuff we _really_ need is the markup and lang files, anything else can be done with extensions.
As long as one of the devs listens when someone explains why they need a hook, we're golden.

That message probably indicates that you are trying to do a SQL command with too few columns.
Check the number of values on the INSERT and the number of columns on the users table (use PHPMyadmin if it's easier for you).

I'm not aware of one right one but there should be later on since it's something useful and easy to do.

You want the "Navigation Icons" extension by Reines: http://fluxbb.org/forums/topic/336/exte … by-reines/

Funny enough, I'm finishing a extension using part if your code . All I need to do is add a option on the administration and user profile to disable it.

Herrrrr..... That was irony, right? Since I didn't see a smiley there I'm not sure.

Oooh, goodie. Does that mean I can publish my language files and start doing styles?

Oh, sure, it wasn't a criticism, I didn't mean to imply that it was finished, that's why I opened the topic on discussion and not on core requests and said "Maybe Paul already has plans for this but.....".
I will most likely do the same whenever I see something I believe could be improved on but not sure if the devs will go along with it or not.

It's just a way of throwing the idea out there and see if there are any objections (there could be a conflict with future plans for the core and therefore not doable without an extension) or if the rest of the people and the devs agree it's the way to go.

I'm a very easy going guy, most people haven't seen a single post from me but I have if not THE most altered punbb based forum, at least one of the most altered ones since I had to merge the torrentbits source with punbb and get something usable
I haven't posted the code since it's a massive change and I didn't document the steps to do it.
I plan on doing it as an extension for fluxbb 1.3 though and will most likely release it then.

I would assume that whenever the admin adds something to a "closed solution" like fluxbb where you don't need anything else to make it work, the admin is the one responsible for it.
Styles use style.php to generate the style, if you dowload a new style what assurances do you have (if you don't open the .php of course) that newstyle.php isn't doing something nasty behind your back?
The issue here is that the admin can't manually check the avatar image before he uploads it to the server like he can with the style or any other file.

Anyway, I think we´re getting sidetracked here, I see that the devs are open to including a solution for this, be it in the core be it in an official extension. I say go with it and disable avatar upload if GD not enabled and do a admin alert with information on why it's disabled and how to enable it even if it's only a link to the wiki or a forum thread.

Could we check for the presence of GD and if present and enabled, use the code above?
That way it wouldn't be a requirement since the avatar upload would still work as it does now.

<?php
if (extension_loaded('gd') && function_exists('gd_info')) {
    echo "It looks like GD is installed";
}
?>

If it's necessary to confirm that a specific function is available, we can always query GD itself:

<?php
echo "<pre>"; var_dump(gd_info()); echo "</pre>";
?>

I don't see the adition of this piece of code as bloating the core since it's a security mechanism that degrades with no issues, but if the devs think it shouldn't go on the core, we can always do an extension so it's not a big issue.

Oh, sure, this would be used for example where you have an annoying user that keeps refreshing a DB intensive page a couple times a second or when you have a  momentary influx of users, not when you have a true DOS.

Yep, the page would be something very simple with no DB query's or complex code. Will probably even have the option to send back just a temporary redirect to someplace that can handle the load.

Correct, like I said this is useful only on a VPS or dedicated server, not on shared hosting where you can't add rules to the firewall. The privileges issue is easily worked around by using sudoers with a rule like "APACHE_USER ALL=NOPASSWD:/usr/sbin/iptables".

The point of the last extension is to make your life easier if you (like me) purchased a VPS just to run your forum. Also, since I have the 403 and 404 pages redirected to customized, I was thinking of using them to ban the IP when I have a vulnerabilities scan (you know the type, where they scan if you have certain versions of phpmyadmin and so on). If someone tries to access http://myforumaddress/phpMyAdmin-2.2.6 I know that he's trying to go someplace he shouldn't and therefore I can ban him with extreme prejudice

I understand that it will probably be used by very few people, maybe even only me.

You can create a database if you connect to mySQL with a user that has permissions to create databases and do a sql query "create database DATABASE_NAME;"

For a bit more information see for example http://www.webdevelopersnotes.com/tutor … abase.php3 and http://www.php-mysql-tutorial.com/creat … th-php.php

Since I don't know how much you know of SMTP and servers, I'll try to dumb it down a bit

Let us assume your SMTP server is responsible for the domain sourcedomain.com and that you want to send mail to the domain targetdomain.com.

Are you sure that you are using a address FROM someone@sourcedomain.com and TO someone@targetdomain.com?

The relay access denied is usually used when you try to send FROM a email address for which the SMTP server is NOT responsible.

You CAN'T send a email FROM someone@anotherdomain.com if the SMTP server is only responsible for sourcedomain.com.

Just read this. Yep, like I said above, if the server doesn't support "open relay" (HUGE mistake leaving it like that, a spammers dream) what you write is correct.