<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Hi Martin,</p>
<p>I have just tested this on my own instance that is running the
current GitHub HEAD for 3.4 and the only issue I found was that
when I added a subject it returned me to the top of the page but
successfully added the subject I wanted. I had no problem
uploading files and the page being updated with the newly added
document. Similarly, I had no problems filing in any other
simpler fields. My short workflow was just a quick hack to add
all components into the same stage so my workflow looks like:</p>
<workflow xmlns=<a class="moz-txt-link-rfc2396E" href="https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Feprints.org%2Fep3%2Fworkflow&data=01%7C01%7C%7Cb580e8ab403d4159688608d8268f45bc%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=TvHwbOVDQ1vPucw4Vh7pn6HrfrwnK0rTNSZY0ocKKvo%3D&reserved=0" originalSrc="http://eprints.org/ep3/workflow" shash="VoBIamUmZuxZNsauEJE+FvxPhdI67y32vgfC24VPxLkMA76PHt71fJnTULXGRKOzUVwprt7sIl26voxRImhRu/oqazt5y9U9DrUg3mgy0nB/fa8JeOhKSSZkAnfnWVWoW1h8YOE+Q8aiiHzBQAmCU37/e4IX/bUg2aRFqqz232U=">"http://eprints.org/ep3/workflow"</a>
xmlns:epc=<a class="moz-txt-link-rfc2396E" href="https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Feprints.org%2Fep3%2Fcontrol&data=01%7C01%7C%7Cb580e8ab403d4159688608d8268f45bc%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=wOU6FVFmlYdukDk%2FTepm9Y8O33fH6xRSNzsFBvnudx0%3D&reserved=0" originalSrc="http://eprints.org/ep3/control" shash="Nzbkv3QBwrOypSYHbRQk1l6ejoouHoVEphrosA3o4z7u24vTxG6WLPisPN2v5jnK4D4vgtniAcQoKUYQhQJvCGFoEVK7hE6tMYxE0ZMyXfohEIs77Xdd9zJNPzF6TNMWrPULzxMziz1VRsrLOZzAOIPA1KiewPNhE5XEekSMiTU=">"http://eprints.org/ep3/control"</a>><br>
<flow><br>
<stage ref="core"/><br>
</flow> <br>
<stage name="core"><br>
...<br>
</stage><br>
</workflow>
<p>Obviously, this is not a very realistic workflow and has the flaw
that you cannot preset the type so that the appropriate components
can be shown in later stages. Maybe a better approach would be to
extend the Import plugin so that it would send you to an
Edit:ShortWorkflow screen plugin that uses the short rather than
default (full) workflow. Then the regular user who has just
imported an item has minimal work to do but the reviewer (or even
that user) could come along later and look across the whole
workflow.<br>
</p>
<p>The error message you see reported getting on line 499 suggests
that a stage with a particular ID could not previously be found
and so led to this undefined value. So how you have assigned
names (i.e. IDs in this context) to you stages in your XML
workflow file may be the reason for the issue here. I don't think
there are any major restrictions on what characters can be used in
stage names but I would advise keeping them alphanumeric with
underscores where necessary, just in case.<br>
</p>
<p>I have also previously noted issues with the file upload looking
unsuccessfully but then when you reload the page the new document
with its metadata fields being present. I cannot remember off the
top of my head what resolution I found for this. I think it was
due to some race condition with the JavaScript. If you include
all the stages on one page there is an even greater chance that
the bits of Javascript will not play nice with each other and lead
to a race condition or some other issue which prevents the newly
uploaded document from appearing automatically. It is worth
having a look at your browser's web console when you are uploading
a file to see if you can spot anything.</p>
<p>Regards</p>
<p>David Newman</p>
<div class="moz-cite-prefix">On 12/07/2020 09:12, Martin Braendle
via Eprints-tech wrote:<br>
</div>
<blockquote type="cite" cite="mid:EMEW3|1ea14e9b9a329b7ba0a67d0549d60491w6B9FN14eprints-tech-bounces|ecs.soton.ac.uk|OFF71770A9.F90681C8-ONC12585A3.002D11F4-C12585A3.002D1444@lotus.uzh.ch">
<font size="2" face="Default Sans
Serif,Verdana,Arial,Helvetica,sans-serif">
<div>
<div><font style="font-family: arial, helvetica, sans-serif;
box-sizing: inherit;" size="2">Hi everyone,</font><br style="box-sizing: inherit; font-family: arial, helvetica,
sans-serif; font-size: 11.199999809265137px;">
<br style="box-sizing: inherit; font-family: arial,
helvetica, sans-serif; font-size: 11.199999809265137px;">
<font style="font-family: arial, helvetica, sans-serif;
box-sizing: inherit;" size="2">we had the idea to offer a
single-stage submission workflow after complaints of a VIP
at our university that the current workflow requires too
many clicks.</font><br style="box-sizing: inherit;
font-family: arial, helvetica, sans-serif; font-size:
11.199999809265137px;">
<br style="box-sizing: inherit; font-family: arial,
helvetica, sans-serif; font-size: 11.199999809265137px;">
<font style="font-family: arial, helvetica, sans-serif;
box-sizing: inherit;" size="2">This short workflow would
be activated after an import of an item from Crossref,
PubMed, ORCID or another source (e.g. at the first
revision of the item and if the source is known), and
would only offer the missing required fields and the
upload component. For many users (we have several hundred
submitters adding more than 10'000 items annually), this
would save hours of work.</font><br style="box-sizing:
inherit; font-family: arial, helvetica, sans-serif;
font-size: 11.199999809265137px;">
<br style="box-sizing: inherit; font-family: arial,
helvetica, sans-serif; font-size: 11.199999809265137px;">
<font style="font-family: arial, helvetica, sans-serif;
box-sizing: inherit;" size="2">However, after implementing
such a single stage, we observed that some components have
the following problems if merged into one stage with other
components:</font><br style="box-sizing: inherit;
font-family: arial, helvetica, sans-serif; font-size:
11.199999809265137px;">
<font style="font-family: arial, helvetica, sans-serif;
box-sizing: inherit;" size="2">- the Subject component
crashes the application after choosing a subject for
adding (leading to a "</font><font size="2" face="Arial,
Default Sans Serif, Verdana, Helvetica, sans-serif"><font style="box-sizing: inherit;">Can't call method
"get_state_params" on an undefined value at
/service-app/apps/eprints/perl_lib/EPrints/Workflow.pm
line 499.\n</font><font style="box-sizing: inherit;">" </font></font><font style="font-family: arial, helvetica, sans-serif;
box-sizing: inherit;" size="2">error).</font><br style="box-sizing: inherit; font-family: arial, helvetica,
sans-serif; font-size: 11.199999809265137px;">
<font style="font-family: arial, helvetica, sans-serif;
box-sizing: inherit;" size="2">- the Upload component does
not return feedback when uploading a document (it goes on
infinitely). After interruption, however, the system
indicates that the document had been uploaded and is
there.</font><br style="box-sizing: inherit; font-family:
arial, helvetica, sans-serif; font-size:
11.199999809265137px;">
<br style="box-sizing: inherit; font-family: arial,
helvetica, sans-serif; font-size: 11.199999809265137px;">
<font style="font-family: arial, helvetica, sans-serif;
box-sizing: inherit;" size="2">Definitely something is
wrong with the workflow engine. In my opinion, components
should be freely includable in whatever part of the stage.</font><br style="box-sizing: inherit; font-family: arial, helvetica,
sans-serif; font-size: 11.199999809265137px;">
<br style="box-sizing: inherit; font-family: arial,
helvetica, sans-serif; font-size: 11.199999809265137px;">
<font style="font-family: arial, helvetica, sans-serif;
box-sizing: inherit;" size="2">Has anybody else tried to
achieve something similar and had success?</font><br style="box-sizing: inherit; font-family: arial, helvetica,
sans-serif; font-size: 11.199999809265137px;">
<br style="box-sizing: inherit; font-family: arial,
helvetica, sans-serif; font-size: 11.199999809265137px;">
<font style="font-family: arial, helvetica, sans-serif;
box-sizing: inherit;" size="2">Kind regards,</font><br style="box-sizing: inherit; font-family: arial, helvetica,
sans-serif; font-size: 11.199999809265137px;">
<br style="box-sizing: inherit; font-family: arial,
helvetica, sans-serif; font-size: 11.199999809265137px;">
<font style="font-family: arial, helvetica, sans-serif;
box-sizing: inherit;" size="2">Martin</font><br>
</div>
</div>
</font>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">*** Options: <a class="moz-txt-link-freetext" href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a>
*** Archive: <a class="moz-txt-link-freetext" href="https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data=01%7C01%7C%7Cb580e8ab403d4159688608d8268f45bc%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=Fev1wbZrKe4yucKQaa3pG8UciklYVAsXOl4UhQLtRew%3D&reserved=0" originalSrc="http://www.eprints.org/tech.php/" shash="fIUY0xAEvfa9ZoHzdkVEJ0jBeixMPgSrdsIz/oQgTGtErS64XFUVItWdcXLVDDfAIFEbQfQ+dzg7fuVnqalkrp1WebS1JAnUoGP7nPOvwO9trTEHbtV8ljEe89PFVQ+GD/zavFWfm7M7Jjx2kR0ALZoQNZ9GPgdMKA9J+30L0VE=">http://www.eprints.org/tech.php/</a>
*** EPrints community wiki: <a class="moz-txt-link-freetext" href="https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.eprints.org%2F&data=01%7C01%7C%7Cb580e8ab403d4159688608d8268f45bc%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=k%2FsoW4cclBBCj7e072UHcRRA6i%2FmHHR0mxJUmca7Mvo%3D&reserved=0" originalSrc="http://wiki.eprints.org/" shash="CwA5j/AxfqYST11HsMYUZscNnaFlYRgd+p+T0H+eLiIwWO6HgBByvHWVUgB0/M9Dj4FNqRaVE5PmGoEFZa4cPs2rcGpjYMqu5+1RV2ZizcRv4P9r/9ANNmqlUTur2C66CgQ9y8aK0nOZL6SvaBLvI2DGTDk4MUp1BcizFigUHAc=">http://wiki.eprints.org/</a></pre>
</blockquote>
<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
<table style="border-top: 1px solid #D3D4DE;">
<tr>
<td style="width: 55px; padding-top: 13px;"><a href="https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.avg.com%2Femail-signature%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Demailclient&data=01%7C01%7C%7Cb580e8ab403d4159688608d8268f45bc%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=JwPFI1P9%2FpiifasAhJwa52nCXFRfsFEijUmiO3Y3q90%3D&reserved=0" originalSrc="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" shash="Knf/3gS4eT7Nlxif1itq9UdMR/7Su/SGoRKYoKnNb29C0FR6tGz56QLOp9ZDllthqKOEWBS4ha5I73MfsGvJ/R7wgVA4TN6xqHO6l3qqmabvujad0y0TK+wM0TUS1Ovg4wJQ8WZs4BeUT3pjb+hXklg/BgLyJoMBXyZXZ8zBDso=" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-green-avg-v1.png" alt="" width="46" height="29" style="width: 46px; height: 29px;"></a></td>
<td style="width: 470px; padding-top: 12px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Virus-free. <a href="https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.avg.com%2Femail-signature%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Demailclient&data=01%7C01%7C%7Cb580e8ab403d4159688608d8268f45bc%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=JwPFI1P9%2FpiifasAhJwa52nCXFRfsFEijUmiO3Y3q90%3D&reserved=0" originalSrc="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" shash="Knf/3gS4eT7Nlxif1itq9UdMR/7Su/SGoRKYoKnNb29C0FR6tGz56QLOp9ZDllthqKOEWBS4ha5I73MfsGvJ/R7wgVA4TN6xqHO6l3qqmabvujad0y0TK+wM0TUS1Ovg4wJQ8WZs4BeUT3pjb+hXklg/BgLyJoMBXyZXZ8zBDso=" target="_blank" style="color: #4453ea;">www.avg.com</a>
</td>
</tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></body>
</html>