<p>Turns out I had a capitalization typo in my plugin php file name.</p>

<p><code>myPlugin.php</code></p>

<p><code>class MyPlugin ...</code></p>

<p>Renaming the file to <code>MyPlugin.php</code> solved it. (capitial M)</p>

<p>So it would seem that the file and class name need to match exactly.</p>

CC BY-SA 3.0
2014-10-08T23:34:08.267Z
Indeed they do. :) [Here are the full specs on where to use which casing...](http://buildwithcraft.com/docs/plugins/setting-things-up)
Lindsey D
CC BY-SA 3.0
2014-10-08T23:29:51.303Z
2014-10-08T23:29:51.303Z
Henry
<p>Make sure that the name of your plugin directory is all lowercase:</p>

<pre><code>/craft/plugins/myplugin
</code></pre>

<p>On some systems, the capitalization doesn't matter, but on other systems it makes a difference. (<a href="https://craftcms.stackexchange.com/a/1537/45">related</a>)</p>

CC BY-SA 3.0
2014-10-08T23:30:35.010Z
Turns out it was the class name. I've posted that below.
Henry
CC BY-SA 3.0
2014-10-08T23:27:40.113Z
2014-10-08T23:27:40.113Z
2017-04-13T12:51:00.303Z
Lindsey D
<p>for me was the file</p>

<pre><code>vendor/craftcms/plugins.php
</code></pre>

<p>it was referencing a wrong class name due to refactor error (plugin development)</p>

CC BY-SA 4.0
2020-03-07T22:09:09.227Z
2020-03-07T22:09:09.227Z
Leo Leoncio
<p>I have created my own plugin. It works on my Mac but when I try to enabled it in my Debian server it shows as Disabled with a red dot. What's the best way to debug this?</p>

<p>I have not found anything particularly illuminating in the logs yet.</p>

<plugin-development><plugins>
Plugin won't enable
# Plugin won't enable

(Asked by: username_0 on 2014-10-08)

I have created my own plugin. It works on my Mac but when I try to enabled it in my Debian server it shows as Disabled with a red dot. What's the best way to debug this?

I have not found anything particularly illuminating in the logs yet.

**Tags:** plugin-development, plugins


---

## 3 answers

### Answer by username_0 on 2014-10-08. Score: 6

Turns out I had a capitalization typo in my plugin php file name.

`myPlugin.php`

`class MyPlugin ...`

Renaming the file to `MyPlugin.php` solved it. (capitial M)

So it would seem that the file and class name need to match exactly.

> **Comments:**
> **username_1**: Indeed they do. :) [Here are the full specs on where to use which casing...](http://buildwithcraft.com/docs/plugins/setting-things-up)  

---

### Answer by username_1 on 2014-10-08. Score: 4

Make sure that the name of your plugin directory is all lowercase:
/craft/plugins/myplugin

On some systems, the capitalization doesn't matter, but on other systems it makes a difference. (related)

> **Comments:**
> **username_0**: Turns out it was the class name. I've posted that below.  

---

### Answer by username_2 on 2020-03-07. Score: 1

for me was the file
vendor/craftcms/plugins.php

it was referencing a wrong class name due to refactor error (plugin development)


---

