It sends all the invisible code before the webpage that your browser requires to understand the language, etc.
In theory commenting it out is very bad but for some reason with bb-gzip it’s being triggered twice which should not happen and is bad. The fix I gave you is a lazy workaround for now until I have time to address it properly one day (and might need a completely different fix with bbPress 1.0.1 etc)
Michael3185, something in your setup is causing bb_send_headers to be sent twice.
Try commenting out line 10 in super-search-init.php
// bb_send_headers();
One day we’ll start a install4free like wordpress but until then,
if they just want a basic install, start giving out this free service:
http://www.simplescripts.com/script_details/script:bbPress
supposedly works on most major hosts including:
* Bluehost
* Hostmonster
* Fastdomain
* LunarPages
* HostGator
* SiteGround
* GoDaddy
* WebHostingPad
* LiquidWeb
* StartLogic
* iPowerWeb
* Dot5Hosting
* MidPhase
* 1and1
It’s kind of hilarious they have blocked ftp yet template upload and edits via php can completely open your system to security vulnerabilites. We’re still trying to figure it out but I have a strong suspicion of the WordPress theme-editor.php causing a large number of WordPress sites to get compromised recently:
babloo/blyat spammer attack on many WordPress blogs
The day bbPress gets a built in theme-editor, delete the file immediately.
Also delete xmlrpc.php unless you absolutely need trackbacks/pings.
And never, ever, use a dictionary word within a WordPress password as there’s no limit on login attempts.
I predicted this problem at the start of April (and they argued that I was wrong).
http://ckon.wordpress.com/2009/04/03/wordpress-28-might-break-login-compatibility-again/
WP developers simply do not give a darn anymore about backwards compatibility, they just want to do whatever they want to do. Personally I’m getting really tired of their attitude.
Caching will help for non-members, especially considering that a more popular site has a few dozen bots crawling around it at any given time. But yes, it will have to generate a new file for each page.
However even without wp-super-cache it’s possible to cache parts of pages for all members, especially worthwhile on parts that use a whole bunch of CPU cycles to generate each time.
I wrote some code awhile back to cache the tag clouds, since they are not filtered by logged-in/out and remain static until a tag is added or deleted. The tag cloud took an average of 10-20 ms out of 120 ms to generate on the front page so the savings were worthwhile.
It’s not increased caching, it’s just reducing queries closer to what 0.9 does.
1.0 RC3 is still slower than 0.9
Doesn’t the timezone support require php 5?
If so, probably should be mentioned since half of bbPress sites are still on php 4.
You can get a 25% speed boost or more by running 0.9 instead of 1.0 depending on how many simultaneous connections you are serving.
1.0 uses 50% more code and several more queries per page when generating the same content.
Fairly certain bb-attachments is no longer working with the newest 1.0 releases
(neither is bb-topic-views apparently)
Remember if you use any of my major plugins like bb-attachments or bb-polls they do not work under RC1 or RC2 and will not be supported for months, so do not upgrade from bbPress 0.9 if those plugins are important to you.
SimpleScripts does a free install of bbPress to many hosts including GoDaddy.
http://www.simplescripts.com/script_details/script:bbPress
I cannot vouch for their quality or security and I highly recommend you change all your password afterwards, but it’s one way to get started if you have little technical knowledge.
SimpleScripts has been tested to work on the following web hosts:
(some may need manual database input)
* Bluehost
* Hostmonster
* Fastdomain
* LunarPages
* HostGator
* SiteGround
* GoDaddy
* WebHostingPad
* LiquidWeb
* StartLogic
* iPowerWeb
* Dot5Hosting
* MidPhase
* 1and1
I had started to write my own xref type of code to show how bbPress worked with a function reference and a action/filter reference but I never finished it.
But you can use grep to grab a list of all the function names and all the actions/filters.
Some people have run bbpress through phpxref and you can find that around the web via google, I don’t find such listings helpful myself though.
Akismet has lost it’s mind over the past several weeks or so.
Lack of whitelisting (as you discovered) is one of several pitfalls of using a remote service.
You could look at how my skip-akismet plugin works and check when $_POST contains submitted $_POST – if ‘post_content’ has only those whitelisted domains, you can unhook akismet as I do for mods, etc.
There’s also another possibly I have been considering – only send to akismet the first few dozen posts by any new member. After that many they’ve probably met with your approval and any other moderation should be done manually, not automatically.
People don’t write software to see their name in lights.
I think the point is being missed by some who haven’t kept up with bbPress history.
bbPress wasn’t invented by Matt to create a better forum for the masses.
It was invented to serve the needs of Automattic needing (faster) support forums.
It just happens to be open source so others can improve it, write plugins for it, etc.
You’ll never have “certified plugins”, that would have no useful purpose to Automattic. On the flip side I would never have written a single plugin if I thought it was being held to some kind of standard, I wrote them for “fun”, to see if I could do it, or to show others it was possible.
Releasing a product as open source is a way for business to get additional labor on their products for free by encouraging adoption. That’s not a criticism, that’s how it works in general. Matt used code from other open source projects so he’s motivated to also share his projects as open source.
Sure there are some projects that are made from scratch to try to serve the greater good. But there’s no reward for that, you can never please more than a handful of people with whatever you try to do, given how many different opinions and experiences there are in any community.
Some of the wishes expressed in this topic were expressed last year, the year before that and will be said next year and the year after that. Don’t use bbPress if any of those issues are important to you, because WordPress has been around for six+ years and it still has those issues and always will.
Have you installed a personal firewall recently on your computer that might be blocking all cookies by default? Do you need to add your own site to it’s whitelist?
bbPress will likely travel the same path as WordPress
so bloat and uneven internal feature adoption is unavoidable
but my hope is it will happen in far later versions than sooner.
I will fondly remember and miss the “good old” 0.9 days 
Note I’m not saying NEVER use 1.0, I’m saying for an active site don’t rush into it and perhaps for any new site, don’t start with it, since it can be upgraded.
Template developers should not use 1.0 until it has extremely wide adoption as it’s features are not backwards compatible, but any template you make in 0.9 will work in 1.0 with virtually no modifications.
timskii don’t worry about 1.0 not being debugged enough, even before RC1 it has a 10% adoption:
1.0a6 : 5%
1.0 ? : 5% (1.0 using pre-a6)
0.9.x : 52%
0.8.x : 35% (this is likely wrong, it includes 0.8 installs that upgraded to 0.9)
I highly encourage the use of 0.9 until (and maybe even through) 2010
1.0 is a different creature internally than 0.9 and while 0.9 has a few years of development and debugging (and compatible with most plugins) 1.0 has none of these things.
IMHO 1.0 should *never* have been called 1.0
0.9 should have been finalized and released as 1.0
and then what is now being called 1.0 should have been called 1.5
People simply do not understand that 1.0 is not some kind of minor upgrade to 0.9 with just incremental fixes – large portions of code have been changed or replaced entirely. Certain database tables have been completely replaced into a much more complex scheme, etc.
Remember, you can *never* downgrade once you start with/upgrade to 1.0
but there is always an upgrade path from 0.9 to 1.0
(someone someday might be crazy enough to write a downgrade routine for 1.0 to downgrade the database tables but it won’t be me)
There is also no clear path for bbPress from Automattic.
They are replacing the WP code base with WPMU, which means the purpose of the extremely labor-intensive drive to integrate BackPress into bbPress 1.0 is now even more unclear.
I’ve yet to see a single feature/ability in 1.0 that you will miss with 0.9
ps. I also think WP 2.5 is the last decent version of WP made but that’s for another forum
“Change Number of Front Page Topics” was formalized into a better plugin here:
https://bbpress.org/plugins/topic/front-page-topics/
If you have never done php programming the admin menu is going to be far too much for you to do.
But someone else might take up the project eventually.
unfortunately you’ve cropped the error, post it between backticks
the 2nd error, the warning, is caused by the first error, ignore it
I’d almost suspect the data isn’t being escaped properly before the mysql insert.
There is no place yet for themes.
Even the theme manager on WordPress.org is a fairly new rewrite.
I’ve put your theme on my theme switcher @ bbShowcase.org
http://bbshowcase.org/forums/?bbtheme=bbVanilla
Akismet has been getting worse and worse each week with false positives and unfortunately some of your posts fell victim to it. I have restored them.
This would be a very good beginners plugin to write, it’s very simple (other than the admin interface).
bbPress fetches stickies via a separate query (which I have always found to be a waste, except for this case) and you could manipulate the results before the final template is loaded.
For example on the front-page if you looks at index.php
you’ll see that
$super_stickies = get_sticky_topics();
and then there is
do_action( 'bb_index.php', '' );
so you hook the action bb_index.php
and then you do a global on $super_stickies
and then you manipulate the order of the array as desired.
for forum pages it’s
$stickies = get_sticky_topics( $forum_id, $page );
and
do_action( 'bb_forum.php', $forum_id );
same concept
That part would take less than an hour to write.
and you’d store the order in the topicmeta
But the part that will take much more time is the admin interface.
Instead you could simply add an extra field on the post edit page that only admin would see and let them chose the topic stickiness priority.
(this is not a plugin I will be writing)
