Title: Replace close button (X)
Last modified: February 10, 2023

---

# Replace close button (X)

 *  Resolved [timbergski](https://wordpress.org/support/users/timbergski/)
 * (@timbergski)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/replace-close-button-x/)
 * I’d like to replace the close button (top-right ‘X’) on the cookie consent block,
   with an icon (svg) that I use in the rest of my theme. Is that possible?
 * Thanks
    -  This topic was modified 3 years, 3 months ago by [timbergski](https://wordpress.org/support/users/timbergski/).

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

 *  Plugin Contributor [Jarno Vos](https://wordpress.org/support/users/jarnovos/)
 * (@jarnovos)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/replace-close-button-x/#post-16458724)
 * Hi [@timbergski](https://wordpress.org/support/users/timbergski/),
 * Yes, you could replace the cookie banner HTML with your own, custom template 
   to replace the close icon SVG.
 * The [details are outlined here in section 3.1 & 3.3](https://complianz.io/create-your-own-banner-from-scratch/),
   in short, you will end up with the following files:
    - [/wp-content/mu-plugins/banner.php](https://gist.github.com/jarno-vos/00c78796459ed8dfdd5d5f47acd1a7a8)(
      to override the current template html)
 *  - [/wp-content/mu-plugins/cookiebanner/cookiebanner.php](https://github.com/Really-Simple-Plugins/complianz-gdpr/blob/master/cookiebanner/templates/cookiebanner.php)(
      the cookie banner HTML, that you can now edit to replace the SVG).
 * ![](https://i0.wp.com/i.gyazo.com/4febbf3edbff3ed11fd1bbbabd84b2be.png?resize
   =222%2C98&ssl=1)
 * Kind regards, Jarno
 *  Thread Starter [timbergski](https://wordpress.org/support/users/timbergski/)
 * (@timbergski)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/replace-close-button-x/#post-16458771)
 * Thanks. I don’t have a directory wp-content/mu-plugins currently. Presumably 
   if I create it, and place my new template in it at that location, it won’t be
   overwritten if I upgrade the plugin?
 *  [Kim van Dijk](https://wordpress.org/support/users/kimvdijk/)
 * (@kimvdijk)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/replace-close-button-x/#post-16459172)
 * Hi [@timbergski](https://wordpress.org/support/users/timbergski/),
 * Yes, you can create this folder yourself. That is why we recommend this way so
   that you can update the plugin without disturbing these files. Read more about
   the mu-plugins folder in these articles: [https://complianz.io/adding-filters-with-mu-plugins-quick-easy/](https://complianz.io/adding-filters-with-mu-plugins-quick-easy/)
   and [https://complianz.io/set-cookies-on-root-domain-mu-plugin/](https://complianz.io/set-cookies-on-root-domain-mu-plugin/)
   to help you understand the functionality better.
 * Kind regards, Kim van Dijk
 *  Thread Starter [timbergski](https://wordpress.org/support/users/timbergski/)
 * (@timbergski)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/replace-close-button-x/#post-16459654)
 * Thanks, I’ve done it; the change was very straightforward – well done for making
   such a customisable system.

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

The topic ‘Replace close button (X)’ 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
 * 3 participants
 * Last reply from: [timbergski](https://wordpress.org/support/users/timbergski/)
 * Last activity: [3 years, 3 months ago](https://wordpress.org/support/topic/replace-close-button-x/#post-16459654)
 * Status: resolved