Issue Bug Closed

#97750Form: Cannot publish workspace after creating form content element

Stephan Schuler 06/08/22, 15:39 updated 02/03/24, 10:48

Description

Hey there.

Configuration:

I’m currently running a TYPO3 version 10.4.27.

I have extension EXT:workspaces enabled.
I have extension EXT:form enabled.

I have a single other workspace in addition to “Live”.

Walk through

I create a new content element of CType “form_formframework” within that workspace.

This content element relates to a specific “definition” file through the “settings.persistenceIdentifier” property of its pi_flex.

Then I try to publish by opening the “Workspace” module of the root page of a site.

Expected behavior

I see a table showing every change the workspace wants to publish.

Actual behavior

The table shown in the TYPO3 backend is empty.

My browsers debug console shows a “500 – internal server error”.

Diving into that error shows: Doctrine AbstractMySQLDriver throws an InvalidFieldNameException because “sys_file” has no column “t3ver_wsid”.
Which is true.

Some thougths

I don’t know if that’s an issue of the Workspace extension or an issue of the Form extension.

Some frames prior to the InvalidFieldNameException being thrown, this very code is executed:
https://github.com/TYPO3/typo3/blob/main/typo3/sysext/workspaces/Classes/Dependency/ElementEntity.php#L418

As shown, the workspace ElementEntity::getRecord() method always asks for t3ver field, no matter if the record in question is actually workspaceable.

Regards,
Stephan

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.