Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flex Form Field is inaccessible after the 13.4.2 update #318

Open
tgrigoryan234 opened this issue Dec 10, 2024 · 11 comments
Open

Flex Form Field is inaccessible after the 13.4.2 update #318

tgrigoryan234 opened this issue Dec 10, 2024 · 11 comments
Labels

Comments

@tgrigoryan234
Copy link

Describe the bug
After the minor update, the Flex Form fields are no longer accessible. It is empty.

To Reproduce
Steps to reproduce the behavior:

 fields:
  - identifier: my_flexform
    type: FlexForm
    fields:
      - type: Sheet
        identifier: sheet1
        label: Sheet 1
        fields:
          - identifier: section1
            type: Section
            label: Section 1
            container:
              - identifier: container1
                label: Container 1
                fields:
                  - identifier: container_field
                    type: Text
              - identifier: container2
                label: Container 2
                fields:
                  - identifier: container_field2
                    type: Textarea

Screenshots
Bildschirmfoto 2024-12-10 um 14 54 22
Bildschirmfoto 2024-12-10 um 14 54 38

TYPO3 Version
13.4.2

@nhovratov
Copy link
Contributor

Did this work in v13.4.1 ? For me it doesn't work in both versions.

@tgrigoryan234
Copy link
Author

it worked for me with 13.4.1.
Should I post bugs in Typo3 or have you already done so?

@nhovratov
Copy link
Contributor

Hm, interesting. Yes, we need to file an issue on TYPO3 forge. If you could do this, I would much appreciate it. I already noticed my Core collegues that there are still issues with FlexForm.

@tgrigoryan234
Copy link
Author

Issue created: https://forge.typo3.org/issues/105800

@nhovratov
Copy link
Contributor

Thanks. But I'm still unsure how it worked for you before. Using exactly the same config results in an empty array for me.

@tgrigoryan234
Copy link
Author

Ich habe in Configuration/TCA/Overrides/tt_content.php ein Flexform Feld aufgebaut. Und in den verschiedenen Contentblocks verwendet.
Vielleicht könntest du es so reproduzieren.

@nhovratov
Copy link
Contributor

nhovratov commented Dec 10, 2024

Yes, you most probably have a constellation, which Content Blocks doesn't create by itself. As a workaround, please add the FlexForm processor in your TypoScript: https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/DataProcessing/FlexFormProcessor.html

Example:

lib.contentBlock {
    dataProcessing {
        110 = flex-form
        110.fieldname = my_flexform
    }
}

This will make the FlexForm available as flexFormData and you can just replace it.

@tgrigoryan234
Copy link
Author

Will it also work for backend previews or collection flex fields? I don't think so. For backend previews I have to develop one and also for collection flex fields, right?
I have created entire web pages of content, and now I have to be careful

@nhovratov
Copy link
Contributor

Ok, in this case you could also implement an EventListener: https://docs.typo3.org/p/friendsoftypo3/content-blocks/main/en-us/DeveloperCorner/DataProcessing/Index.html

And then just call FlexFormService->convertFlexFormContentToArray on your FlexForm field.

Otherwise, please wait until this is fixed in Core.

@tgrigoryan234
Copy link
Author

tgrigoryan234 commented Dec 11, 2024

Even if I will also use Event Listner, the problem with Collections still exists. That's why I created a patch locally that works. I'll post it here.

typo3-cms-core-flex.patch

@nhovratov
Copy link
Contributor

The Event Listener also works for Collection Records. But if the fix works for you, this is fine as an intermediate workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants