<p>"Source" is in the context of "where an element is pulling its data from".</p>

<p>The easiest example is with <a href="http://buildwithcraft.com/docs/assets" rel="nofollow">Assets</a>, because they have easily defined Asset Sources settings portion of the control panel, but all elements (entries, tags, categories, users, etc.) have sources behind the scenes.</p>

<p>See the <a href="https://github.com/pixelandtonic/CategorySources" rel="nofollow">CategorySources</a> plugin for an example of how it might be used (including a screenshot).</p>

CC BY-SA 3.0
2015-02-08T19:53:57.563Z
I guess my question is more specific in regards [this question](http://craftcms.stackexchange.com/questions/7044/editorial-workflow-custom-status) and whether modifying EntrySources would affect the status drop-down menu in the Entry List view in any way?
Douglas McDonald
CC BY-SA 3.0
2015-02-08T20:53:36.837Z
Hehe, this is exactly what I guessed (read hoped) 'modifyEntrySources' does when I read the release notes last week. 'modifyEntrySortableAttributes' is pretty much useless in most cases for me, without being able to define it per section (source?).
carlcs
CC BY-SA 3.0
2015-02-09T22:26:57.890Z
@Douglas the hook makes this possible: https://github.com/pixelandtonic/CategorySources/
carlcs
CC BY-SA 3.0
2015-02-10T01:03:06.493Z
@carlcs Thank you. That's the same link that brad posted above. But I did install it this time to see what it does. Still confused though. I looked at the code and can see that it added the categories to my entry sources, but how does that help me? No change to the CP that I can tell. Does this give me some new capability on the template side?
Douglas McDonald
CC BY-SA 3.0
2015-02-10T08:42:51.633Z
Ouups.. I should start reading SE post completely again. Totally missed Brad's last sentence, @Douglas!
carlcs
CC BY-SA 3.0
2015-02-08T19:43:11.430Z
2015-02-08T19:43:11.430Z
Brad Bell
<p>What does the <a href="http://buildwithcraft.com/docs/plugins/hooks-reference#modifyEntrySources" rel="nofollow">modifyEntrySources</a> hook do exactly, and when might one use it? Can someone help clarify this please?</p>

<plugin-development><hook>
What does the 'modifyEntrySources' hook do?
# What does the 'modifyEntrySources' hook do?

(Asked by: username_0 on 2015-02-08)

What does the [modifyEntrySources](http://buildwithcraft.com/docs/plugins/hooks-reference#modifyEntrySources) hook do exactly, and when might one use it? Can someone help clarify this please?

**Tags:** plugin-development, hook

---

## 1 answers

### Answer by username_1 on 2015-02-08. Score: 2 | Accepted answer

"Source" is in the context of "where an element is pulling its data from".

The easiest example is with [Assets](http://buildwithcraft.com/docs/assets), because they have easily defined Asset Sources settings portion of the control panel, but all elements (entries, tags, categories, users, etc.) have sources behind the scenes.

See the [CategorySources](https://github.com/pixelandtonic/CategorySources) plugin for an example of how it might be used (including a screenshot).

> **Comments:**
> **username_0**: I guess my question is more specific in regards [this question](http://craftcms.stackexchange.com/questions/7044/editorial-workflow-custom-status) and whether modifying EntrySources would affect the status drop-down menu in the Entry List view in any way?  
> **username_2**: Hehe, this is exactly what I guessed (read hoped) 'modifyEntrySources' does when I read the release notes last week. 'modifyEntrySortableAttributes' is pretty much useless in most cases for me, without being able to define it per section (source?).  
> **username_2**: @Douglas the hook makes this possible: https://github.com/pixelandtonic/CategorySources/  
> **username_0**: @carlcs Thank you. That's the same link that brad posted above. But I did install it this time to see what it does. Still confused though. I looked at the code and can see that it added the categories to my entry sources, but how does that help me? No change to the CP that I can tell. Does this give me some new capability on the template side?  
> **username_2**: Ouups.. I should start reading SE post completely again. Totally missed Brad's last sentence, @Douglas!  

---

