You need to modify the topic template in your BuddyPress theme:
/groups/single/forum/topic.php
Unfortunately I can’t code the thing for you.
This thread can perhaps get you in the right direction:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/the-forum-topics-second-posts-position/
Gotcha.
Sounds like a timezone issue. Your server might need to be set to the correct timezone. Also try manually setting the timezone in the WordPress admin area:
https://codex.wordpress.org/Settings_General_SubPanel
you can check out the site
community.mis.temple.edu
This is wierd, so the next post finally came (which is one more post).
This one is 8 hrs ago, The one before this is 1 day and 8 hrs (this is right before the move)
meanwhile i found a plugin which could work – still not found out how 
https://buddypress.org/community/groups/one-quick-post/activity/
No, all seems to work correctly, is just that seems that when you put buddypress in a secondary blog, it doesen’t caches the primary blog posts… because the posts of my secondary blog are appearing
I actually did as soon as you suggested it, no success
@travel-junkie – if you are a hoarder it might make sense. it’s disorganized. should be able to click on plug-ins as an admin and see everything. but you have to go to another section of admin. how many admin pages really need to be there? only one. if it’s not broke don’t fix it. it only adds more time to your administrative duties on your site. back and forth and back and forth and back and forth again. this is actually the worst wordpress update i’ve ever experienced. it seems rushed and untested. with over 60 million people depending on it you’d think… well, that’s the problem… i thought. nevermind.
@DJPaul – well, people ought to know that if they are running plug-ins (any plug-ins including spam plug-ins) that most of their installed plug-ins are going to get killed. Including Welcome Pack. And I did comment on the WordPress site. Not happy. There is no way there was enough testing on this. On Buddypress side, things are working fine. It’s WordPress. All my major plug-ins… dead. Now I’m going to have to revert back to the previous versions. I really shouldn’t have hit the update button. But… you’d think that you should be safe to do so.
Feedback on WordPress should go on the wordpress.org forums, so the community directly involved with that product can see it.
`
Wouldn’t it be easier if all the plug-in developers, BuddyPress, and WordPress somehow got on the same page so that all updates could be easily streamlined so that we didn’t need to go through this every time?
`
BuddyPress had a same-day compatibility release for the next version of WordPress. We had planned it for months. It couldn’t have happened quicker
WP really irritates. I’m going to refrain from using foul language because everyone who commented was able to.
It’s broken lots of the plug-ins I was using. Welcome Pack – doesn’t work. BP Album + – doesn’t work, although I spoke with the plug-in developer and he is currently working on a fix. I don’t know who the Welcome Pack developer is so I don’t know if he is aware that it is broken. The BP Album + developer didn’t know that their plug-in wasn’t working. So maybe the other plug-in developers don’t know that their plug-ins don’t work either. Who knows?
Wouldn’t it be easier if all the plug-in developers, BuddyPress, and WordPress somehow got on the same page so that all updates could be easily streamlined so that we didn’t need to go through this every time? If the plug-in developers were able to test their plug-ins before the updates were integrated that could save EVERYONE lots of headaches. Is it possible for this simple streamlining of events to happen? Can’t there be a centralized place where things are actually tested first?
Not only did WP break certain plug-ins but they’ve also changed the way “users” and “sites” are listed in the dashboard. They are all alphabetical now. If anyone knows about spammers and how OFTEN we have to mark them as spam on the fly or delete them, they will know that an alphabetical listing is not efficient. This is an IDIOTIC change. Having users and sites listed as first joined or created and last joined or created was better as deleting spam took 1 minute. Now it takes an hour. You have to click through each page or copy and paste the spammers user name into search users in order to delete or edit or whatever.
And what’s up with “network admin” and who thought that was a good idea? What’s going on WordPress? I know this isn’t a Buddypress issue, but a cook is a better designer of a kitchen than an architect. Just sayin’. UGH.
Argh – it doesn’t work if the image files are small enough that they don’t need to be resized – this is what adds the widthxheight to the end of the filename as far as i can tell.
For now I have added a rejection for any files that end in ‘myavatar’ .ext, and added a message to users that if their files don’t upload properly they should rename the file in that format.
This is pretty poor, though. Is there any way I can set up a rejection of any files in the avatars folder that do not end in bpfull. or bpthumb.?
That makes a lot more sense. thanks @r-a-y
Disable the Ability for your users to upload their own avatars in the wp-admin buddypress section.
Go to gravatar.com and upload your picture there.
put in bp-custom.php:
`remove_action( ‘wp’, ‘bp_core_screen_signup’, 3 );`
It’s pretty self explanatory, if you read the directions carefully. Once you install buddypress, you must choose between an existing installation, or a new installation, and it will do it for you, and you are done. Read this also: https://codex.buddypress.org/buddypress-site-administration/buddypress-forum/ for extra help on setting it up.
@r-a-y, sorry. I am just so determined to get my forum to say replied on second post, and from them on like: http://etivite.com/groups/buddypress/forum/topic/still-got-problems-with-the-latest-topics-widget/
Etivites. With your solution, it sort of goes there, but on the second page, it does not say “replied” anymore..
Found my Answer.
http://bpdevel.wordpress.com/2011/02/24/updating-your-buddypress-plugins-for-1-2-8/
The BuddyBar and the WP Admin Bar Additional logic has been added to the BuddyBar loader (bp_core_load_admin_bar()) to account for the introduction of a similar admin bar in WP 3.1. (There are plans to integrate the core version BuddyBar into the WP admin bar in the future, but for now you have to choose.) By default, the BuddyBar is shown. Site admins can disable the BuddyBar in favor of the WP admin bar by defining define( ‘BP_USE_WP_ADMIN_BAR’, true ); in wp-config.php. BP_DISABLE_ADMIN_BAR continues to disable *all* admin bars, and takes precedence over BP_USE_WP_ADMIN_BAR. If your plugin or your site has made modifications to the way that the BuddyBar loads, you might want to verify compatibility with BP 1.2.8.
I upgraded to both BP 1.2.8 and WP 3.1
I Have completely lost my BuddyPress section of the dashboard unless I navigate to http://mysite/wp-admin/network/ and then (as others have reported) all the BP plugin links are missing. Other than that so far so good.
Our forums seem to be working fine.
That function name is a little misleading, as bp_the_topic_last_poster_name() only works within the forum loop on the forum directory.
You’ll have to write your own function to grab the last poster name in the topic loop try something like this in your theme’s functions.php:
`
function my_the_topic_last_poster_name() {
echo my_get_the_topic_last_poster_name();
}
function my_get_the_topic_last_poster_name() {
global $forum_template;
if ( !$domain = bp_core_get_user_domain( $forum_template->topic->topic_last_poster ) )
return __( ‘Deleted User’, ‘buddypress’ );
return apply_filters( ‘my_get_the_topic_last_poster_name’, ‘‘ . $forum_template->topic->topic_last_poster_name . ‘‘ );
}
`
Then in your topic.php, add the following:
`
`
That’s actually the WordPress Admin Bar and it resembles the Buddypress Admin Bar.
To disable it add this to functions.php:
add_filter( 'show_admin_bar', '__return_false' );
you can download some version of translation on the buddypress i18n trac:
https://i18n.trac.buddypress.org/browser
or on the buddypress trac:
https://trac.buddypress.org/browser?order=name#tags
there are only 3 strings diffs between 1.2.7 and 1.2.8 pot, so it’s not very important at this time if you miss something
If you want to work with pot files, you have to pick in the tagged version, not in the trunk (except for your private tests of course)
Same issue here, any help?
