I am usin wordpress 3.6 and both files style.css and custom.css are in directory: /public_html/wp-content/themes/iconic-one
my custom.css:
/*
Theme Name: Themonic
Custom CSS Template for Iconic One.
*/
a {
color: #007CC2;
font-size: 15px;
text-decoration: none;
}
.entry-header .entry-title a {
color: #007CC2;
font-size: 28px;
margin-bottom: 20px;
text-decoration: none;
}
.entry-header .entry-title {
color: #007CC2;
font-size: 28px;
margin-bottom: 20px;
text-decoration: none;
}
hgroup a {
color: #000000;
font-size: 34px;
font-weight: bold;
padding-left: 10px;
text-decoration: none;
}
.widget-title {
color: #000000;
font-size: 16px;
}
.widget-area .widget a {
color: #007CC2;
font-size: 98%;
text-decoration: none;
}
a.comment-reply-link, a.comment-edit-link {
color: #007CC2;
font-size: 13px;
line-height: 1.84615;
}
blockquote {
margin: 1em 3em;
color: #999;
border-left: 2px solid #999;
padding-left: 1em;
}
.avatar {
-moz-border-radius: 50%;
-webkit-border-radius: 50%;
border-radius: 50%;
height: 40px;
width: 40px;
}
.socialmedia img {
border: 2px solid #CCCCCC;
border-radius: 18px;
}
Thanks.
Hi I think i found it.
Sometimes to obvious to see at first time.
I have to put the file in root directory or i have to make a redirect to directory /wp-content/themes/iconic-one/custom.css
In the file style.css i have : @import url(“/custom.css”);
But the custom.css file are in the theme folder /wp-content/themes/iconic-one/custom.css
Thanks.
By the way the theme is excelent. Will buy pro version.
I modified the style.css line to:
@import url("custom.css");
Hi Ajay,
So simple !
That’s it.
Is that the best way isn’t it ?
I have to manage the 404 errors !
Can you give me some advice ?
I am using 404 Redirect plugin.
Thanks
I had SEO Ultimate installed which monitors 404s. The 404 Redirect is good if you’re aware of the 404s.
I think the best way is what I did above. The issue is that they upgraded the theme without fixing this error.
Another option is to dump a blank custom.css in your root directory.
Hello Guys,
This issue has been noted and it will be fixed in the next version very soon.
Regards
Thank you! Glad to hear this 🙂