Bug: Version 3.4.9 Breaks CSS Encoding

  • Resolved lulech23

    (@lulech23)


    3 years, 2 months ago

    Installed the latest Branda update today and immediately noticed that some of my admin CSS rules were not applying. Digging a bit deeper, I found that the latest update (3.4.9) is encoding special characters as HTML. For example, if I have a rule:

    #parent > .child {}

    This will be output to the page as:

    #parent > .child {}

    Downgrading the plugin back to 3.4.8.1 restored the correct encoding.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Kris – WPMU DEV Support

    (@wpmudevsupport13)

    3 years, 2 months ago

    Hi @lulech23

    There was amandatory security improvement, as demanded by ww.wp.xz.cn for any plugin that is available via the free plugin repository. This is unfortunately a very strict rule that all plugins there need to follow (not allowing unfiltered HTML to be added), even if there are cases like this one where allowing script tags is the key. Following this it seems “>” was affected in CSS module.

    I already pinged our Branda Team to review that and fix that in next version.

    Kind Regards,
    Kris

    Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    3 years, 1 month ago

    Hi @lulech23

    I hope you are doing well and safe!

    We haven’t heard from you in a while, I’ll mark this thread as resolved.

    Feel free to let us know if you have any additional questions or problems.

    Best Regards
    Patrick Freitas

    Thread Starter lulech23

    (@lulech23)

    3 years, 1 month ago

    Hi Patrick,

    I can confirm that the latest updates have solved this issue! Thanks for the fix.

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

The topic ‘Bug: Version 3.4.9 Breaks CSS Encoding’ is closed to new replies.

Tags