apache friends = xampp = awesome
1 minute fully configured install plus you can turn on some other options like eaccelerator if you want later
Only thing I’d recommend differently than I did if you have the extra disk space is the full install instead of the lite install because the lite install can’t be (easily) upgraded.
Ah, now I remember when they changed/fixed that in WordPress. Because my logs became full of the cron entries with WordPress pinging back to itself through the server. I think it polls like every few minutes too which was annoying. Hopefully that’s changed too or it will have to be deleted asap (along with xmlrpc).
1.0 is going to be so much more bloated over 0.9
Snoopy/http class alone is 40k.
Just remember that the cron in bbPress/WordPress is fake and not parallel tasking. Meaning that the user waits while the task is completed when the task is triggered. Unless they are using url fetching via php to do a pseudo multi-task, which I doubt.
Sometimes (most times) a real cron is better. I asked them way-back-when cron was first introduced in WordPress to allow a real cron job to be substituted but still work with the API and I don’t believe they’ve ever done that.
Off the top of my head this looks like a very bad idea performance-wise:
AND NOT p.topic_id IN (SELECT t.topic_id FROM bb_topics
AS t WHERE t.topic_status <> '0')
Though mysql may optimize it on the fly. Technically there could be thousands of deleted topics on an active site which makes quite a few items to search for (though in your case, there are NO deleted topics, yet, so this won’t be problem early on). However I think topic_status has an index? If not, it’s even worse.
Alternatively you could “over-search” the results (ie. ask for 100 instead of 30) and reverse the check of the 100 topic_id’s to make sure topic_status=0.
Since you’d end up using two queries, you could merge the two needs, to check titles AND to check topic status for the previously returned list of posts.
You’re dead right about pagination becoming insanely complicated in this case. This could be solved by limiting result lengths to just 100 items max, and then use my “over-query” idea to ask for 200 just incase it hits alot of deletions.
Here’s a question I had not considered before but is important. When you downgrade in WP and bbPress, does the re-install also downgrade the db version number? I hope so, or things will completely break.
I would avoid GoDaddy and Dreamhost (for different reasons) but that’s just my personal opinion. GoDaddy’s management and customer service is horrific and Dreamhost’s filesystem is the slowest I have ever seen on any host.
I do recommend for technical novices (maybe even intermediates) that you get a host with cpanel so it’s easier to backup and move your entire setup at will.
no, bb_get_profile_link does not self echo but it does return a full formed url apparently, so I was half wrong to use it inside of a href.
The direct link is via get_user_profile_link( $id )
byles, your code is wrong in that it doesn’t need an echo
<?php bb_profile_link('link text here'); ?>
There is a bug in the older template you are using.
Find these line in your header.php in your template folder:
<?php bb_enqueue_script('topic'); bb_head(); ?>
<?php endif; ?>
and change it to this:
<?php bb_enqueue_script('topic'); ?>
<?php endif; ?>
<?php bb_head(); ?>
I think your broke your htaccess as I can’t see any topic.
If people can’t see the bars that probably means the CSS is not being included for some reason. Might need to check for bb_head in your header template.
Works fine for me with default template in newest 1.0 alpha. Or do you mean you want anonymous people to be able to vote. That’s not possible.
Any particular reason you started a new topic on this rather than asking on the page for the plugin itself?
I am not sure why people bump year old topics instead of posting on the page for the plugin itself, but to answer your question, if you are logged in and admin, you can add a poll anytime. Otherwise the ability to add a poll expires an hour after the topic is started by default (which you can change in the settings).
No, WordPress 2.6.1 and bbPress 0.92 cannot integrate logins/cookies at all. I guarantee you were missing that something was not working right.
WPMU users are pretty much on their own and have to ask the handful of other WPMU users.
It’s because you are destroying $user_id
This is wrong:
$user_id = bb_get_user( $user_id );
$bb_twitter = $user_id->social_twitter;
You should do:
$user = bb_get_user( $user_id );
$bb_twitter = $user->social_twitter;
$user_id holds the id number, not the entire user object.
If you didn’t hack the core and just templates, all they need to do is install the same version of bbPress you have installed, send them your custom theme files to install, and then send them a full export of your bbpress db to replace their default install. Then it should be identical.
Remember, the problem with MATCH AGAINST is it will not do partial words or words under 4 characters.
It’s not too hard to replace the search, you just have to decide which way you want to go. The regular expression will at least do 3 character words which I find is more common than you’d imagine.
The problem is that the time for any way without an index is going to increase dramatically once you start adding sorting and other options that cause full table scans. You can see this happen if you try to add a simple option to the regex demo like sorting by reverse post_id (which is a trick that should be a little faster than sorting by date).
SELECT * FROM bb_posts WHERE post_text LIKE '%test%' LIMIT 5 ORDER BY post_id DESC;
and
SELECT * FROM bb_posts WHERE post_text LIKE '%test%' AND REGEXP ':<:%test%:>:' LIMIT 5 ORDER BY post_id DESC;
You might want to test a worse case scenario by using three character nonsense words that will cause a cache-miss like “zzz” and “aaa”. Change them each time so mysql cannot cache the results and give you faster times.
If the above example returns in an acceptable amount of time you can just replace bbpress’s built in search with that simple method. By parsing a query you can also AND words together instead of bbPress’s default OR which to me is incredibly annoying and useless (you’ll notice no major search engine like Yahoo or Google does OR by default).
Well you have a point in that it’s important to you and you are expressing your feedback in the feedback section, however again, it’s an alpha issue so I can’t be motivated.
Oh and I would never actually delete you.
It was a just my own “feedback” you might say 
So don’t take it personally.
Oh and looking at a MySQL performance guide for text search, apparently bbPress’s search is using ALL of the slowdown triggers:
order by
group by
and worst of all SQL_CALC_FOUND_ROWS
How long does this query take without the modifiers:
SELECT * FROM bb_posts WHERE post_text LIKE '%test%' LIMIT 5;
because that’s as fast as it can possibly get without an index and should be used as a baseline.
Looking at the original query, I believe they are causing a FULL scan of the entire table to rank and group it first. That’s going to be insanely slow.
You might be able to just use LIKE with a simple sort by post date DESC.
The largest bbPress install I have access to has nearly 100,000 rows and still only takes 0.04 seconds for that trimmed query. The original queries you posted take 0.5 seconds so that’s 10x slower.
But keeping a full-text index can get rather huge, which is probably why bbPress doesn’t use it by default.
BTW, MySQL 5.1 apparently has some nice improvements in fulltext search.
If you have your own dedicated or vps server you can tinker with some mysql settings to speed things up. (You never did answer if you have mysql cache turned on)
If I had the ability to delete accounts it would be for people who insist their “missing feature” is the most important
Fortunately they are smart enough to not let me delete accounts, lol. Your missing feature is the least needed feature for thousands of other people.
Let me express this for the 100th time (not just to you, to everyone). 1.0 is *alpha* – it’s not stable, it’s not final, it’s not even close to final. They are adding and changing things daily. Sam just changed something this morning.
The bb-sync author (fel64?) did a fantastic job. But bbPress changing is not their fault (or their problem unless they want it to be).
If they go and spend hours to make it work now under 1.0 alpha, it may break again tomorrow. And the day after that. They are still changing 1.0 alpha and will change it again.
You running 1.0 alpha right now for a live, active site is exactly one person’s problem, yours.
I think that’s one of the default javascripts scripts loaded in the topic.php page.
It only shows in mini-track because it’s generated by a php file.
Most of the javascript in bbPress can be disabled and makes for faster loading pages (ajax goes away however).
So the answer is no, it’s not hacking. But you will see the attempts sooner or later – there are thousands of bots out there scanning sites and most people are unaware.
I’ll put in some code to exclude bb-includes in the next mini-track.
Super-Search is currently over 20k and only about halfway done in what it needs to do. All the bbPress core needs is a proper way to and/or words and disable partial matching instead of defaulting to just searching for every single fraction of each word.
Post revisions? You mean like my Edit History plugin?
This topic is old – bbPress has not been hacked – there was an exploit for all of a day or two back in 0.8 that was quickly fixed.
What’s happening is that OTHER programs on the same account or server are being hacked and what they do is attach themselves to the bbPress templates though those other programs.
In over 4000 sites, I’ve only detected 8 XSS hacks so it’s obviously coming in through other programs and not directly (or the problem would be far more widespread).
(And by the way, if you keep getting hacked, that means your server has been compromised and need to be wiped and re-configured. Just re-installing the PHP programs won’t fix the issue if there is a a hidden backdoor elsewhere. )
