Narrowed it down a little bit. When using PHP 5.2.0, the results are odd for some posts, as described above. When using PHP 4.4.4, the search results are normal and as expected. Could be something different with the install or the compiled options. But, this is a little bit of the problem. In the phpinfo, one small thing I noted is that PCRE is version 6.6 in PHP4 and version 6.7 in PHP5. Is there anything else I can check in the phpinfo that would be helpful?
Trent, I would PM you but there’s no PM here yet… 
Can you check trac tickets 507 and 508? Those appear to be two other inconsistencies I found and reported. Maybe they can be bumped for 0.74 if you find the same issue with your install?
Thanks.
Trent, I created a my-templates/profile.php and changed line 52 of that file from:
if ( strtotime(get_topic_start_time()) < strtotime(get_topic_time()) )
to this:
if ( get_topic_start_timestamp() < strtotime(get_topic_time()) )
and now it works as expected and returns the correct date for the topic_start_time. I don’t know if that’s the correct way to fix it, but it works over here.
I also edited a couple of places where sentences end with “ago” and made them consistent with a period, or not, for all of them.
Trent, I am looking into bb-templates/profile.php around line 52. It seems like this test always fails and thus prints ‘No replies.’ Seems like the wrong two values are being compared or something. Also, it seems like strtotime(get_topic_start_time()) returns a really weird date, in the future too, and it’s changing too, every time I run the query. That should not happen for the topic start time (it is what it is, right?) Here are some of the time stamps I’ve received in the past couple minutes.
1169441052 Sun, 21 Jan 2007 22:44:12 -0600
1169441231 Sun, 21 Jan 2007 22:47:11 -0600
1169441457 Sun, 21 Jan 2007 22:50:57 -0600
The topic_start_time from MySQL:
2006-12-07 21:43:24
The topic_time from MySQL:
2006-12-17 15:58:30
The topic_time is accurate in the profile page (1166389110) but it fails because get_topic_start_time() is returning some date in the future…
Weird.
(Also, the date on my server is accurate, and my post freshness is working properly. The only issue I have with time is that the server is GMT -0500 and my customers are GMT -0600, so the post times are off an hour, but no one minds that.)
Does it make sense that it would have the wrong information? I am trying to understand that.
Never noticed at the wordpress forums. Weird.
I just checked here and in my profile, every thread I started says “No replies” after it, and that’s not accurate. Seems like it’s wrong? Why show “No replies” when there are replies? Why not just not show anything at all? Better no info than inaccurate info.
That was my thought, but I didn’t want to clutter this forum with bugs, since the closest forum name is troubleshooting.
Will post them here separately.
This is .73 – not using TRAC. Normally, there is no error. Just this once there’s an error. If it happens again I will post again. There have been a couple of weird MySQL errors in the past few days, but I doubt I will be able to recreate them.
fourthed – just had someone ask me about that today…
That php error is usually caused by white space/blank lines before the <?php or after the closing ?>. I would check for that first.
skrimpy, please share how you fixed it for the benefit of others who might run across the same problem. Thanks.
Maybe this will help:
https://bbpress.org/forums/topic/462?replies=4
p.s. glad you figured the first part out.
The site issue and the database issues do seem like separate things. That was the first thing that caught my eye though (the URLs.)
my database has bbpress_ tables (like bbpress_forums, bbpress_posts, etc) and wp_ tables (like wp_links, wp_users, wp_usermeta etc)
My config.php (bbpress) has this for the DB stuff:
$bb_table_prefix = 'bbpress_';
$bb->wp_table_prefix = 'wp_';
And mine just works with user integration like that. Is is possible that including the ‘http://dearauthor.com/wordpress/wp-config.php’ is overwriting something? I didn’t have to include that, and just have the one other require there. Why is that included for yours (did you read something I didn’t maybe?)
Looking at your original error:
'dearauth_bbdb.wp_users' doesn't exist
the table prefix there is set to dearauth_bbdb somehow. Maybe you forgot to close a quote or something? Or did you edit your config before posting it (i.e. it’s not the actual, but it’s edited without the same error maybe?) You didn’t post the MySQL and bbpress config stuff from the top of the config.php.
Just guessing, but maybe we’ll get it.
Hi Trent, Merry Christmas. I did install it and it apparently was working since someone got blocked :yikes: I could not find any logging anywhere, and to fix it yourself with the code provided
> Your technical support key is: 0000-zzzz-yyyy-xxxx
>
> You can use this key to fix this problem yourself.
you need to log in to the ioerror/homelandstupidity site here:
http://www.ioerror.us/ip/
But with the IP that was blocked. So, with no logging and no way to know why this legitimate user was blocked, I disabled it. I was looking at the logging a bit (using bad-behavior-wordpress.php as an example as suggested) but I haven’t figured it out yet. I was hoping there was a config section with four lines like WP or BB, where I could enter the DB details, but it’s not there 
So, turned off for now. It was doing something though, I just don’t know what or why.
I think if your blog is at dearauthor.com/wordpress, then
$bb->wp_home and $bb->wp_siteurl are both wrong – they don’t point to the blog but just the domain name. I think they should be:
$bb->wp_home = 'http://dearauthor.com/wordpress'; //
$bb->wp_siteurl = 'http://dearauthor.com/wordpress'; //
Also, your require once is different than mine, but that might be unrelated. This is the only one I have in my config.php:
require_once( BBPATH . 'bb-settings.php' );
I think the wp_home and wp_siteurl might be wrong. Did you go to WordPress – Options->General: Blog address (URL) and WordPress – Options->General: WordPress address (URL) and verify that the settings are the same there?
This has been covered in the forum before: https://bbpress.org/forums/topic/439?replies=2
Seems like the problem is with the CSS:
#profile-menu {
list-style: none;
position: absolute;
right: 0;
}
The position:absolute and the right:0 cause it to be anchored all the way over on the right side of the screen. Not much that can be done with it on bbpress.org, but if you are using the same template, you can fix your own CSS.
Yes, remove the directory from $bb->domain.
// Just the domain name; no directories or path. There should be no trailing slash here.
$bb->domain = ‘http://www.kensavage.com/forums’;
Trent, I installed this and the install went smoothly. How can I test this or know that it’s actually working? What differences would I see? I didn’t see any testing procedure in the FAQ at http://www.homelandstupidity.us
Thanks for sharing the procedure.
Works for me too. Now to do something like “WP Since Last Visit” from Alex King.
Also, I made the same change in forum.php on lines 16 and 25 for consistency.
edit: Oops, just looked through the files and that need to be changed in lots of places. I lost track already…
Downloaded v1.3 and it appears to be working exactly as expected. I like the new function.
OK – thanks. My freshness is accurate, so I won’t mess with it I don’t think. I can wait. It’s only an hour.
So, using this, the original config.php is set to the server offset from GMT, and then this $hours is set to … what? I am one hour off from my server (server is GMT -0500, I am GMT -0600) and my config.php is set to -5. What would I set $hours to? My freshness display is accurate now, but my post times are off an hour (they show server time, so an hour later in my case) and my search results show GMT all the time (which is likely another issue altogether.)
Thanks
Also, the config.php editing thing was addressed for version .74 here:
https://trac.bbpress.org/ticket/477
<strong>Description</strong>
There are many common errors made when editing config.php.
We can check for these errors prior to installation refuse to install if things are out of whack.
It’s not an install script, but it does at least validate the config. It won’t prevent the errors but it will catch them.
