# Autoload Plugin ...
**URL:** https://discourse.paraview.org/t/autoload-plugin/1284
**Category:** Development
**Created:** [February 14, 2019, 8:49am UTC](https://discourse.paraview.org/t/autoload-plugin/1284 "2019-02-14T08:49:32Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Niklas](https://discourse.paraview.org/u/Niklas)
#### Post date: [February 14, 2019, 8:49am UTC](https://discourse.paraview.org/t/autoload-plugin/1284/1 "2019-02-14T08:49:33Z")
Hi,
there was probably a good reason why the Cmake options PARAVIEW\_AUTOLOAD\_PLUGIN\_XXX have been removed, but is there a work around to specify that certain plugins should be automatically loaded? If not, could it be brought back?
Cheers,
Niklas
---
### Author:  [@Niklas](https://discourse.paraview.org/u/Niklas)
#### Post date: [August 8, 2019, 9:10am UTC](https://discourse.paraview.org/t/autoload-plugin/1284/2 "2019-08-08T09:10:40Z")
Hi,
is there any other way to automatically load certain plugins? I’d love to configure ParaView on our cluster in a way that users can start right away, and some plugins are mandatory. I would not want every user to first load all the plugins manually. Any help is greatly appreciated.
Thanks and Cheers,
Niklas
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [August 8, 2019, 9:31am UTC](https://discourse.paraview.org/t/autoload-plugin/1284/3 "2019-08-08T09:31:51Z")
Which version of ParaView are you using ?
---
### Author:  [@Niklas](https://discourse.paraview.org/u/Niklas)
#### Post date: [August 8, 2019, 9:34am UTC](https://discourse.paraview.org/t/autoload-plugin/1284/4 "2019-08-08T09:34:14Z")
The latest one, 5.7-RC2
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [August 8, 2019, 1:59pm UTC](https://discourse.paraview.org/t/autoload-plugin/1284/5 "2019-08-08T13:59:28Z")
@ben.boeckel : Looks like PARAVIEW\_AUTOLOAD\_PLUGIN\_\* cmake option has been removed. Was that intentional ?
@Niklas : You can either
- edit the `lib64/paraview-5.7/plugins/.plugins`,
- use the env variables PV\_PLUGIN\_CONFIG\_FILE : [https://www.paraview.org/Wiki/ParaView/Plugin\_HowTo#Using\_Plugins](https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Using_Plugins) or
- edit the user space config file.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [August 8, 2019, 3:52pm UTC](https://discourse.paraview.org/t/autoload-plugin/1284/6 "2019-08-08T15:52:14Z")
Yes and no. It was intentional in that the way it got populated before was removed. It was unintentional in that another way to specify it should have been added back.
The best way to add it back is something like:
```auto
set(autoload_plugins)
foreach (paraview_plugin IN LISTS paraview_plugins)
option("PARAVIEW_AUTOLOAD_PLUGIN_${paraview_plugin}" "Autoload the ${paraview_plugin} plugin" OFF)
mark_as_advanced("PARAVIEW_AUTOLOAD_PLUGIN_${paraview_plugin}")
if (PARAVIEW_AUTOLOAD_PLUGIN_${paraview_plugin})
list(APPEND autoload_plugins
"${paraview_plugin}")
endif ()
endforeach ()
paraview_plugin_build(… AUTOLOAD ${autoload_plugins})
```
at the top-level. Docs should be added to the `build.md` as well.
---
### Author:  [@Niklas](https://discourse.paraview.org/u/Niklas)
#### Post date: [August 9, 2019, 7:59am UTC](https://discourse.paraview.org/t/autoload-plugin/1284/7 "2019-08-09T07:59:03Z")
Thank you both! I’d love to mark both as solution, but can only one…
I got it easily fixed. Thanks for your help!
Cheers, Niklas
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [August 26, 2019, 8:49am UTC](https://discourse.paraview.org/t/autoload-plugin/1284/8 "2019-08-26T08:49:33Z")
I’ve opened an issue here:
[https://gitlab.kitware.com/paraview/paraview/issues/19276](https://gitlab.kitware.com/paraview/paraview/issues/19276)