Forums

No lie you said you weren`t sure if it was implemented and if it was it should be tested. So I tried it.

Right to get the upgrade to run you need to change FORUM to PUN in config.php. The upgrade completes successfully but your no longer able to login, wrong username/password message is given.

Hope that helps.

I wasn`t singleing you out Bert. I`m just sick of hearing about the past and what went wrong. Those who know, know and those who are new don`t really need to wade through thread after thread of it. It`s better of in the past and kept there so energies can be wholely put into the future. Is all.

Of course talk about what you like, this is just my opinion. No need to take it personally.

Whatever has happened I don`t think it`s good to keep dragging it up, leave it in the past and lets move forward. Which is what the majority is doing already, I`m trying to anyway.

Yeah but reading the suport thread it`s not maintained and has bugs. I`m not aware of any others available.

Reading Koos`s reply again though maybe sphinx would be better.

I meant there is obviously a benefit but maybe only to the big beasts, which FluxBB is not...

If your on shared hosting qie their idea of high cpu usage may not actually be that high, it`s just your using more than they`d like you to be. Like the others have said you need to find out more details.

Regarding the op, IPB stores the parsed post, users still have options on what`s displayed and it doesn`t seem slow. Don`t know how they deal with it but it may be worth looking into.

Thanks Reines for the heads up, thanks Smartys for your work on 1.4 and thanks to the whole team for your ongoing efforts.

To the future, cheers.

ignor

I`ll try to explain myself better in future, I think there has been some confusion here but hopefully I can clear it up here.

My origional post was just to point out that linking to an uncompressed version is a good idea to keep it useable for everyone, not just the origional file holder.

I`m not disputing the fact that manually compressing CSS can significantly reduce the size, that`s the whole point of doing it in the first place. I`m saying that it`s not worth the effort as the only time manual compression offers a worthy benifit is when the server doesn`t do any compressing (not that often).

Of course every little helps but if the server is compressing it already then the gain is so little it`s not really worth the effort.

MattF, I was refering to the benefits of compressing twice (I presume Connor was too) and not the potential space saving, that is obvious, at least for me.

For the few that browse without cache it`s only of benefit if the server isn`t compressing them.

You could heavily compress the CSS but leave a comment at the top with a link to the uncompressed version. I`ve done that in the past.

Obviously you wouldn`t want to do it untill your happy with the CSS because constantly compressing it can get annoying.