Home>Support>Found a issue in custom css

Found a issue in custom css

Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].

Hello,
I think I have found a issue abou custom css.
If you use @import… in custom css and save it,you won’t be able to click the eye icon untill you remove the @import code.
I use the vantage theme.

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 9 years, 20 days ago Andrew Misplon
    Hi, I Work Here

    Hi 派斯克國際有限公司

    Thanks for reaching out. I’ve tried to replicate the issue but haven’t been able to. Can you perhaps send the import statement used?

  2. 9 years, 15 days ago 派斯克國際有限公司

    Hello,I use these two lines:
    @import “https://fonts.googleapis.com/css?family=Shrikhand”;
    @import “https://x-wind.pask.com.tw/drawing.css”;

    and another funny thing:
    if you just use “@import…” for one line, and the eye-icon will be clickable again.

    thank you

  3. 9 years, 14 days ago Alex S
    Hi, I Work Here

    Hi 派斯克國際有限公司,

    To clarify, are you using those exact quotation marks (being smart quotes)? If so, that’s the problem. You’ll need to use dumb quotes (although known as straight quotes) – which are ‘ or ” For reference, please refer to this article.

  4. 9 years, 14 days ago 派斯克國際有限公司

    Hi, thanks for your replying.
    It is still not working by using dumb quotes,
    and I change them to:
    @import url(https://fonts.googleapis.com/css?family=Shrikhand);
    @import url(https://x-wind.pask.com.tw/drawing.css);
    the eye-icon is still unenterable if you keep using @import for more than one line.

  5. 9 years, 13 days ago Alex S
    Hi, I Work Here

    Hi 派斯克國際有限公司,

    Okay so I was able to replicate the issue you’ve described. I’ve logged this as a bug in our issue tracker. We’ll investigate this and try come up with a fix in (hopefully) the next version.

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More