I am not running svn, but rev. 3326. I do a manual update each day just to catch up. For instance, you made tons of commits last night so I need another update. Dad is quite sick today so I have to take off for a bit, but will install new vs. when I return home tonight.
For the most part, I have not yet gotten into looking for bugs as I am 100% focused on building a custom template. For now I am not going crazy until things are more stable. It is a tedious job recreating the theme templates on each revision, which means I am leaving the internal logic alone for now.
Once I have a better grasp of what is truly going on, then I’ll post more reports. These reports are just the basic stuff that I am coming across while picturing what I want my bbpress to function like.
I’ll send you a link to my demo forum when you wake up LOL.
I saw all the new commits in the middle of the night, amazing…
Is there a way to apply the Human Test plugin to the bbpress plugin?
Thanks.
This is such a silly issue, but for new users (myself) included it seems to be troubling. I have 2.0.beta1 on our WP site (version 4). I changed my permalink structure from the default to the and created a page called forums.
Yet still the forum I have created with bbpress does not appear on my WP site. I can see the forum from the admin side. Here are the two urls in case that helps – many thanks!
(forum) http://storytelling.concordia.ca/storiesmatter/forums/forum/stories-matter
(site where forum should be) http://storytelling.concordia.ca/storiesmatter/forums
This is such a silly issue, but for new users (myself) included it seems to be troubling. I have 2.0.beta1 on our WP site (version 4). I changed my permalink structure from the default to the and created a page called forums.
Yet still the forum I have created with bbpress does not appear on my WP site. I can see the forum from the admin side. Here are the two urls in case that helps – many thanks!
(forum) http://storytelling.concordia.ca/storiesmatter/forums/forum/stories-matter
(site where forum should be) http://storytelling.concordia.ca/storiesmatter/forums
Is there any way of setting permissions for users at this time (with the bbpress 2 beta)?
As in, people who are not logged in should not be able to read the forums.
Thanks JJJ, I tried the recount on the standalone again just to be safe but it does not appear to have affected the post_position column. Every row still says 0.
(I got “Removing deleted topics from user favorites… Failed!” but I assume this does not have anything to do with my issue.)
Do I need to write a simple script that looks at each topic_id, ordered by post_time, and then insert 1, 2, 3, 4… etc. into post_position? Or should the recount have taken care of this?
I guess at this point this is not bbpress 2.0 related (or is it?) so if I should create a new topic on this, please let me know.
Should be an easy adaptation. Would be awesome of someone to port that over.
@kai920 – Go to the tools/recount area of your stand alone installation, and run all of the recount functions there (just to be on the safe side.)
Any chance I can get some screen shots of what’s going on? Some of this is anticipated behavior.
There’s are a few ‘context sensitive widget’ type plugins available for WordPress that would probably be the best places to start.
Are you using Beta 1, or using the SVN checkout? Since you’re actively finding smaller bugs as you go, it’d be helpful if it were possible for you to switch to running the SVN checkout and get the updates as I commit them.
Added a wrapper to user.php.
The style of this template comes straight out of the TwentyTen theme.
Thanks Gautam,
I did that instead but still having the same problem.
The only way I can solve the problem is by taking:
<?php bbp_get_template_part( 'bbpress/form', 'reply' ); ?><br />
from single-topic.php out of the loop.
Would be nice to have a switch to remove a users favorites from users views.
No, I have not setup any forums as private or hidden yet, have not yet made it that far into bbpress.
Favorite topics are public in bbPress 2.0, and always have been in previous versions.
Is it possible the reason why they’re appearing for you when you’re logged in, and not for other users (or logged out users) because those topics exist inside a private or hidden forum?
I did find a possible undefined variable situation that could cause an error value to be returned instead of topic ID’s, so if the topics exist in public forums, that code change might fix it.
@dotaleague – There will probably never be a 1.3 version of bbPress. The next standalone version will be 1.1, which will most likely get released along side 2.0.
@dotaleague – There will probably never be a 1.3 version of bbPress. The next standalone version will be 1.1, which will most likely get released along side 2.0.
Fixed in SVN, will be fixed in Beta 2.
When I am logged in and go to my user.php profile page, I am indeed able to see a listing of my favorite posts.
It is when I am not logged in that my user.php profile page says
‘This user has no favorite topics.’
Now either the logic is broken, or it is intentional not to show a users favorites to a non-logged-in user. If that is the case then we need the logic to remove the favorites from non-logged-in users.
IMHO, I don’t think the public has any business knowing which posts are my favorites. I’d rather just have that text taken out of the template if I am viewing any users profile other than my own.
So far every single template that I have worked with have had some type of ‘wrapper’ around the bbpress content.
example:
div class=”bbp-topic-wrapper” id=”bbp-topic-wrapper-1546″
The bbpress/user.php is the only template so far that has no type of ‘wrapper’ containing the output.
This is not really a problem as I was able to add my own wrapper, but it would be nice to have one built into the standard theme.
Reasons:
I am applying a padding/margin of 20px to the wrapper in order to display a separate background color for the forum area. Having a wrapper makes this natively easy.
also.. this is the only template that is really displaying items in a really weird way. Below the user area is a table list of the users posts that is somehow falling outside the normal layout.
I have to admit that this particular template in its current state is a pain in the butt to apply custom styles to. IMHO This template needs a bit more thought about the flow of information.
Yes, that makes sense thanks 
So, how do I make sure the first posts are ‘cached properly’? I ran another test import and on the screen, the feedback the plugin importer gave was:
Added topic #2559 (LG's iPhone - the KS20) as topic #1374 with 1 replies.
Is ‘1 reply’ same as ‘1 post’ (and no replies), or does it mean it had 1 reply to the original post?
edit: this line isn’t returning anything (i.e. $first_post is empty)
$first_post = bb_get_first_post( $topic->topic_id );
edit2: turns out, there IS something wrong with my bb_posts table… the post_position column is all 0! Is there a way to repair this?
@bryan_w
Yes, I believe it is indeed a code problem. I have used a number of different forum systems and ordering the forums always follows the same pattern as what I outlined above.
Meaning, I can use order #1 within each sub-forum, otherwise trying to maintain the ordering is a nightmare.
The problem may lie within ‘nested’ orders of sub-forums.
If I mark a post as either super sticky or sticky it does indeed stick to the top.
However, the same post shows up twice, once on the top, and also repeated again within the list of posts wherever it would normally belong.
In my instance I made a super sticky post and can also find the same sticky post on page2 of my forum. It is even highlighted on page 2, just like it is on page 1.
solution:
I believe this is a similar problem that I ran into when building a featured gallery. The solution was to store the post id#s of my featured posts, and make sure to remove those from the loop calling the regular posts, i.e. no duplicates.
Sorry, I have not read through any of the bbpress code itself beyond theme files to even have a clue on where to fix it, otherwise I would try and post a fix here.
