# Suppression boutons impossible

**URL:** <https://forums.realmacsoftware.com/t/suppression-boutons-impossible/45627>\
**Category:** RapidWeaver Elements\
**Created:** [December 15, 2024, 11:03am UTC](https://forums.realmacsoftware.com/t/suppression-boutons-impossible/45627 "2024-12-15T11:03:07Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jean-Marc](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/jean-marc/32/26097_2.png) [@Jean-Marc](https://forums.realmacsoftware.com/u/Jean-Marc)\
**Post date:** [December 15, 2024, 11:03am UTC](https://forums.realmacsoftware.com/t/suppression-boutons-impossible/45627/1 "2024-12-15T11:03:07Z")

</div>

RapidWeaver Elements b27 (23161)  
Après la fermeture d"Elements, à la réouverture, cela à généré 2 boutons qu’il m’est impossible de supprimer.  
Bon dimanche les amis.

 ![Capture d’écran 2024-12-15 à 11.54.55](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/b/0/b076b5f64f39b02ed867a1c405d543c0971afa76.png)

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [December 15, 2024, 3:34pm UTC](https://forums.realmacsoftware.com/t/suppression-boutons-impossible/45627/2 "2024-12-15T15:34:02Z")

</div>

Can you share the project with us via Elements Cloud?

---

<div class="post-metadata">

**Author:** ![Jean-Marc](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/jean-marc/32/26097_2.png) [@Jean-Marc](https://forums.realmacsoftware.com/u/Jean-Marc)\
**Post date:** [December 15, 2024, 3:50pm UTC](https://forums.realmacsoftware.com/t/suppression-boutons-impossible/45627/3 "2024-12-15T15:50:42Z")

</div>

elementsapp://downloadDocument/7CboHtQF1UIH

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [December 15, 2024, 3:59pm UTC](https://forums.realmacsoftware.com/t/suppression-boutons-impossible/45627/4 "2024-12-15T15:59:00Z")

</div>

Thanks, this certainly looks like a bug, we’ll look into it and get it fixed.

In the meantime, just unlink them from a Global and then you should be able to delete them!

---

<div class="post-metadata">

**Author:** ![thominator](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/thominator/32/35233_2.png) [@thominator](https://forums.realmacsoftware.com/u/thominator)\
**Post date:** [December 15, 2024, 4:09pm UTC](https://forums.realmacsoftware.com/t/suppression-boutons-impossible/45627/5 "2024-12-15T16:09:45Z")

</div>

I found the same thing with SVG in your menus. You can’t get rid of the SVG (and it didn’t like my Adobe-created SVGs anyway), and if you drag it out or start fiddling with the Global, you can get into a state where you can’t remove it. As you note, Unlink from Global is the workaround, at which point you can remove it.

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [December 15, 2024, 5:35pm UTC](https://forums.realmacsoftware.com/t/suppression-boutons-impossible/45627/6 "2024-12-15T17:35:05Z")

</div>

> [@thominator](#):
>
> You can’t get rid of the SVG (and it didn’t like my Adobe-created SVGs anyway),

SVG’s are code based, so sometimes you have to tweak the output to get them to work the way you want on the web (this isn’t unique to Elements).

Take a look at the [SVG Component Docs](https://docs.realmacsoftware.com/elements-docs/elements-app/components/built-in-components/svg), it contains some advice on how to get size and colour working.

> [@thominator](#):
>
> if you drag it out or start fiddling with the Global, you can get into a state where you can’t remove it. As you note, Unlink from Global is the workaround, at which point you can remove it.

Thanks for the report, we’ll get this fixed in the next beta or two!
