Encoding issues with custom CSS

  • Resolved Helmut Wandl

    (@ehtmlu)


    1 year, 8 months ago

    Hi,

    thank you for this great plugin.

    Unfortunately, the custom CSS field is only of limited use because the CSS is incorrectly encoded. Incorrect HTML entities and unnecessary backslashes lead to syntax errors.

    Example:

    .gt_switcher-popup > span { background-image: url("image.jpg"); }

    results in:

    .gt_switcher-popup > span { background-image: url(\"image.jpg\"); }

    Therefore, the characters >, " and probably a few others are not usable.

    It would be great if this could be fixed, as I generally like that I can specify the CSS directly in the plugin and don’t have to outsource it somewhere else.

    Thank you and best regards,
    Helmut

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author edo888

    (@edo888)

    1 year, 8 months ago

    Hi,

    I believe you can simply leave out > and ” special characters and it will be fine.

    If for some reason you must have them, feel free to place the additional CSS in some file. Usually additional customizations are done in style.css file in your child theme.

    Thanks! 🙂

    • This reply was modified 1 year, 8 months ago by edo888.
    Thread Starter Helmut Wandl

    (@ehtmlu)

    1 year, 8 months ago

    Thank you for your response. In my case I need the special characters because I would like to add an svg data URL as background image. However, of course I can place it anywhere else. I was just hoping I could use the custom CSS field for my custom CSS as well 🤪

    Thanks anyway

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Encoding issues with custom CSS’ is closed to new replies.