Title: Bug: Version 3.4.9 Breaks CSS Encoding
Last modified: March 2, 2023

---

# Bug: Version 3.4.9 Breaks CSS Encoding

 *  Resolved [lulech23](https://wordpress.org/support/users/lulech23/)
 * (@lulech23)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/bug-version-3-4-9-breaks-css-encoding/)
 * 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:
 *     ```wp-block-code
       #parent > .child {}
       ```
   
 * This will be output to the page as:
 *     ```wp-block-code
       #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](https://wordpress.org/support/users/wpmudevsupport13/)
 * (@wpmudevsupport13)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/bug-version-3-4-9-breaks-css-encoding/#post-16523558)
 * Hi [@lulech23](https://wordpress.org/support/users/lulech23/)
 * There was amandatory security improvement, as demanded by wordpress.org 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](https://wordpress.org/support/users/wpmudevsupport12/)
 * (@wpmudevsupport12)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/bug-version-3-4-9-breaks-css-encoding/#post-16640275)
 * Hi [@lulech23](https://wordpress.org/support/users/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](https://wordpress.org/support/users/lulech23/)
 * (@lulech23)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/bug-version-3-4-9-breaks-css-encoding/#post-16640511)
 * 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.

 * ![](https://ps.w.org/branda-white-labeling/assets/icon-256x256.gif?rev=3407049)
 * [Branda – White Label & Branding, Free Login Page Customizer](https://wordpress.org/plugins/branda-white-labeling/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/branda-white-labeling/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/branda-white-labeling/)
 * [Active Topics](https://wordpress.org/support/plugin/branda-white-labeling/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/branda-white-labeling/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/branda-white-labeling/reviews/)

## Tags

 * [css](https://wordpress.org/support/topic-tag/css/)

 * 3 replies
 * 3 participants
 * Last reply from: [lulech23](https://wordpress.org/support/users/lulech23/)
 * Last activity: [3 years, 1 month ago](https://wordpress.org/support/topic/bug-version-3-4-9-breaks-css-encoding/#post-16640511)
 * Status: resolved