child theme/custom header travails
-
Facts:
WordPress 3.5
Buddypress 1.6.2
bbPress 2.2.3
Theme: BuddyProblem:
My header currently has a black background and I want to substitute an image as a background in the header. From what I’ve seen the best way to do this is to implement a child theme which makes total sense.
I’ve followed the various instructions at various places but I must be missing something. Basically once I’ve implemented the most basic child theme with the child style.css importing the Buddy style.css I would expect that I could visit my site and it should look exactly as before since I’m doing nothing in my child theme in terms of customization at all at this point. My intent was once I get that implemented and verified then try to implement the image in the child theme, ie stepwise approach.
My child theme directory is at the same level as buddy and contains only the style.css file as below
However, when I visit my site with this child theme activated my header is all screwed up as well as all my navigation and sidebars. The logo and menus are all gone. I also see the following message in the admin area.
You’ll need to activate a BuddyPress-compatible theme to take advantage of all of BuddyPress’s features. We’ve bundled a default theme, but you can always install some other compatible themes or update your existing WordPress theme.
When I revert to the Buddy theme everything goes back together as before.
Here’s the contents of my child style.css
/* Theme Name: Buddy-Child Description: Child theme for the Buddy theme Author: MyName Template: buddy */ @import url("../buddy/style.css");
If I just change the color of the header directly in the buddy/style.css in the header section I can see my change immediately so I know that file is controlling my header but of course that is not the recommended way of doing it and I want an image anyway and want to implement that in the child theme so I don’t lose it when updating in the future.
What am I missing?
- The topic ‘child theme/custom header travails’ is closed to new replies.