Hi @eable,
The directions look like they mean for me to move the whole of /buddypress/ into my child theme
Be careful not to copy the whole BuddyPress plugin to your child theme. Just the templates should be copied. As you mention in your post, the templates are found here /bp-templates/bp-legacy/buddypress/
Also worth mentioning is you only need to copy the templates you need. So for example, if you want to modify the members loop, then you can just copy members-loop.php into folder /your-theme/buddypress/members/members-loop.php
Thankyou, @henrywright.
Copying the whole plugin would be much more than what I did.
I copied the buddypress folder that is contained in bp-legacy. Is that not was what the directions meant?
If I did this right, why are the files not visible in the WordPress back end at Themes > Editor > mytheme?
I copied the buddypress folder that is contained in bp-legacy. Is that not was what the directions meant?
That sounds right to me.
If I did this right, why are the files not visible in the WordPress back end at Themes > Editor > mytheme?
If you’re not working on localhost, you’ll need to upload the files to your web server. Have you done that?
I’ve uploaded them to a working child theme installed on a working installation of WP multisite. Both WP & BP are the most recent versions.
mytheme is a child of 2013 that contains
style.css
404.php
and the buddypress folder I copied from within the bp-legacy dir
no functions.php yet
BuddyPress is installed and working.
I’ve made child WP themes before, but never with BP.
@danbp Before I started this thread I read that thread, and the two files you link to in that thread.
I’m sorry, but I don’t understand.
@eable so your theme contains just the /buddypress/ folder and style.css and 404.php files? I think that might be your problem. Themes must include an index.php file. Try adding one and see if the problem is resolved.
A child theme does not have to have more than style.css, correct? This is a child theme of 2013.
https://codex.wordpress.org/Child_Themes
I can add an index.php, but I don’t have a reason to customize it yet. Are you saying that a child theme has to have an index.php in order for files in a buddypress dir to show up?
Hope that you understand this tutorial:
codex.buddypress.org/themes/bp-theme-compatibility-and-the-wordpress-default-themes/twenty-thirteen-theme/
@eable apologies I didn’t realise you were using a child theme. You’re right, just style.css is required in that case.
@danbp – Yeah! Thank you! Saw that earlier. Lots of useful stuff in there. I’m looking forward to seeing how much I can do with the groups views, especially.
@henrywright – No problem! I appreciate any help.
I want to figure out why these files aren’t showing up, so I can start to learn from breaking things on purpose.
I’ll check back later, after I try copying the buddypress template dir into the full version of TwentyThirteen. If the files show up in the full TwentyThirteen, I did something odd in my child theme. If they don’t show up, the problem is that I don’t understand how to get any theme to see those bp template files that I want to play with.
Gotta be something noob-worthy. When I get this figured out I may be qualified to write a dummies-friendly tutorial – LOL
One thing again: you add ONLY the file(s) you want to modify into /child-theme/buddypress/ folder !
Will I mess up WordPress’s ability to see them all, if I drag them all over?
Also, I’m assuming I need to retain the dir structure? For instance, if I just need home.php from buddypress/activity/single, I have to put it here mytheme/buddypress/activity/single/home.php?
I know I don’t need to overwrite anything with an exact copy of itself. 🙂
Thanks again for your time.
@eable good idea to test on the Twenty Thirteen parent theme. If it works then you’ll know something is up with the child theme.
Will I mess up WordPress’s ability to see them all, if I drag them all over?
There’s no harm in dragging them all over. And yes, you do need to retain the folder structure.
>When I get this figured out I may be qualified to write a dummies-friendly tutorial – LOL
Did try and write it as noob friendly as possible 🙂
The editor im WP won’t show subfolders or used not to and it’s not a great idea to edit files this way or indeed have it running from a security point of view.
And the file paths/dir are vital as stated in the guide. When you are a little more familiar with the process of template hierarchy and theme compatibility have a read of the more advanced guide on how to further modify the template files for more specific actions.
Big cheer, verrry sheepish – it was a case of not thinking it was working, because no files were visible in the WP editor.
I added a bit of lovely, old school inline css to mytheme/buddypress/activity/single/home.php:
<div id="buddypress" style="background-color: pink;">
Worked like a charm. The background of the single activity update view is now pink.
……………..
> Did try and write it as noob friendly as possible 🙂
– Ohhh, but there was that caped noob crusader detail I was blind to at the moment! LOL
> The editor im WP won’t show subfolders or used not to
– Actually, the WP editor can show subfolders – they look like (dirname/filename.php)
AND now I know that not all files show.
> it’s not a great idea to edit files this way or indeed have it running from a security point of view.
– Yup. I never use the wp theme editor on an active or remotely hosted site. I don’t even like to sign in as Admin unless I need Admin rights that day.
Thank you for your patience, everybody. Hopefully the way I tagged and titled this post will help the next wanderer with related confusions find their answer in Search.
