2

In reply to: new font

#27416

Yes, thank you – I had expected those things to need re-loading etc. But what I saw when I previewed the child theme activation involved many more items; sidebar was gone, but widgets from the sidebar were stacked below the home page, all icons for the social media buttons above the header were gone, replaced by overlapping lines of text – and many more things gone haywire. Here’s what I’m going to do: create an export file for the entire site, then create a subdomain, then import files to the subdomain, then create and activate a child theme, then place all the custom css from the current Graphene options into the child theme, remove same from the Graphene options, and then test everything out. If I can make the subdomain site, using the child theme, look like the emain site, I’ll move the subdomain site into the main domain.

In future, I’m creating a child theme right off the bat for new sites!

In reply to: new font

#27414

Oh – the website in question is dhanaecokids.com. Thanks again.

In reply to: new font

#27413

Thanks for your step-by-step video on how to create a child theme. I get it and I’m going to do so from now on; I have 4 new websites to design and will definitely start with a child theme for each one.

However, for the website I’ve just about finished (except for the issue of the font I want to add and use for sidebar h2, page and post titles, and page and post h1,

I set up a child theme and then clicked on preview… and when I did, I expected the custom header, custom menu, and background image to be gone as noted in one of your other posts, but there was so much more out of whack: Everything was crazy on the display; front page sidebars gone and stacked down below everything on the page, social media buttons above the header turned into strings of text…so much more. All these are things that aren’t controlled by the custom css currently on the main graphene theme. I’m afraid if I activate this child theme I’ll essentially have to do my site over. So I think I’ll just make the child theme Step #1 for all future websites.

When you activate a child theme, then do all the choices made under Graphene options go away such that you have to do them all over again?

Thank you.

In reply to: new font

#27411

Wow. OK. Thank you. Biting the bullet and doing it now.

In reply to: can I "degrade" or "tear" edges of content areas?

#27379

Very cool. I’m going to try having my graphic designer create a tiled image matching the background color of my page body, post body, and sidebar containers. Then once I get an image file for the tile, can you explain how to insert it in the border property in css? Again, thank you much.

In reply to: new font

#27409

Sadly, no. I’ve read directions for doing so but haven’t understood the process well enough to try it. Is there a “how to set up a child theme for dummies” doc or video I can consult?

In reply to: Background for post content, page content, sidebar content

#27406

Thank you. I was able to make some other backgrounds (main wrapper) totally transparent by using the word transparent instead of a color code. But, I don’t know how to make a gradient instead of a color or total transparency. I’m trying to make the backgrounds display at 85% screen under the total text/image area and then fade out to transparent at the edges. Also I know it’s best practice to create a child theme but I haven’t mastered how to do that yet – so will this work if I simply add the code to the custom CSS area under Graphene options? Thank you so much.