Forums

Unfortunately no one can be told what FluxBB is - you have to see it for yourself.

You are not logged in.

#2 Re: General support (1.4 / 1.5) » this guys says fluxbb is insecure » 2012-02-28 00:34:09

FSX

PHP's trim behaves exactly the same on my installation. I think the problem is not on php-utf8's code.

#3 Re: General support (1.4 / 1.5) » How to protect the file config.php » 2012-02-08 23:35:11

FSX

Maybe it should be possible to put the configuration file outside of the web directory?

#5 Re: Core development » 2.0 Coding Conventions » 2011-12-05 10:11:20

FSX

We're already going to use namespaces in php-utf8 so why not use that in FluxBB too and keep class names as short as possible and not use underscores in them (you don't need prefixes with namespaces). And what about keeping namespace names lowercase? It's easier to type.

I agree with method names. It's standard now, but I actually prefer names with underscores. wink

Braces for classes and functions should be on their own line. Like this:

class Stuff
{
    public function bleep()
    {
         // noop
    }
}

And I would go for tabs. I always use those.

#6 Re: Core development » OOP version of the UTF-8 API » 2011-10-31 15:14:06

FSX

I guess everyone agrees? I'll start with this in a development branch.

#7 Re: Core development » OOP version of the UTF-8 API » 2011-10-25 08:31:15

FSX

Loading everything at once is not a good idea. You don't all of the functions of the library so that would cause a lot of overhead. Look at the list of functions here: http://php-utf8.61924.nl/documentation.html

The core functions are loaded by default (see list for core functions). And maybe trim too, since that one is also used often. The others are not used that often.

#8 Core development » OOP version of the UTF-8 API » 2011-10-24 21:54:42

FSX
Replies: 5

This ticket requests an OOP version of the UTF-8 API. And as you might or might not know: FluxBB uses php-utf8. Which I maintain.

The API would look like this:

Utf8::strlen('somestring');

strlen can be any function that exists in the php-utf8 library. Functions are lazily loaded when they're needed and then cached. This with the help of __callStatic and anonymous functions. PHP 5.3 is needed for this. Can't see why we should use 5.2 anymore.

Here is a very simple draft implementation just to show how it work:

<?php


class Utf8
{
    private static $cache = array();

    public static function __callStatic($name, $arguments) {
        if (!isset(self::$cache[$name])) {
            self::$cache[$name] = require $name.'.php';
        }

        return call_user_func_array(self::$cache[$name], $arguments);
    }
}


var_dump(Utf8::rot13('abc'));

rot13.php

<?php

return function ($somestring) {
    return str_rot13($somestring);
};

The concept is pretty simple. This way you don't need to put the whole library in one class (which is stupid, because you won't use 90% of it most of the time).

Opinions, suggestions and other stuff is welcome.

If you have issues with php-utf8, report it at: https://github.com/FSX/php-utf8

Thanks.

#9 Re: Core development » 2.0: Translation system (pull request) » 2011-09-19 14:51:07

FSX

*crawls out of the ground* Hi.

1. A shorthand (_) is the standard when using Gettext.

2. I don't know what we decided neither. But I would go with key-based, becuase you won't end up with huge strings in your code and it would look a bit cleaner that way.

// TODO: How could we automatically regenerate these cache files when necessary? 
(E.g. imagine the default language files being replaced during a new release, the custom 
translations haven't caught up yet. How to handle that? etc.)

How about using some kind of version number or checksum for each language pack? The author gives a version numberm to his/her pack and is updated something is changed. The language file loader notices that because the cache file (or something in the DB maybe, dunno) has a different number and then cleans the cache.

#10 Re: Core development » 2.0 DB: Sanitize table names etc.? » 2011-09-15 15:55:32

FSX

It depends on where database tables come from. I would not sanitize them all the time.

#12 Re: General support (1.4 / 1.5) » how do you send 10000+ emails to members? » 2011-08-14 10:22:37

FSX

Swiftmailer can sent batches of emails with a timeout in between. I used it at work to send emails to 600-800 people. I don't know how it behaves with 10,000 emails though.

#13 Announcements » FluxBB 1.4.6 released » 2011-08-12 17:58:50

FSX
Replies: 7
Today, we release FluxBB 1.4.6!

The last release was some months ago and since then we've fixed 49 tickets!

And a lot more.

As usual, downloads can be found on the download page.
Changed files and patches can be obtained on the upgrade page.

Updating to FluxBB 1.4.6 will still work if you use any prior version of FluxBB and even from PunBB 1.2/1.3.
As always, please remember to do a backup of both your files and database!

This will be the last big release of the 1.4 branch and we'll only provivde bug fix releases from now on. As of now we're going to focus on 2.0. On a side note, FluxBB 1.2.24 has also been released.

If you have any questions, don't be afraid to ask.

#14 Re: Feature requests » Post Caching System that Intelligently Reloads when Necessary » 2011-08-12 07:47:14

FSX

I don't think you'll have any problems. Turn on PHP APC (PHP opcode caching) and it'll get a bit faster.

#15 Re: Feature requests » Post Caching System that Intelligently Reloads when Necessary » 2011-08-11 22:17:31

FSX

Would be possible if the parser parses BBcode in 2 passes. First pass will parse BBcode that'll never change and the second pass will parse BBcode that could be different for each user. Then you can cache the first parsing part.

#16 Re: Feature requests » User ID system - IP based » 2011-08-07 11:24:11

FSX

You mean the imageboards? If you want FluxBB to behave the same way you can make a DB table for anonymous users and link that to the guest posting code. Not too hard I think.

FluxBB is not made for this and most of the functionality is made for registered users. Subscribing to topic/posts, userlist, etc.

#17 Re: General support (1.4 / 1.5) » 503 error when posting links » 2011-08-05 13:40:37

FSX

It is not similar. The person there has a 404 error, which mean a page wasn't found.

You have a 503 error, which means there went something wrong on the server. I'm not sure what's wrong. Maybe you can ask your host if they can do something, because sometimes it's the host's fault.

#18 Re: Feature requests » User ID system - IP based » 2011-08-05 10:15:48

FSX

I don't really get what you want to do. Track anonymous user with their IP?

IP addresses can be changed easily. By using proxies for example.

#19 Re: General support (1.4 / 1.5) » 503 error when posting links » 2011-08-05 10:11:43

FSX

Can you check your error log if there's anything suspicious?

#21 Re: FluxBB discussion » Where has PRIVACY gone? » 2011-07-07 17:58:33

FSX

I don't see why that's not possible.

#22 Re: FluxBB discussion » Microformats? » 2011-05-19 07:37:00

FSX

Can you give a good reason for this? Does it have any use in a forum?

#23 Re: Core development » FluxBB Hackathon Weekend » 2011-05-09 16:58:15

FSX

*Throws bricks at Smurf*

Ok.

I assume you can't to do this over IRC? Would be really awesome if we could meet somewhere and do the coding there. Not sure if people live too far away for this.

#24 Re: Core development » FluxBB Hackathon Weekend » 2011-05-08 08:05:58

FSX
Garciat wrote:

Sounds fun. Rewrite FluxBB in nodeJS?

Maybe even better! ;D

#25 Re: Core development » FluxBB Hackathon Weekend » 2011-05-03 20:21:44

FSX

Sounds fun. Rewrite FluxBB in Python?

Board footer

Powered by FluxBB 1.5.0