Project

General

Profile

Actions

Bug #93564

closed

form validation error in 10.4.13

Added by David Menzel over 3 years ago. Updated 8 days ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend JavaScript
Target version:
-
Start date:
2021-02-22
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
7.4
Tags:
backend, form validation
Complexity:
Is Regression:
Sprint Focus:

Description

I use ext:news and ext:mask and use mask content elements in news records.

After the TYPO3 10.4.13 update an editor noticed that it's not possible to edit the news record which has mask content elements anymore and only gets a spinner element. You can also see a form validation error in the console (screenshot).
This news record uses mask content elements and the error appears when I have a mask link field with a link included in that content element. If I remove the link in the Database then it's again possible to edit the news record.

Furthermore I downgraded to 10.4.12 and then it was possible to edit news records which has mask ce with link elements. Now, the only problem were misplaced ui elements in the news content elements tab (screenshot). Newly created news records in 10.4.12 with mask ce and link elements had given no problems.

On a side note, I also noticed that it takes now 2-4 seconds until a news records opens in the BE when it has multiple mask elements.

Maybe it has something to do with the update of the form validation introduced in TYPO33 10.4.13?


Files

misplaced-elements.jpg (64 KB) misplaced-elements.jpg misplaced elements after downgrade from 10.4.13 to 10.4.12 David Menzel, 2021-02-22 15:26
spinner-element-news.jpg (56 KB) spinner-element-news.jpg only spinner when open news record David Menzel, 2021-02-22 15:26
BE-Form-JS-error-News.jpg (638 KB) BE-Form-JS-error-News.jpg form validation error David Menzel, 2021-02-22 15:26
Actions #1

Updated by Riccardo De Contardi 8 days ago

  • Status changed from New to Closed

I apologize for this very late reply; I think it is safe to close this issue for now - All of the involved components changed a lot since v10

If you think that this is the wrong decision or experience the issue again on recent TYPO3 versions (12 or 13) please reopen it or open a new issue with a reference to this one.

Thank you.

Actions

Also available in: Atom PDF