Closed Fanor51 closed 11 months ago
I saw these changes from v4.1 to v4.2 -> https://github.com/TYPO3-Headless/headless/commit/fd4684acb785fed9205438a7d813654cfc550f40. Are here any migration stepps for forms or did there maybe went something wrong with the key shown above?
Best regard - Fabio
Hi @Fanor51, what value of "headless" in you have in your site configuration? By any chance you enabled mixed mode?
Hello @twoldanski ,
what do you mean with value of "headless"? Here is my site config ->
base: '%env(BASE_DOMAIN)%'
frontendBase: '%env(FRONTEND_BASE_DOMAIN)%'
errorHandling:
-
errorCode: 404
errorHandler: PHP
errorPhpClassFQCN: Vendor\MySitePackage\Error\JsonErrorHandler
- errorCode: 410
errorHandler: PHP
errorPhpClassFQCN: Vendor\MySitePackage\Error\JsonErrorHandler
languages:
-
title: German
enabled: true
languageId: 0
base: /
typo3Language: de
locale: de_DE.utf8
iso-639-1: de
navigationTitle: ''
hreflang: ''
direction: ''
flag: de
solr_core_read: '%env(SOLR_CORE)%'
rootPageId: 2
routeEnhancers:
... my enhancer
routes:
... my routes
solr_enabled_read: true
solr_host_read: '%env(SOLR_HOST)%'
solr_path_read: '%env(SOLR_PATH)%'
solr_port_read: '%env(SOLR_PORT)%'
solr_scheme_read: '%env(SOLR_SCHEME)%'
solr_use_write_connection: false
websiteTitle: ''
We don´t have any translations if this was your question.
Thank you! Fabio
@Fanor51 thx. Please add headless
flag you your yaml configuration with one of the values (1 => full headless site, 2 -> mixed (default fluid, json on Accept
header). In configuration above you have now headless mode disabled, that is reason you have broken forms (in non-headless we do not process response to fix USER_INTs declarations)
Hello @twoldanski ,
Thanks for you support. Your settings really fixes my issues with 4.2.2: Now everything lgtm.
Thanks!
Version(s)
PHP: 8.2.11 TYPO3: v12.4.7 Headless: v4.2.2
Descirption
Hello,
i updated the headless extension form v4.1.1 to v4.2.2 and every Page with a TYPO3 Forms formular breakes because of displaying ts cache keys.
f.E.
You can see at the start of the form json -> HEADLESS_INT_START<< and the end >>HEADLESS_INT_END. I downgraded back to v4.1.1 and everything was fine.
Can you please check if there is something broke in v4.2.2 or if you can reproduce this so i know i dint break anything? I can deep dive into that too if there is any need. I have not yet looked into the the code from the v4.2.2 release so maybe i can see there something.
Best Regards Fabio