Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E election
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • servicesservices
  • t3o sites
  • voting.typo3.org
  • extensions
  • election
  • Issues
  • #27
Closed
Open
Issue created Jan 22, 2020 by Stephan Großberndt@grossberndtsOwner

Disable deprecation log and TypoScript.strictSyntax check

Please disable deprecations at least for the production server, see https://blog.reelworx.at/detail/deprecation-log-handling-in-typo3-9/ and have a look at the errors in typo3_*.log. By scanning the log quickly I assume either setting TypoScript.strictSyntax to not complain about the old syntax or fixing the syntax to use only the new syntax a lot of lines can be avoided: https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.5/Deprecation-86068-OldConditionSyntax.html

Related to t3o/typo3.org#460

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking