Bug #80366
closedValues aren't always saved in the TYPO3 backend
100%
Description
Problem/Description¶
A video is worth a thousand pictures :-[
https://youtu.be/5cqln5P1MJA
Update: Just for the records¶
2 hours later, same browser session, same server environment, faster internet connection between client and server: I couldn't actually not reproduce the described behaviour.
ToDo(s)¶
*
Acceptance Criteria¶
*
Updated by Markus Hofmann over 7 years ago
Same problem in 7.6.16, required input fields are not saved on the initial save. The data is not transferred in the POST. Downgrade to 7.6.15 fixed the problem
Updated by Markus Klein over 7 years ago
@Markus H.
Can you reproduce the issue reliably? Does your instance involve JS code from extensions?
Can you do a git bisect to find the offending commit?
The following changes have been merged between .15 and .16, which touch JS somehow:
https://review.typo3.org/51262
https://review.typo3.org/51816
https://review.typo3.org/51718
Don't know if those actually interfere here though.
Updated by Markus Hofmann over 7 years ago
@Markus K.
We reproduced the bug in different TYPO3 instances. Every time a new data is inserted. I tested with be_users, required fields are password, username and usergroup in a blank and new typo3 instance, and with own types of data in other instances.
Fields with default values and fields, which are not required, are updated properly.
We found some possible issues in reviews and will test them. I'll give you feedback.
Updated by Sven Juergens over 7 years ago
i had the same problem here some time ago, so i think it's not related to 7.6.16
the first time i see this issue i used current Chromium version as Browser, so i thought it's related to some new stuff in Chromium.
Maybe a JS Event is not fired every time or something like that. Because the Problem is, that the input of the fields are not transfered to the hidden input fields, which are sent.
Updated by Josef Glatz over 7 years ago
My colleague had reproduced it with TYPO3 7.6.13 AND Chrome Version 57.0.2987.98 (64-bit) Mac. We can't reproduce the problem at the same time with Firefox for example.
So I could anybody of you can reproduce it with e.g. Firefox or IE?
Updated by Nicolas Scheidler over 7 years ago
Encountered the same issue here in 7.6.16 (Chrome 57.0.2987.110 (64-bit)).
Updated by Alex B over 7 years ago
Same here.
Typo3 Versions 7.6.15 and 7.6.16, Chrome 57.
I can not reproduce the bug in Firefox.
This happens for all fields and not just in required fields! Tested with Typo3 Header CE and various Fields in Extensions.
Tested with all custom Extensions turned off in Chrome.
Updated by Markus Klein over 7 years ago
- Category set to Backend User Interface
- Status changed from New to Accepted
- Assignee set to Markus Klein
- Complexity set to hard
- Is Regression changed from Yes to No
We will look into this tomorrow at the camp Vienna.
Updated by Markus Klein over 7 years ago
Please apply the patch of #80459: https://review.typo3.org/52168 and check if things got better.
Feedback very appreciated.
Updated by Sven Juergens over 7 years ago
hi,
testet it with 7.6.16.
the Problem still exisit.
the problem is here locatated (TYPO3 7.6.16)
typo3/sysext/backend/Resources/Public/JavaScript/FormEngineValidation.js
function:
FormEngineValidation.updateInputField ~ line 197
var config = $mainField.data('config');
if (typeof config !== 'undefined') {
.... here the fields are updatet
}
sometimes the var config is empty
Updated by Markus Klein over 7 years ago
Thanks a lot Sven! Will look into this.
Updated by Gerrit Code Review over 7 years ago
- Status changed from Accepted to Under Review
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/52180
Updated by Gerrit Code Review over 7 years ago
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/52180
Updated by Gerrit Code Review over 7 years ago
Patch set 1 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/52208
Updated by Gerrit Code Review over 7 years ago
Patch set 2 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/52208
Updated by Gerrit Code Review over 7 years ago
Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/52180
Updated by Gerrit Code Review over 7 years ago
Patch set 3 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/52208
Updated by Gerrit Code Review over 7 years ago
Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/52180
Updated by Markus Klein over 7 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 976934a36c8efde01c31ed38cafec7340562e6f4.
Updated by José Ricardo over 7 years ago
Any idea on when 7.6.17 will be available with this fix?
Updated by Sven Juergens over 7 years ago
on Tuesday, April 18th, 2017
https://typo3.org/news/article/regular-maintenance-release-schedule/
Updated by Mona Muzaffar over 7 years ago
- Related to Bug #80632: still issues with missing input in BE added
Updated by Riccardo De Contardi over 7 years ago
I guess I've stumbled upon this issue on a fresh 8.7.0 install (I am not able to reproduce at the moment, just guessing)
Updated by Mona Muzaffar over 7 years ago
- Related to Bug #80672: Saving problems in Chrome 57+ added
Updated by Pascal Hinz over 7 years ago
- Related to Bug #80884: FAL metadata has to save multiple times before it's go to the database added
Updated by Riccardo De Contardi about 7 years ago
- Status changed from Resolved to Closed