automated-typo3-update issueshttps://git.higidi.com/Automated-TYPO3-Update/automated-typo3-update/-/issues2017-05-11T07:54:20+02:00https://git.higidi.com/Automated-TYPO3-Update/automated-typo3-update/-/issues/68Check Database2017-05-11T07:54:20+02:00Daniel Siepmanncoding@daniel-siepmann.deCheck DatabaseObviously 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 sho...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
- [ ] Apply PageTSConfig checks to database, see #54
- [ ] Apply UserTSConfig checks to database, see #54
- [ ] Check whether removed fields contain something that will be lost during migration?
- [ ] Check what TYPO3 does between the versions to create further related issues.Nice to haveDaniel Siepmanncoding@daniel-siepmann.deDaniel Siepmanncoding@daniel-siepmann.de