CSS Customization Error

riversideassembly · Member · Oct 18, 2014 at 2:43 pm
Copy link

Add topic to favorites
Hey, all I’m trying to do is change the color of a particular font on the sidebar widget. Easy enough, except when I change the color, copy and paste the CSS into the CSS editor and save, it gives me an error which reads:

Font from origin ‘https://s1.wp.com’ has been blocked from loading by Cross-Origin Resource Sharing policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘https://myriversideassembly.wordpress.com’ is therefore not allowed access.

And the color remains the same. Is this a problem with allowing the original theme CSS to remain active? I would think changing the color of the text wouldn’t be something the main theme CSS would be stuck on.

The blog I need help with is: (visible only to logged in users)
hallluke · Member · Oct 18, 2014 at 2:52 pm
Copy link
Could you paste the CSS code you have tried to use here between backticks (or click the code button just above the comment box) so we can investigate what the problem might be.

If you’re trying to change the contact details to be the same grey colour you should be able to use this:
```
#secondary .confit-phone,
#secondary .confit-hours {
  color:#DBDBDB;
}
```
You should also delete this part of your existing custom CSS as it’s not formatted properly and might be causing issues too:

media="all"
thesacredpath · Member · Oct 18, 2014 at 2:53 pm
Copy link
Hi there, can you paste the CSS you are trying to use here in the forums between code tags like this:
<code>put code here</code>

We can then take a look at it and also try that code in our test sites.
thesacredpath · Member · Oct 18, 2014 at 2:53 pm
Copy link
@hallluke was faster than me. :)
designsimply · Member · Nov 14, 2014 at 4:22 pm
Copy link
The warning message you mentioned earlier doesn’t look to me like it’s related to pasting CSS to me, or perhaps that’s a separate issue.

If the CSS you’re adding disappears when you try to save it, then it does sound like there might be a syntax error in the CSS itself. If you paste the example here as hallluke and thesacredpath suggested earlier, we can try to take a closer look at it for you. If you would prefer to test on you can use the “By direct input” tab on this page to try to validate your CSS:
http://jigsaw.w3.org/css-validator/#validate_by_input

No items found.