Prism does not find remote plugin correctly
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
When starting Prism for the first time (and I suspect any plugin) remote server, if you have started in a different directory than the normal bin directory, the plugin library will not be found. Try this:
start client from top of build, as in ./bin/paraview... start server from top of build, as in ./bin/pvserver ...
Now, try to load the remote server Prism plugin. It won't show in the window. If it does, try again without reading in config state. One option, although not a good one, would be to have an environment var that points to optional plugins that need to be loaded. Another would be to include a .plugins file in the server side.