Bug #80825: FlexForm Sections don't get saved before the parent record was stored to the DB - TYPO3 Core - TYPO3 Forge

Custom queries

Accessibility
Easy tasks
Forge Triage
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
My open issues
No feedback within 90 days
Open Bugs
Open issues of 10
Recently modified
Regressions
Stabilization Issues
Usability or UX

Watchers (5)

Daniel Goerz
Faton Haliti
Felix Nagel
Gregor Nathanael Meyer
José Ricardo

Actions

Copy link

Bug #80825

closed

Story #69617: FormEngine bugs

FlexForm Sections don't get saved before the parent record was stored to the DB

Added by Daniel Goerz over 7 years ago. Updated about 6 years ago.

Status:

Closed

Priority:

Must have

Assignee:

Christian Kuhn

Category:

FormEngine aka TCEforms

Target version:

Candidate for patchlevel

Start date:

2017-04-12

Due date:

% Done:

100%

Estimated time:

TYPO3 Version:

PHP Version:

7.0

Tags:

Complexity:

Is Regression:

Yes

Sprint Focus:

Description

Reproduce with current 8LTS and styleguide extension:

Create a styleguide record "Form engine - flex"
Go to tab "section container"
Create one or more container.
Save & Close

The error message "1: Attempt to insert record on page '[root-level]' (0) where this table, tx_styleguide_flex, is not allowed" is shown and the flexform was not stored. The field flex_2 of the newly created record is empty.

Containers can be created without problems once the parent recod is saved. The issue only occurs on creation of a new recod when it is saved for the first time.

Files

error.png (11 KB) error.png

Daniel Goerz, 2017-04-12 17:10

Related issues 3 (0 open — 3 closed)

Related to TYPO3 Core - Bug #80473: Do not bypass fetch of database record if tableName is tt_content

Closed

Faton Haliti

2017-03-27

Actions

Related to TYPO3 Core - Task #80100: Bypass fetch of database record if already loaded

Closed

Xavier Perseguers

2017-03-02

Actions

Related to TYPO3 Core - Bug #80426: Creating a FlexForm section causes exception in ajax request (none admin user)

Closed

2017-03-23

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Daniel Goerz over 7 years ago

Description updated (diff)

Actions

Copy link

Updated by Daniel Goerz over 7 years ago

Subject changed from FlexForm Sections don't get saved before the parent CE was stored to the DB to FlexForm Sections don't get saved before the parent record was stored to the DB

Actions

Copy link

Updated by Daniel Goerz over 7 years ago

Assignee set to Christian Kuhn

As discussed on slack, Christian needs free brain space for this one :)

Thank you for taking care!

Actions

Copy link

Updated by Daniel Goerz over 7 years ago

Related to Bug #80473: Do not bypass fetch of database record if tableName is tt_content added

Actions

Copy link

Updated by Daniel Goerz over 7 years ago

Related to Task #80100: Bypass fetch of database record if already loaded added

Actions

Copy link

Updated by Daniel Goerz over 7 years ago

Related to Bug #80426: Creating a FlexForm section causes exception in ajax request (none admin user) added

Actions

Copy link

Updated by Christian Kuhn over 7 years ago

first guess: that's probably related to the missing uid handling from https://review.typo3.org/#/c/51929/ / https://review.typo3.org/#/c/52174/ ... this needs further thoughts. i can dig into that before 8.7.1 release.

Actions

Copy link

Updated by Daniel Goerz over 7 years ago

This issue was also reported in the flux bugtracker on github as flux (like many other extensions) uses flexform sections.

For reference: https://github.com/FluidTYPO3/flux/issues/1400

Actions

Copy link

Updated by Radu Mogos over 7 years ago

Still present in 8.7.1

Actions

Copy link

#10

Updated by José Ricardo over 7 years ago

I have a content element with flexform section and it always gives a 503 error when I try to add a new section element before saving the content itself. I think it's related to this.

The exception thrown is:
#1476107295: PHP Warning: Invalid argument supplied for foreach() {mybasedir}/typo3_src/typo3/sysext/backend/Classes/Form/Container/FlexFormElementContainer.php line 48 (More information)

I'm using and admin account on TYPO3 8.7.1
The same flexform works fine on 7.6.18

Actions

Copy link

#11

Updated by Radu Mogos over 7 years ago

Priority changed from Should have to Must have

Any info if this will be adressed at least in 8.7.2 since it's a blocking issue when dealing with flexform sections

Actions

Copy link

#12

Updated by Gerrit Code Review over 7 years ago

Status changed from New 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/53215

Actions

Copy link

#13

Updated by Gerrit Code Review over 7 years ago

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

Actions

Copy link

#14

Updated by Gregor Nathanael Meyer over 7 years ago

I tried out the patch set 2 and it solves the problem for me. Thanks.

Actions

Copy link

#15

Updated by Gerrit Code Review over 7 years ago

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

Actions

Copy link

#16

Updated by Christian Kuhn over 7 years ago

Status changed from Under Review to Resolved
% Done changed from 0 to 100

Applied in changeset e3fd3c7a1f78e1b82085814948fd70c7947c9587.

Actions

Copy link

#17

Updated by José Ricardo over 7 years ago

Was this solved on 8.7.2?
THe problem I reported on my comment still exists. Not sure if it's another problem or this issue didn't came to 8.7.2;

Actions

Copy link

#18

Updated by Daniel Goerz over 7 years ago

Hey Riccardo. What you describe looks like a different issue. The one tackled with the patch was only about flex form sections and - yes - this is now solved in TYPO2 8.7.2 thanks to Christian!

Actions

Copy link

#19