This is vexing me. You can see the problem in action here: http://www.wordlab.com/forums/

I am using bp_the_topic_last_poster_name, which should show the last poster beneath the Topic title. It is behaving in three different ways:

1. For older posts and replies, made before today’s upgrade to BP 1.5, it works as it should.
2. For new post-upgrade replies to Topics that were created before the upgrade, it incorrectly shows the original Topic poster, instead of the last poster, but correctly links to the member page of the last poster
3. For new Topics created after the upgrade, no user or link is shown at all for the last poster.

I have the same problem using my modified child theme, the PB 1.5 Default theme, and the Frisco theme, so it looks like the theme code isn’t the issue. I have tried turning off all the plugins that I could, and I still have the problem. Updated permalinks in my .htaccess file, still have the problem.

I appreciate any help on this issue. I wracked my brains for hours and don’t know how to proceed. Thanks.

[@snark Participant 13 years, 2 months ago]

Has anybody seen this issue? It’s very weird — the Topic page displays just fine, and has no trouble identifying the latest poster. But on forums-loop.php, it can’t, and the problem persists with the default 1.5 theme, so it seems like something to do with WP/BP settings or is server-side.

[@snark Participant 13 years, 2 months ago]

Ok, here is a slight change to the pattern I’ve observed (in uppercase, below) with the display of bp_the_topic_last_poster_name in the Forums Loop — again, ou ycan see the problem in action at http://www.wordlab.com/forums/ :

1. For older posts and replies, made before today’s upgrade to BP 1.5, it works as it should.
2. For new post-upgrade replies to Topics that were created before the upgrade, it incorrectly shows and links to the NEXT TO LAST POSTER
3. For new Topics created after the upgrade, no user or link is shown at all for the last poster.

Does anybody know how to fix this????

[@snark Participant 13 years, 2 months ago]

@r-a-y @johnjamesjacoby @boonebgorges @DJPaul — Any of you guys have any idea what could be causing this problem and how to fix it? Thanks.