I have been testing the bbPress Plugin on Windows, well I was up until about a month ago when I hit a few PC problems, but like JJJ said … much has changed since then! 
For one, that’s a paid script.
Which would be fine, except their “About Us” page has an HTML problem. Hope their actual script is better than their crap website.
My question: will this also migrate files that have been uploaded?
The best script is the migrators.eu ipb2bbpress script. It convert anything just perfect!
Take a look!
http://www.migrators.eu/migrators.php
Each topic already carries the name of the person that started it, so this is very easy to do without a plugin.
Simply edit your front-page.php and forums.php templates and put
<?php echo $topic->topic_poster_name; ?>
where you’d like it.
also see this tag
https://bbpress.org/forums/tags/topic-author
Each topic already carries the name of the person that started it, so this is very easy to do without a plugin.
Simply edit your front-page.php and forums.php templates and put
<?php echo $topic->topic_poster_name; ?>
where you’d like it.
also see this tag
https://bbpress.org/forums/tags/topic-author
Forum performance inside of BuddyPress is improved in 1.2.7 and will be further improved in 1.3 (which still includes the bbPress stand-alone version.)
Having BuddyPress load all of its code and process everything that it does is the bottleneck in your circumstance. You’d be better off loading bbPress standalone properly themed, then the bbPress plugin, and lastly inside of BuddyPress groups (regardless of standalone/plugin.)
But, I think it’s a horse a piece.
The more you need to load is the slower it’s going to be, and the more important caching becomes. The bbPress plugin will respond to W3TC much better than bbPress standalone and BuddyPress will, since it uses the existing WordPress object cache.
Forum performance inside of BuddyPress is improved in 1.2.7 and will be further improved in 1.3 (which still includes the bbPress stand-alone version.)
Having BuddyPress load all of its code and process everything that it does is the bottleneck in your circumstance. You’d be better off loading bbPress standalone properly themed, then the bbPress plugin, and lastly inside of BuddyPress groups (regardless of standalone/plugin.)
But, I think it’s a horse a piece.
The more you need to load is the slower it’s going to be, and the more important caching becomes. The bbPress plugin will respond to W3TC much better than bbPress standalone and BuddyPress will, since it uses the existing WordPress object cache.
Judging by two recent comments [1, 2]made by two knowledgeable developers, it seems speed won’t be one of the key features the bbPress plugin will have going for it, at least not on initial launch.
How fast will BuddyPress forums run when powered by bbPp, as compared to the current BP+bbP integration?
—
If that’s too general I can use my own website as an example:
Per month we have about:
50’000 visits
250’000 page views
5 pages/visit
The bulk of that activity goes on in our forum, i.e. groups.
We use W3 Total cache.
The site runs on a dedicated box. I don’t have the specs right now but it’s a fairly powerful Ubuntu computer.
We use a minimal amount of odd plugins & widgets, yet our forum runs pretty slow.
—
Maybe this is a difficult question to answer, but I reckon it should at least be possible to make some fair assessments, and I do believe there’s a common interest in this information, considering the amount of people assessing the future of their community alongside the development of bbPp.
I don’t test with IIS… We could always put a call out on the hackers list if needed.
@_ck_ – Will do. I have a VM I can test on when I get back from Tybee next week, and will see about getting anyone on Windows to play with it. I know when I started, I was using IIS on Windows 7 and it was working fine, but much as changed since then.
well, i don’t know whether that is correct, but .htaccess in bbpress folder inherited the wordpress .htaccess data. removing that from .htaccess base in bbpress folder seemed to resolve the problem.
well, i don’t know whether that is correct, but .htaccess in bbpress folder inherited the wordpress .htaccess data. removing that from .htaccess base in bbpress folder seemed to resolve the problem.
I test on windows, to some extent, with EasyPHP.
I know y’all are in super-dooper alpha state right now but be sure to put on your list to test the plugin under windows (try the 1 minute xampp lite install for testing).
I’m not even sure where to start with some of the errors, I’ll try to debug.
ps. can an admin please turn off the hash-to-trac link plugin that’s running on bbpress.org? It’s incredibly annoying because it makes no effort to determine if it’s really a ticket reference.
@ Cashman
The bbpress plugin includes a standard theme which should work for most themes I suppose.
But if you want a perfect theme that fits you’ll have to make a child theme of the wordpress template your using atm.
Basic integration is where WP and bbPress share cookies, users, and login sessions. Basically, they don’t share functions. Deep integration will allow that. However, I am having some trouble deep integrating the two with my current theme.
Basic integration is where WP and bbPress share cookies, users, and login sessions. Basically, they don’t share functions. Deep integration will allow that. However, I am having some trouble deep integrating the two with my current theme.
Along the lines of what CK is talking about, the issue is one of DB structure. WordPress only gives us post_parent to help with post relationships, which leaves us with postmeta for everything else. That’s forces us to rely on the object cache and to try to predictively preload data that would otherwise be queried selectively and only as needed. A fully tricked out install with widgets and sidebar can fore the query count into the hundreds on pages like the user profile, with the object cache still missing quite a few.
Compared to bbPress 0.9, the current incarnation of the plugin will be abysmal query wise. Caching helps tons with this on the reads end of things. I’ve gotten it down to 1 cache miss on most pages, with auto cache refresh on writes. But this is one area where more eyes will be helpful. Like CK said, there probably isn’t a whole lot that can be optimized but I’d love to see it.
I’m just a little confused about how the themes work for this. Does there need to be a separate bbpress theme for each wordpress theme you want to use? Or can you use a default bbpress theme that will inherit the wordpress theme in use?
Gautam: no effect…using /%category%/%postname%/ and have tried /%postname%/
mobious74: Try going to Settings -> Permalinks and press save changes.
loving the dev going on here…I’ve been playing with the plugin on my local site and managed to get a lot working…including an import (albeit hacked to bloody hell) from http://www.iteisa.com/phpbb2bbpress. All my posts have been imported ok (still working on replies) and the counts all work on the forum front page…but if I click on a particular forum I get the, “Oh bother! No topics were found here! Perhaps searching will help.” Even though it says there’s 168 posts…
If I search for a post, or click on a user and show all their posts they show up fine.
This isn’t the case if I actually post something…they show up fine…it’s the imported stuff. Nothing I can see in the DB shows me that I’m missing something (although I obviously am…)
Any pointers?
Cheers,
Brian
Try using WP3 these days on an active site where there are cache misses, the server will fall apart. You cannot rely on the miracle of caching and ultra-fast hardware to get around fundamental design problems.
Too true.
So fundamentally the problem is with WordPress’ design?
There is no need to minify PHP comments, they are dropped by opcode caches.
However reducing query count is not going to be easy.
I’ll do a 3rd party analysis on the queries (and file count) next week or so, I suspect there is going to be little that can be done to reduce the load because of how this is now being done. It is likely any bbPress plugin install is going to have to be heavily cached on any reasonably active site, just like WordPress now absolutely requires a complicated cache like W3 Total Cache.
But what people don’t realize is you cannot cache an active forum like a blog, they work very differently. Blogs are write-once, read many times and then the comments can be isolated with periodic updates. But on a forum it’s write-many-times and constantly changing. So there will always be many cache misses and the mysql engine will get a huge workout.
Try using WP3 these days on an active site where there are cache misses, the server will fall apart. You cannot rely on the miracle of caching and ultra-fast hardware to get around fundamental design problems.
