Skip to content

Instantly share code, notes, and snippets.

@josefglatz

josefglatz/TYPO3 9.5 LTS open tasks-bugs-suggestions Integrators.md

Last active December 10, 2018 04:26
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save josefglatz/b1ad98df03881c283ee3d9f9b68213ca to your computer and use it in GitHub Desktop.
Save josefglatz/b1ad98df03881c283ee3d9f9b68213ca to your computer and use it in GitHub Desktop.
Download ZIP
TYPO3 9.5. LTS open task/bug/suggestion list thoughts
Raw
TYPO3 9.5 LTS open tasks-bugs-suggestions Integrators.md

For editors missing stuff or newly introduced bugs/regressions/changes

(This list is updated regulary/if something is tested/fixed by me)

a) TYPO3 Pagetree: New pages must respect TCAdefaults.pages.hidden = 0 and other properties

https://forge.typo3.org/issues/87089 https://forge.typo3.org/issues/59383 If you create a new page within the pagetree, it's always disabled per default. it would be a real benefit if such settings get's respected

  • Fixed and merged
Raw
TYPO3 9.5 LTS open tasks-bugs-suggestions.md

For integrators missing stuff patches/issues like these should/could/must be fixed

(This list is updated regulary/if something is tested/fixed)

from my perspective, as a TYPO3 integrator for many years the following points need some love

A) [FEATURE] Make SiteLanguage available in TypoScript https://review.typo3.org/#/c/58930/

If you want to stick fully to the new site handling feature of TYPO3 9 LTS, there are often situation where you want to retrieve data via getText/data from the active site language. For example: If you want to extend the SiteLanguage (this is possible a missing feature too) with fields like siteTitle (because it's different for every language), GoogleAnalytics (Because the project/customer needs different ID's for GA), ...

  • (Pending) Patch already on Gerrit
  • Fixed and merged

B) [BUGFIX] Avoid overwriting page context in TSFE->cObj by f:cObject https://review.typo3.org/#/c/58661/ √

Basic stuff like https://forge.typo3.org/issues/86979 have to work ootb like stdWrap was possible within page.bodyTagCObject and so on.

  • (Pending) Patch already on Gerrit
  • Fixed and merged

C) [BUG/TASK] TypoScript getText "site" can't retrieve nested properties

See issue for details about that point: https://forge.typo3.org/issues/87036

  • (Pending) Patch already on Gerrit
  • Fixed and merged

D) [QUESTION/TASK/DOCUMENTATION] How to extend/use the site language configuration with custom fields

The actual problem is, that the expandability of the "site language configuration" is not possible from my perspective. Since we have this new great tool in TYPO3, all site wide configuration should be centralized there.

https://review.typo3.org/#/c/59025/

  • (Pending) Patch already on Gerrit
  • Fixed and merged

E) [BUG/TASK] TypoScript Conditions / New ExpressionLanguage() condition don't work as expected

  1. The TypoScriptCondition Matcher does not work as expected when using expressionLanguage conditions
  2. The expressions concatenated with logic operators do not work like before with the old conditions. For example If you use a [getTSFE().beUserLogin === 1] combined with another condition: if the object isn't here, the expressionLanguage logs an error / breaks. It's completely different like before. Such behaviour must be communicated maybe via the core's RsT's
  • (Pending) Patch already on Gerrit
  • Fixed and merged

https://forge.typo3.org/issues/87021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment