# plugins search path

**URL:** https://discourse.paraview.org/t/plugins-search-path/6080
**Category:** Development
**Created:** [December 16, 2020, 6:19pm UTC](https://discourse.paraview.org/t/plugins-search-path/6080 "2020-12-16T18:19:26Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![jfavre](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/j/b5ac83/32.png) [@jfavre](https://discourse.paraview.org/u/jfavre)
#### Post date: [December 16, 2020, 6:19pm UTC](https://discourse.paraview.org/t/plugins-search-path/6080/1 "2020-12-16T18:19:26Z")

</div>

The Plugin Manager tells me that plugins are automatically searched for in \<INSTALL\_PATH\>/bin/plugins, however everywhere I compile and install ParaView, plugins are placed in \<INSTALL\_PATH\>/lib64/paraview-5.9/plugins.

So my question is, is the message above hardwired for “bin/plugins”, and if not, wouldn’t “lib64/paraview-5.9/plugins” be the more logical place to search for?

this might be aesthetic only, since it does find the plugins. Their location is listed as bin/…/lib64/paraview-5.9/plugins. 😉 Am I just being picky? Sorry.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [December 17, 2020, 12:07pm UTC](https://discourse.paraview.org/t/plugins-search-path/6080/2 "2020-12-17T12:07:55Z")

</div>

This is an oversight, this string should have been updated manually.

Could you open an issue ?

---

<div class="post-metadata">

### Author: ![jfavre](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/j/b5ac83/32.png) [@jfavre](https://discourse.paraview.org/u/jfavre)
#### Post date: [December 17, 2020, 12:14pm UTC](https://discourse.paraview.org/t/plugins-search-path/6080/3 "2020-12-17T12:14:44Z")

</div>

Thanks for your reply:  
[https://gitlab.kitware.com/paraview/paraview/-/issues/20401](https://gitlab.kitware.com/paraview/paraview/-/issues/20401)