Bug #85633
closed
"Save and create a new one" button in BE appends superfluous hash which resets defVals
0%
Description
Even though the savedoknew buttons are created as inputButtons in the EditDocumentController, eventually they end up as something like:
<a href="#" data-name="_savedoknew" data-value="1" data-form="EditDocumentController" class="t3js-editform-submitButton"><span class="t3js-icon icon icon-size-small icon-state-default icon-actions-document-save-new" data-identifier="actions-document-save-new">
<span class="icon-markup">
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><g class="icon-color"><path ...></path></g></svg>
</span>
</span> Save and create a new one</a>
Since they are <a>-tags in the DOM with an href-attribute set to '#', the hash get's appended to the returnUrl which results in all defVals getting lost on the way...
I'm editing records from backend modules and sometimes I'm in the context of a parent record and want to set this record as parent for newly created child records.
In my case the current "Save and create a new one" behaviour can lead to orphaned child records, but I can imagine more data-mess when the defVals aren't populated to new "save and new" records that are created in one go.
Updated by
Updated by Georg Ringer about 4 years ago
- Related to Bug #24515: alt_doc.php does not keep default values given in URL. added
Updated by Oliver Bartsch over 3 years ago
- Status changed from New to Closed
Hi,
as already documented in the related issue #24515 there is no savedoknew button anymore.
While the code is still present, the issue isn't as there are no "Save + New" Buttons anymore in the normal edit forms of TYPO3. Using the most similar way of creating a new record (open any record, press new) the default values are taken into account now.
I will therefore close this issue now. If you feel there is still something that does not work using the described workflow, please let me know and I will re-open the ticket.