Project

General

Profile

Actions

Bug #80633

closed

Sending empty forms in some cases

Added by Frank Nägler about 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Category:
Backend JavaScript
Target version:
Start date:
2017-04-02
Due date:
% Done:

100%

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

Description

In some cases (hard to reproduce) the FormEngine forms will be submitted with an empty set of data.
This could be triggered in chrome and firefox with the "save and new" submit button.

In my case I can reproduce it by creating 10 header records, set headline field and link field, hit the save an new button.

8 of 10 records are created with empty values.

Setting a higher timeout in TBE_EDITOR.submitForm solved the issue for me.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #80884: FAL metadata has to save multiple times before it's go to the databaseClosed2017-04-19

Actions
Related to TYPO3 Core - Bug #80632: still issues with missing input in BEClosed2017-04-02

Actions
Actions #1

Updated by Gerrit Code Review about 7 years ago

  • Status changed from In Progress to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/52315

Actions #2

Updated by Frank Nägler about 7 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #3

Updated by Lars Stratenwerth Stratenwerth about 7 years ago

I'm having the same problem with Typo3 7.6 and PHP 5.6.
Only it is not 8 out of 10 times and more like 2 out of 10.

Actions #4

Updated by Markus Klein about 7 years ago

  • Related to Bug #80884: FAL metadata has to save multiple times before it's go to the database added
Actions #5

Updated by Markus Klein about 7 years ago

  • Related to Bug #80632: still issues with missing input in BE added
Actions #6

Updated by Christer V about 7 years ago

We also still have this problem in 8.7.1. About 20% time the last edited field isn't saved.

Actions #8

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF