# XML plugin syntax evolution between ParaView 5.6 and 5.8

**URL:** https://discourse.paraview.org/t/xml-plugin-syntax-evolution-between-paraview-5-6-and-5-8/4975
**Category:** Development
**Created:** [July 28, 2020, 3:14pm UTC](https://discourse.paraview.org/t/xml-plugin-syntax-evolution-between-paraview-5-6-and-5-8/4975 "2020-07-28T15:14:28Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Loic](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/l/e9c0ed/32.png) [@Loic](https://discourse.paraview.org/u/Loic)
#### Post date: [July 28, 2020, 3:14pm UTC](https://discourse.paraview.org/t/xml-plugin-syntax-evolution-between-paraview-5-6-and-5-8/4975/1 "2020-07-28T15:14:28Z")

</div>

I’ve noticed some changes in the way ParaView 5.8 handles several custom plugins when a .pvsm state file is loaded.

Theses plugins are based on the vtkPythonProgrammableFilter class and uses a XML file to display some parameters in the properties panel. In order to define input and output file path, we used the following XML syntax to define filechooser options:

```
<Documentation>Path to the TXT file to generate</Documentation>
<FileListDomain name="files"/>
<Hints>
      <FileChooser extensions="txt" file_description="Result file" />
  <AcceptAnyFile/>
</Hints>

```

With ParaView 5.6, the paths defined with that syntax appear in the “Load State file” window when the option “Choose File Names” is activated.

With ParaView 5.8, these paths do no longer appear in that window.

I don’t know if the XML plugin syntax has evolved since ParaView 5.6 and if I have to adapt my XML file to get these paths back in the “Load State” window.

Should I open an issue in the bug tracker?

Thanks a lot for your help,

Loïc

---

<div class="post-metadata">

### Author: ![Loic](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/l/e9c0ed/32.png) [@Loic](https://discourse.paraview.org/u/Loic)
#### Post date: [July 29, 2020, 7:23am UTC](https://discourse.paraview.org/t/xml-plugin-syntax-evolution-between-paraview-5-6-and-5-8/4975/2 "2020-07-29T07:23:58Z")

</div>

I’ve open an [issue](https://gitlab.kitware.com/paraview/paraview/-/issues/20116) in the bug tracker with a test case showing that problem.