Hi,
I’ve just integrated bloguismo.com and bloguismo.com/foro with BBPress but I’m doing something wrong with cookies.
First of all I’ve done deep integration but I have the logout/login problem…
Second: in the wordpress part (bloguismo.com) i use on the top nav bar this:
<?php $user_info = get_userdata(1);
echo($user_info->first_name . “n”);
?>
So it could shows the first name of the user registered, but shows my name (admin name)… could you register and test?
http://www.bloguismo.com/login/?action=register
http://www.bloguismo.com/foro/register.php (the same)
thanks!
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!
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.
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.
@Gautam 15? Simply brilliant! If only I could breath code like you do.
Unfortunately, I just break, test and report things and that’s all.
OK. Happy to test. How do I contact you?
I am still in the finishing stages of finishing mine up and always do need testing databases to make sure it works fine.
Do contact me if you would like to help me test it as I would like to test the converter on just more then my original IP.Board and default installations.
Thanks for the update, John and Gautam!
As I am anxious to convert my existing stand-alone bbPress installation to the new WP-plugin version, I expect to start testing (and porting over my existing bbPress Theme) once the Plugin hits beta.
I’m curious about template tags, functions, and documentation. Are the existing template tags and functions from the stand-alone version used in the Plugin version, or have you developed all-new tags/functions?
Also, as I remember, part of the biggest problem with the stand-alone version was the lack of documentation. So (in all my free time…) I’ll do what I can to pitch in for documentation with the Plugin version.
Thanks for the update, John and Gautam!
As I am anxious to convert my existing stand-alone bbPress installation to the new WP-plugin version, I expect to start testing (and porting over my existing bbPress Theme) once the Plugin hits beta.
I’m curious about template tags, functions, and documentation. Are the existing template tags and functions from the stand-alone version used in the Plugin version, or have you developed all-new tags/functions?
Also, as I remember, part of the biggest problem with the stand-alone version was the lack of documentation. So (in all my free time…) I’ll do what I can to pitch in for documentation with the Plugin version.
As a sidenote to the original topic! …
Rich Pedley: @Mark – test again 
Thanks for that Rich, you can see I’m having a little nose around, and thanks for the offer Gautam — Even started talking to myself, and trying out other stuff too!
As a sidenote to the original topic! …
Rich Pedley: @Mark – test again 
Thanks for that Rich, you can see I’m having a little nose around, and thanks for the offer Gautam — Even started talking to myself, and trying out other stuff too!
@Mark McWilliams
Just DM me your email id and I’ll mail you your user/pass of my test forums.
@Mark McWilliams
Just DM me your email id and I’ll mail you your user/pass of my test forums.
My rule regarding trac vs forums, is that the forums are traditionally for support and confirmation of an issue occuring, and the trac is for when bugs appear that can be duplicated and/or you have a suggested code change. You can even drop enhancement requests in the trac if you have a really neat idea, even better if you have a patch to match it.
Core developers live and breathe by the trac. If it isn’t in there, it doesn’t exist. It’s our diary of development, and without it our lives would be much more difficult. The trac is less social, and more developer speak. The forums tend to be a little more relaxed.
With WordPress 3.1 almost in its third release candidate, we can expect it to ship really, really soon. That said, it makes sense to drop 3.0 support and focus on 3.1. I’ve made sure we’ve stayed compatible with 3.0 this entire time, but it’s time to focus on the version of WP that the bbPress plugin will see the most use on.
Thanks to everyone that’s been testing on 3.0 installations. If you *really* want this to be 3.0 compatible, definitely open trac tickets and contribute patches to keep that support alive.
Is there a link to download for testing?
just checked out the latest revision, installed locally and I seem to be missing the:
Edit | Trash | Close | Spam | Sticky | Move
against topics, I’m just seeing Edit | Trash
is this a bug? Or have they been removed intentionally?
I was reading a reply to my own thread when I noticed it said on the left:
Started 10 hours ago by hennyjack
“hennyjack” hadn’t even posted in the thread. I was going to report this, but then I thought, “why bother? It’s not the old bbP standalone we should be worrying about anyhow.”
I’ve tested bbPress and it can definitely talk the talk, but of course I can’t tell for sure if it can walk the walk on a high profile site such as bbpress.org. That said, I think this is as good a time as any to start discussing when the bbPress community should start “eating their own dog food”.
Maybe a good topic for the next weekly meeting?
The recent WordPress security upgrade (regarding kses) wasn’t 4 hours from initial contact to release, but you’re right to say that having more eyes and developers did help to expedite the testing.
Needless to say I wasn’t personally accessible to work on this until I was back from holiday, so it is me dropping that ball and not being prepared. I’ll take that responsibility even if no one expects me to. 
Honestly, the reminders get a little repetitive, but only because I get them from a few different places. Open source development is kinda like having 1,000 bosses, but I’m used to it and take pride in having people be worried about the state of things.
I’ve got pretty thick skin and don’t take things personally. So, no worries. 
Another personal hurdle was learning exactly what the procedure is to actually push out a release of bbPress. Having never needed to do it yet, and having the only person who has in the past few years (Sam) not immediately at my disposal, it took a few days to get me setup and ready to be able to do it.
The trunk and 1.0 branches are fixed. The 1.0 branch is ready for a release. I am going to do the 0.9 branch tonight, do some testing, make my first deployments, and look forward to things hopefully going smoothly for releases tomorrow or this weekend.
I’m not new to bbPress, but I am new to the logistics. Don’t fret, I’m a fast learner.
The recent WordPress security upgrade (regarding kses) wasn’t 4 hours from initial contact to release, but you’re right to say that having more eyes and developers did help to expedite the testing.
Needless to say I wasn’t personally accessible to work on this until I was back from holiday, so it is me dropping that ball and not being prepared. I’ll take that responsibility even if no one expects me to. 
Honestly, the reminders get a little repetitive, but only because I get them from a few different places. Open source development is kinda like having 1,000 bosses, but I’m used to it and take pride in having people be worried about the state of things.
I’ve got pretty thick skin and don’t take things personally. So, no worries. 
Another personal hurdle was learning exactly what the procedure is to actually push out a release of bbPress. Having never needed to do it yet, and having the only person who has in the past few years (Sam) not immediately at my disposal, it took a few days to get me setup and ready to be able to do it.
The trunk and 1.0 branches are fixed. The 1.0 branch is ready for a release. I am going to do the 0.9 branch tonight, do some testing, make my first deployments, and look forward to things hopefully going smoothly for releases tomorrow or this weekend.
I’m not new to bbPress, but I am new to the logistics. Don’t fret, I’m a fast learner.
The trunk is technically 1.1, so both the 1.0 branch and 0.9 branches also need fixes, which means they both need testing. There is also another critical bug that’s cropped up that I’m working on currently, to get them both in under the same security releases.
The trunk is technically 1.1, so both the 1.0 branch and 0.9 branches also need fixes, which means they both need testing. There is also another critical bug that’s cropped up that I’m working on currently, to get them both in under the same security releases.