Title: Issue with editing cookie-statement
Last modified: September 19, 2025

---

# Issue with editing cookie-statement

 *  Resolved [Boudewijn](https://wordpress.org/support/users/wbrooseboom/)
 * (@wbrooseboom)
 * [9 months ago](https://wordpress.org/support/topic/issue-with-editing-cookie-statement/)
 * We are unable to edit the fonts of the [cmplz-document type=”cookie-statement”
   region=”eu”] in DIVI. The page immediately becomes unresponsive when the text
   module is opened. This happens on three different websites in both WP.org and
   WP.com.
 * Any suggestions would be much appreciated.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fissue-with-editing-cookie-statement%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Support [Antonio Candela](https://wordpress.org/support/users/antoiub/)
 * (@antoiub)
 * [9 months ago](https://wordpress.org/support/topic/issue-with-editing-cookie-statement/#post-18648130)
 * Hello [@wbrooseboom](https://wordpress.org/support/users/wbrooseboom/) ,
   Thank
   you for reaching out.
 * The text in the legal documents is loaded directly via the shortcode, so it cannot
   be edited as if it were a normal paragraph. To edit the text itself, you would
   need to de-sync the legal document, as explained in this guide: [https://complianz.io/editing-legal-documents](https://complianz.io/editing-legal-documents).
 * To avoid de-syncing the documents, our recommendation is to apply custom CSS 
   rules instead, since in your case it’s only about fonts.
 * Best regards,
   Antonio
 *  Thread Starter [Boudewijn](https://wordpress.org/support/users/wbrooseboom/)
 * (@wbrooseboom)
 * [9 months ago](https://wordpress.org/support/topic/issue-with-editing-cookie-statement/#post-18648157)
 * Okay thanks, but where should I add those custom CSS rules? Previously I was 
   able to apply those rules to the module with the shortcode. But that is no longer
   possible, because when the module is opened the page brakes immediately. So how
   can I now target the shortcode?
    -  This reply was modified 9 months ago by [Boudewijn](https://wordpress.org/support/users/wbrooseboom/).
    -  This reply was modified 9 months ago by [Boudewijn](https://wordpress.org/support/users/wbrooseboom/).
 *  Plugin Support [Antonio Candela](https://wordpress.org/support/users/antoiub/)
 * (@antoiub)
 * [9 months ago](https://wordpress.org/support/topic/issue-with-editing-cookie-statement/#post-18648169)
 * Hello [@wbrooseboom](https://wordpress.org/support/users/wbrooseboom/) ,
   You 
   can follow Divi’s own guide here: [https://help.elegantthemes.com/en/articles/8357875-how-to-add-custom-css-to-divi](https://help.elegantthemes.com/en/articles/8357875-how-to-add-custom-css-to-divi).
   Best regards, Antonio
 *  Thread Starter [Boudewijn](https://wordpress.org/support/users/wbrooseboom/)
 * (@wbrooseboom)
 * [9 months ago](https://wordpress.org/support/topic/issue-with-editing-cookie-statement/#post-18648174)
 * I’m familiar with that CSS option. I guess I’ll just add a class then. Thanks

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

The topic ‘Issue with editing cookie-statement’ is closed to new replies.

 * ![](https://ps.w.org/complianz-gdpr/assets/icon-256x256.png?rev=2881064)
 * [Complianz - GDPR/CCPA Cookie Consent](https://wordpress.org/plugins/complianz-gdpr/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/complianz-gdpr/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/complianz-gdpr/)
 * [Active Topics](https://wordpress.org/support/plugin/complianz-gdpr/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/complianz-gdpr/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/complianz-gdpr/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [Boudewijn](https://wordpress.org/support/users/wbrooseboom/)
 * Last activity: [9 months ago](https://wordpress.org/support/topic/issue-with-editing-cookie-statement/#post-18648174)
 * Status: resolved