Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
automated-typo3-update
automated-typo3-update
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Automated-TYPO3-Update
  • automated-typo3-updateautomated-typo3-update
  • Issues
  • #68

Closed
Open
Opened Apr 13, 2017 by Daniel Siepmann@DanielSiepmann0 of 5 tasks completed0/5 tasks
  • Report abuse
  • New issue
Report abuse New issue

Check Database

Obviously this will not be implemented as a Sniff. But our tool should ease TYPO3 updates in all possible ways. One would be to check the database. Are you including css_styled_content which is no longer available?

Therefore we should probably provide different tools, one providing phpcs standards as already done. One providing db migrations, a distribution to bundle all together, etc.

We should implement the css_styled_content as a first example to kickstart the architecture and feature to check the database.

Once that's implemented, create issues for the following tasks:

  • Apply TypoScript checks to database, see #54 (closed)
  • Apply PageTSConfig checks to database, see #54 (closed)
  • Apply UserTSConfig checks to database, see #54 (closed)
  • Check whether removed fields contain something that will be lost during migration?
  • Check what TYPO3 does between the versions to create further related issues.
Assignee
Assign to
Nice to have
Milestone
Nice to have
Assign milestone
Time tracking
None
Due date
None
4
Labels
component/Database help wanted issueType/newFeature status/SelectedForDevelopment
Assign labels
  • View project labels
Reference: Automated-TYPO3-Update/automated-typo3-update#68