-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Importing and re-exporting a full XML removes <additional_input>
#998
Comments
Hi @Zack-83 above you write "options" but you are on the optionset page or the catalogs page, can you clarify a bit what you did edit on which page? |
I follow the links from the catalogue https://rdmocat.aip.de/management/catalogs/19/nested/ to the optionset https://rdmocat.aip.de/management/optionsets/134/ to the option https://rdmocat.aip.de/management/options/995/ , tick the radio buttons on the last line, save, go back to https://rdmocat.aip.de/management/catalogs/19/nested/ , download. |
Hmm, I cannot really reproduce the problem here, are you sure the option was saved? Maybe there is another bug preventing this. I currently have no account on https://rdmocat.aip.de or my pw is not working anymore. Maybe you or @triole can create/update mine. |
I created an account for you.
|
Ah, so it will only apear when importing the old format, right? This I did not check. |
I've added the first additional_input = element.get('additional_input')
if additional_input in ['', 'text', 'textarea']: # from Option.ADDITIONAL_INPUT_CHOICES
pass
elif additional_input == 'True':
element['additional_input'] = 'text'
else:
element['additional_input'] = '' PS made a mistake with |
Yes, this should work. I think the files that cause these problems have the wrong |
yes, but who knows what the right |
hmm, the idea was never to edit the xml files directly, but people do it anyway. I guess they just need to be careful, but any |
With which version was the |
In |
@MyPyDavid this is also implemented in |
yes, this will be part of RDMO 2.2.0 |
Description / Beschreibung
Edit some options and export them in/from the subpage
./management/optionsets/
. Open the XML file with a text editor. The fields<additional_input>
are populated.Edit the same options within a catalogue in the subpage
/management/catalogs/
, and export the full XML. Open the XML file with a text editor. The fields<additional_input>
are empty!Edit a XML optionset file on your computer and import it into the subpage
./management/optionsets/
. The fields<additional_input>
are populated.Edit a full XML file on your computer and then import it into the subpage
/management/catalogs/
. The fields<additional_input>
are reset to "---"!Expected behaviour / Erwartetes Verhalten
The content of
<additional_input>
should be maintained on either way.I have attached an exemplary full XML before and after the export. The information loss is striking.
epm.zip
The text was updated successfully, but these errors were encountered: