In reply to: Add Button in Header or Menu

#12310

I am working on the child theme, and I’m thinking my troubles might be because I’m using the wordpress multisite.

Do you know how I would create a child theme for this purpose?

When I opened the header.php in graphene it had the data for a different site than I wanted to use.

In reply to: Add Button in Header or Menu

#12309

I have activated the graphene child theme I created here: http://putlzebeta.putzle.com/

so you can see what I am doing wrong.

In reply to: Add Button in Header or Menu

#12308

Not now, you are correct ….I changed it back.

I created the child theme and was able to activate it, but when viewing it, everything was like a ‘mirror’ of the original graphene theme.

I then, educated myself on the WordPress site, how to create child themes, and using their example, created the ‘Twenty Ten’ child theme. That also appear as a mirror of the original theme.

Since it was making me dizzy, I changed putzle back.

(everything lines up to the right, including the content, which looks like you are reading backwards but the text is intact, if this makes any sense)

Apparently there is more to creating a child theme than the directions in the tutorial.

Upon reading your comments in the editor of graphene ‘Theme Functions’ you talk about the ‘hooks’.

Is this maybe the part I am missing?

thanks

In reply to: Add Button in Header or Menu

#12306

Thank you. I will try this once I figure out why the child theme I created using your instructions is not quite what it should be.

Please let me know what you think I did wrong here: http://putzle.com (I used this as a test child theme before implementing on the real site.) This is what is in the style.css for the child.

/*

Theme Name: Graphene Child

Theme URI: http: //vikinglodge3683.putzle.com/

Description: Child theme for the Graphene theme

Author: Deb Chabot

Author URI: http: //example.com/about/

Template: graphene

Version: 0.1.0

*/

@import url(“../graphene/style.css”);

/* Your modification goes here */

Thank You, once again.