• After upgrading to the latest version, my custom CSS has stopped working. Viewing the page source shows me that the CSS is getting-html escaped, so double quotes and > are not working.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi worriedguy,

    Thanks for using our plugin.
    Can you please provide a screenshot and URL. the custom CSS where you applied for and your custom CSS code so we can check and fix as well.

    Thanks

    Thread Starter worriedguy

    (@worriedguy)

    I am having some trouble making a screenshot, but what I save in the plugin “Custom CSS” text box (under “login form setting”) looks like this:

    form[name=”loginform”] > p:nth-of-type(1), form[name=”loginform”] > p:nth-of-type(2), form[name=”loginform”] .forgetmenot, form[name=”loginform”] .submit {
    display: none;
    }

    When I do “view source” on the login form, I see that the CSS has turned into this:

    form[name=\"loginform\"] > p:nth-of-type(1), form[name=\"loginform\"] > p:nth-of-type(2), form[name=\"loginform\"] .forgetmenot, form[name=\"loginform\"] .submit {
    display: none;
    }

    (i.e. So I’m complaining about the “\"” and the “>” )

    This exact CSS used to work fine in an earlier release of the plugin. It broke after I upgraded a week or two back.

    After saving the custom CSS if I go back to the settings page later, I do see that “\” has been inserted before every “]”. I don’t know if that was happening in the earlier version as I had not paid much attention until it broke.

    Thanks!

    Thread Starter worriedguy

    (@worriedguy)

    Ugh. Now I see why you wanted a screenshot. The cut and pasted CSS got munched by the software that handles the messages. Let me try harder to get some screenshots…

    Thread Starter worriedguy

    (@worriedguy)

    I’ve uploaded two screenshots here.

    The first one shows what I see in the plugin settings AFTER saving and returning. When I entered the CSS into the settings, the backslashes before each quote mark were not there. I’m not sure if they’re a problem, but they might be.

    The second shot (black background) shows what I see when I view source on the web page. You can see that html escaping has been applied to the CSS I entered so all of the quotation marks and greater than signs have been escaped.

    The original CSS I entered was working fine with an earlier version of the plugin. It broke after I upgraded 2 weeks ago.

    Since I also upgraded some other plugins at the same time, it’s possible that some other plugin is doing the escaping, but I don’t think so as I’m not having any problems with CSS on other pages.

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

The topic ‘Custom CSS getting html-escaped …’ is closed to new replies.