<p>That message comes from from <a href="https://github.com/pixelandtonic/Garnish/blob/master/Source/classes/Select.js" rel="nofollow">Garnish.Select</a>, when the same DOM element is associated with two separate Garnish.Select instances. The JS will log that message right before destroying the first Garnish.Select instance.</p>

<p>It’s not necessarily a bad thing, but could be an indication of something in your JS that could be improved. (Craft’s own JS causes several of those messages, so don’t worry too much about it if everything seems to be working correctly.)</p>

CC BY-SA 3.0
2014-06-26T08:49:17.757Z
Perfect, thanks Brandon. Then I won't worry about it too much, since everything else seems to be working normally. :)
Lindsey D
CC BY-SA 3.0
2014-06-26T07:25:00.840Z
2014-06-26T07:25:00.840Z
Brandon Kelly
<p>My plugin has a field type. When I'm editing an entry which uses that field type, this message gets logged to the console:</p>

<pre><code>Element was added to more than one selector
</code></pre>

<p>I can tell that it's Garnish which is generating this message, but <strong>what does it mean?</strong> Is it a problem that needs to be fixed? And if so, how would I go about fixing it?</p>

<plugin-development><fieldtypes><garnish>
Is this Garnish message bad? "Element was added to more than one selector"
# Is this Garnish message bad? "Element was added to more than one selector"

(Asked by: username_0 on 2014-06-26)

My plugin has a field type. When I'm editing an entry which uses that field type, this message gets logged to the console:
Element was added to more than one selector

I can tell that it's Garnish which is generating this message, but what does it mean? Is it a problem that needs to be fixed? And if so, how would I go about fixing it?

**Tags:** plugin-development, fieldtypes, garnish


---

## 1 answers

### Answer by username_1 on 2014-06-26. Score: 4 | Accepted answer

That message comes from from [Garnish.Select](https://github.com/pixelandtonic/Garnish/blob/master/Source/classes/Select.js), when the same DOM element is associated with two separate Garnish.Select instances. The JS will log that message right before destroying the first Garnish.Select instance.

It’s not necessarily a bad thing, but could be an indication of something in your JS that could be improved. (Craft’s own JS causes several of those messages, so don’t worry too much about it if everything seems to be working correctly.)

> **Comments:**
> **username_0**: Perfect, thanks Brandon. Then I won't worry about it too much, since everything else seems to be working normally. :)  

---

