Child Theme not working after upgrade
-
Hi – I love the Graphene template.. Been using it for a couple of years… End of year and trying to upgrade everything… I just upgraded Graphene from 1.8.2 to 1.9.2. And now my child theme files are not being recognized. I also upgraded from WordPress 3.3 to 3.8… Not sure what happened.
#1 – Style.css
I have stuff in my child theme to remove the white borders around images in sidebars, etc, which I had to recreate when I upgraded jetpak!
Any ideas?
website = http://www.paws-n-play.net – You can see white border around “Got a problem” image on home page.
Child theme in Graphene-Child2 folder with Style.css and function.php files and a few others.
This is the code I have to remove the backgrounds: ( “Got a Problem” =#image-3 – Maybe there is a better way to do this???)
/*
Remove all background formats for specific text widget images
*/
#image-2 {
background:transparent;
border: none;
-moz-box-shadow: 0 0 5px transparent;
-webkit-box-shadow: 0 0 5px transparent;
box-shadow: 0 0 5px transparent;
}
#image-3 {
background:transparent;
border: none;
-moz-box-shadow: 0 0 5px transparent;
-webkit-box-shadow: 0 0 5px transparent;
box-shadow: 0 0 5px transparent;
}
#text-6 {
background:transparent;
border: none;
-moz-box-shadow: 0 0 5px transparent;
-webkit-box-shadow: 0 0 5px transparent;
box-shadow: 0 0 5px transparent;
}#2 functions.php
The only thing I use child functions.php for is to create a list links function to auto display/list all the info in my defined links. It used to work before the upgrade.
Code in my function.php
<?php
// add the filter for links page. On a new page set Slug = list-links
add_filter ('the_content', 'jl_add_links');
function jl_add_links ($content) {
if (!(is_page('list-links'))) return $content;
$content .= wp_list_bookmarks('category_before=&category_after=&title_before=<h3>&title_after=</h3>&show_images=0;&show_images=1;&show_description=1&echo=0');
return $content;
}
?>Now when I click on my Links menu, I just get blank body… So it is not pulling anything from my link definitions…
Any ideas on this one? Maybe also related to the overall child theme files/functions not being recognized after the upgrade?
Thanks in advance! –Mic
Mod
Live and learn: you should never upgrade more than one thing at a time, else it’s difficult to see where problems arise. We all learn this one the hard way, it seems.
Quote:And now my child theme files are not being recognized.I don’t see that you are using a child theme. Have you gone into themes and reselected your child theme?
Quote:Maybe there is a better way to do this???Yes, you can group multiple selectors with commas:
#image-2, #image-3, #text-6 {
background:transparent;
border: none;
-moz-box-shadow: 0 0 5px transparent;
-webkit-box-shadow: 0 0 5px transparent;
box-shadow: 0 0 5px transparent;
}As far as your links are concerned, possible the upgrade from WP 3.3 to 3.8 had something to do with it. (That’s quite a few upgrades to skip!)
You might want to read this:
http://codex.wordpress.org/Links_Manager
Quite frankly, I’ve always found the links manager to be a headache when I need a simple list of links on a page or a text widget. It’s much easier to just add them manually to the page. (And saves the server overhead of one more function.)
I have deleted your other post in “Talk”. Put code in between backtick (
Code:`) characters. It’s usually located above the Tab key on your keyboard.
Mod
As a follow-up, does any of this function correctly if you disable JetPack?
Hi Ken… You were right, my child theme was not activated…. I had activated it, but then switched back to Graphene, when I couldn’t get it working, then everything crashed and I had to have the site restored last night. Now I just activated the child theme again and everything that was broken is fixed! DOH! I will take your advice and stream line the background syntax…
Thank you sooo much for your assistance! You can close this topic…
Mod
Marking thread as resolved. You can do this yourself as well.
Viewing 5 posts - 1 through 5 (of 5 total)
- You must be logged in to reply to this topic.