Custom filters are loaded before plugins, bug if custom filter refers to plugin proxy
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
If you make a custom filter using a proxy that was loaded by a plugin, then the next time you start paraview the custom filter will not work. Paraview fails to load the custom filter definition because it tries to load it before loading the plugins, even if the plugins are set to auto load.