Project

General

Profile

Actions

Bug #85633

closed

"Save and create a new one" button in BE appends superfluous hash which resets defVals

Added by Christian Richter over 6 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2018-07-24
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
Sprint Focus:

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.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #24515: alt_doc.php does not keep default values given in URL.Closed2011-01-11

Actions
Actions

Also available in: Atom PDF