Problem in version 4.05

  • Resolved Nazar Hotsa

    (@bugnumber9)


    3 years, 2 months ago

    Hello,

    In the latest version 4.05 something has changed in Custom CSS.
    Now CSS rules like “body > .class” are echoed in HTML source like “body > .class” thus no longer work.
    I changed that rule, but I believe custom CSS should allow all CSS ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Alexandru Tapuleasa

    (@talextech)

    Hi,

    Yes, we improved plugin security and we escape HTML tags, meaning < and > will not work anymore in Custom CSS. Since the page structure is rather simple, you should be OK targeting elements without the child combinator, but if you are having difficulty with that let us know ??

    After the last update I also have the same problem with the custom css.

    I had changed this in the custom css field:

    body > .main-container:after {opacity: 0;}
	
.login-form input[type="text"], .login-form input[type="password"] {background-color: #ffffff;}

    and now they don’t work anymore.

    How can I solve the problem?

    Thank you
    Max

    Thread Starter Nazar Hotsa

    (@bugnumber9)

    @gruis28 For the first one try .main-container:after {opacity: 0;} or .main-container:after {opacity: 0 !important;}
    For the second one I think .login-form input {background-color: #ffffff;} should work.

    Thanks @bugnumber9 for the help.

    They only work if you enter !important

    
.main-container:after {opacity: 0 !important;}
.login-form input {background-color: #ffffff !important;}

    Thank you
    Max

    Thread Starter Nazar Hotsa

    (@bugnumber9)

    If we talk about the maintenance page, it’s fine to use the !important modifier, no matter what CSS purists tell you ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Problem in version 4.05’ is closed to new replies.