<p>There's a 99% chance you're running into a case-sensitivity issue on your file system.</p>

<p>Check your plugin's name, the handle and the action URL for the controller you're trying to hit.</p>

<p>Most likely locally, you've got a case insensitive file system, so it doesn't matter that <code>pluGiNHanDlE</code> is not equal to <code>pluginHandle</code>, but on staging it's case sensitive so it does.</p>

CC BY-SA 3.0
2017-01-31T12:30:35.110Z
Thanks Brad... but I pushed the same plugin files to staging and copying the same URI from localhost :(.
Bhashkar Yadav
CC BY-SA 3.0
2017-01-31T18:21:54.517Z
If it's a case sensitivity problem, that would address the issue, though.  Check the names of your plugin files vs. the names of the classes they are declaring.
Brad Bell
CC BY-SA 3.0
2017-01-31T05:23:03.410Z
2017-01-31T05:23:03.410Z
Brad Bell
<p>I created a plugin to schedule some custom email notifications. The action URL is working perfectly on localhost but isn't working on stagings server. Is it related to any server stuff.</p>

<plugin-development><controller><elementaction>
Plugin's action URL not working and showing 404 error
# Plugin's action URL not working and showing 404 error

(Asked by: username_0 on 2017-01-31)

I created a plugin to schedule some custom email notifications. The action URL is working perfectly on localhost but isn't working on stagings server. Is it related to any server stuff.

**Tags:** plugin-development, controller, elementaction

---

## 1 answers

### Answer by username_1 on 2017-01-31. Score: 1

There's a 99% chance you're running into a case-sensitivity issue on your file system.

Check your plugin's name, the handle and the action URL for the controller you're trying to hit.

Most likely locally, you've got a case insensitive file system, so it doesn't matter that `pluGiNHanDlE` is not equal to `pluginHandle`, but on staging it's case sensitive so it does.

> **Comments:**
> **username_0**: Thanks Brad... but I pushed the same plugin files to staging and copying the same URI from localhost :(.  
> **username_1**: If it's a case sensitivity problem, that would address the issue, though.  Check the names of your plugin files vs. the names of the classes they are declaring.  

---

