BuddyPress.org

Thanks for your quick reply. The mentioned thread was just to show that someone has already tried to find a solution.

I have no coding skills at all, but I guess someone – either BuddyPress or YOAST team would have to make changes to their code in order to solve the issue. Can you please go ahead and raise the issue on Trac? If someone asks specific questions there, I most probably could not give the right answers.

Regards,
Martin

Thank you for the response. I reviewed both links and not sure if it answers my questions.

While I understand that your plugin will allow the member’s posts to show, it doesn’t answer my core question of what if we as administrators are the “author” of the post in WordPress and how we then associate a post with that member so it can then show?

James

i was able to get your first example to work

function add_banner() {
echo ‘this will be a banner’;
}
add_action( ‘bp_before_activity_loop’, ‘add_banner’ );

when i replaced activity_loop for directory_activity it didnt seem to do anything.

sorry for the newbie questions & thank you for your help so far

OK, no replies as of yet but some progress to report:

I abandoned the idea of making minor style customizations in my WS child theme’s style.css because of the inconsistent results I was getting (see my previous post). Instead, after more hours scouring of the internet, I found a different approach which is to setup folders under my child theme folders like so:

…/wp-content/themes/mytheme/buddypress/css

I then created a new file named buddypress.css in the new /css folder, put in a couple of css entries and voila! – it didn’t work. Determined to get this working, I then spent a few more hours of scoouring and through trial and error and finally came up with the following which does work for me:

1) setup the above mentioned folder structure under the child WP theme
2) copy buddypress.css from the core buddy press css folder under the chosen template (e.g. nouveau) to the new css folder
3) rename the new buddypress.css to “buddypress.min.css” (even though it is not “minified”)
4) changes made to the new buddypress.min.css now take effect (hoorah!)

Although this approach seems to work, it does raise several questions:

A) since the custom version of the css file is not “minified”, does this not defeat the purpose of minifying css files in the first place (i.e. presumably performance improvements)?

B) I would have hoped that the custom css file would only need to contain deviations from the theme’s css – however this does not seem to be the case. It appears that the entire file needs to be copied. The concern here is that when buddypress is upgraded, there may be css changes in the upgrade that are now “masked” by the custom css file which contains the older version of the styling (in cases where no modifications were made) – this seems a bit “messy” to me

C) I guess my main question really is whether the above approach which I finally settled on is valid and is the best available approach.

Sorry for the lengthy post, but I am seeking clarity on this so that I end up with a good long term solution.

Dennis

It was because I was updating my display name via wp_update_user that the profile page wasn’t showing.

So i guess the real questions is, why is it that when I update the display_name via wp_update_user, the profile url isnt updated?

That answers my questions well! I was expecting as much but wanted to make sure I wasn’t reinventing the wheel. I’ve worked with WP for a long time now and this is a passion project so hopefully I can devote some time to educating myself and getting it done. Thank you!

It seems that you have to have a paid account to ask them questions.