August 8, 2013 at 7:31 pm #116860
I’m having trouble creating a child theme base upon Responsive (free).
The most basic child theme I can create looks radically different than the parent (e.g., the background is different, the menu item’s sub-menus are promoted to top menus. The header image is reverted to the default.
I’ve created a directory next to responsive in my ~/wp-content/themes/ directory.
and I’ve added a style.css file that looks like this:
Theme Name: Responsive Child
Description: Child Theme for the Responsive Theme
Shouldn’t it look like the parent theme?
What am I doing wrong?
August 8, 2013 at 8:28 pm #116895
August 14, 2013 at 5:15 pm #118210
Is there a child theme made for the responsive pro? :)
August 15, 2013 at 1:55 am #118244
Yes, I believe you can get it here:
August 15, 2013 at 4:38 pm #118429
One of the key updates to Responsive is that you no longer need to have the
@importline any more in your child theme.
August 18, 2013 at 11:16 pm #119012
I have the same problem, also when I remove the @import as stated in the update.
August 19, 2013 at 3:29 am #119037
Can you provide a link to your site?
August 19, 2013 at 9:19 pm #119165
So to expand upon Bryan Hadaway’s _terse_ reply (which is entirely true, but didn’t answer my question).
It seems that it isn’t necessary to have a child theme anymore for simple style.css changes. In short, Bryan was trying to say there’s a better way of doing what you want to do.
What I’ve come to realise is that what I was doing, was probably working. However, what was going wrong was I _expected_ the configuration changes I made when running on the Responsive theme would have carried over to the child theme. Which of course they didn’t. I had to re-apply the changes in the child theme as well.
Not Responsive’s fault… the WordPress documentation and tutorials that I’ve worked with weren’t as explicit about that as I would hope.
August 20, 2013 at 12:48 am #119177
August 20, 2013 at 1:46 am #119217
Not entirely off-topic: there seems to be a small bug in the footer when using a child theme; it refers to the core-folder in the child directory without failover to the responsive-directory in case it doesn’t exist.
A symbolic link would fix this symptom.
August 20, 2013 at 1:49 am #119218
Thanks Pong, I’ll forward to development.
August 22, 2013 at 3:23 am #119648
This is fixed and will be in the next update.
You must be logged in to reply to this topic.