Closed ross-spencer closed 5 years ago
We're overriding as_p
here: https://github.com/artefactual/archivematica-storage-service/blob/stable/0.11.x/storage_service/locations/forms.py#L106
And the definition of as_p
is here: https://docs.djangoproject.com/en/2.0/_modules/django/forms/forms/
For whatever reason, minor or otherwise, appending a string to as_p
is causing this issue because if you remove it, all is okay.
There's a pretty nice thread on overriding this function here: https://stackoverflow.com/a/7770417. Consulting this and the class seems to show a focus on rows, not what happens at the end of the form, so I will take a look at this in more detail and also see if there are any clues as to why our little override isn't quite working when we come to render the form.
Have tested this in our dataverse QA environment and it is looking good to me!
The form component after the staging path when asked to re-render, e.g. submitting the form once correctly or otherwise results in the following output:
The HTML when we view source looks as follows: