<p>My guess is it's a case sensitivity issue with the main plugin class/file name (some operating systems have case sensitive filesystems and some don't).</p>

<p>You can review the requirements for how things should be named here: <a href="https://craftcms.com/docs/plugins/setting-things-up" rel="noreferrer">https://craftcms.com/docs/plugins/setting-things-up</a></p>

<p>Or better yet, use a site like <a href="https://pluginfactory.io/" rel="noreferrer">https://pluginfactory.io/</a> to generate the boilerplate plugin code for you and compare it to what you have.</p>

CC BY-SA 3.0
2016-04-29T16:49:07.200Z
2016-04-29T16:49:07.200Z
Brad Bell
<p>In this instance all of the file names and database were correct.</p>

<p>We had not run our composer dump-autoload script in several months since we updated the name which caused this issue.</p>

CC BY-SA 3.0
2016-04-29T18:28:17.707Z
2016-04-29T18:28:17.707Z
Exziled
<p>I'm attempting to enable a plugin from within the Craft control panel but I am unable to do so. It shows Disabled and when I click "Enable" it shows "Plugin Enabled" at the top but still shows disabled below and will not enable.</p>

<p>I'm not getting any errors reported and it seems to work on other environments just will not work now?</p>

CC BY-SA 3.0
2016-04-29T16:56:56.943Z
Related: http://craftcms.stackexchange.com/questions/3023/plugin-wont-enable
Lindsey D
<plugins><control-panel>
Cannot enable Craft plugin in control panel
# Cannot enable Craft plugin in control panel

(Asked by: username_0 on 2016-04-29)

I'm attempting to enable a plugin from within the Craft control panel but I am unable to do so. It shows Disabled and when I click "Enable" it shows "Plugin Enabled" at the top but still shows disabled below and will not enable.

I'm not getting any errors reported and it seems to work on other environments just will not work now?

**Tags:** plugins, control-panel
> **Comments:**
> **username_1**: Related: http://craftcms.stackexchange.com/questions/3023/plugin-wont-enable  

---

## 2 answers

### Answer by username_2 on 2016-04-29. Score: 5

My guess is it's a case sensitivity issue with the main plugin class/file name (some operating systems have case sensitive filesystems and some don't).

You can review the requirements for how things should be named here: <https://craftcms.com/docs/plugins/setting-things-up>

Or better yet, use a site like <https://pluginfactory.io/> to generate the boilerplate plugin code for you and compare it to what you have.


---

### Answer by username_0 on 2016-04-29. Score: 2

In this instance all of the file names and database were correct.

We had not run our composer dump-autoload script in several months since we updated the name which caused this issue.


---

