# What is needed to make plugin settings persistent?

**URL:** https://discourse.paraview.org/t/what-is-needed-to-make-plugin-settings-persistent/10759
**Category:** Development
**Created:** [November 15, 2022, 10:22pm UTC](https://discourse.paraview.org/t/what-is-needed-to-make-plugin-settings-persistent/10759 "2022-11-15T22:22:56Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![johnt](https://discourse.paraview.org/user_avatar/discourse.paraview.org/johnt/32/3645_2.png) [@johnt](https://discourse.paraview.org/u/johnt)
#### Post date: [November 15, 2022, 10:22pm UTC](https://discourse.paraview.org/t/what-is-needed-to-make-plugin-settings-persistent/10759/1 "2022-11-15T22:22:56Z")

</div>

I have a small plugin that needs one persistent setting (string). I can add an xml config file to my build (via SERVER\_MANAGER\_XML) and the new setting appears in the pqSettingsDialog, and I can get/set its value via vtkSMSettings. However, the value is not stored, but is reset each time I restart the app.

It is not obvious to me how ParaView handles properties specified this way. I tried adding the SaveInQSettings hint in the ProxySettings xml element, but that didn’t make any difference.

Right now, the plugin doesn’t have any vtiObject classes nor any vtk module. Do I need to add either/both?

---

<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: [November 16, 2022, 8:44am UTC](https://discourse.paraview.org/t/what-is-needed-to-make-plugin-settings-persistent/10759/2 "2022-11-16T08:44:12Z")

</div>

Hi @johnt

What you describe should work, here is a fonctionnal example:

> **[ThemysSettings · main · themys / ThemysServerPlugins · GitLab](https://gitlab.com/themys/themysserverplugins/-/tree/main/ThemysSettings)**
>
> GitLab.com

Hth.