- INDIA • Managing iTUG - India TYPO3 User Group • Member of TYPO3 Content Team • Active Contributor of TYPO3.org Relaunch • Love my wife Urmi, Cricket and Reading
NITSAN increased sales 15% at last year’s campaign (if you need full campaign details, contact me) • I know, they always say, "What are the benefits of this?", "Can not we wait another year?", "Safety? Oh, nothing will happen! " • Reason to Upgrade ◦ More features and convenience in editorial work ◦ Greater security and faster troubleshooting ◦ Greater range and better mobile use through responsive web design ◦ Faster loading times and higher visitor satisfaction ◦ Latest software update is part of GDPR
Upgrade ◦ Security ◦ Visibility and Compatibility ◦ Usability ◦ Speed and Performance ◦ Read an interesting article by Mathias at https://goo.gl/n58TkH • Two types of Contracts with your customers ◦ Minor versions with SLA ◦ Major versions with Proposal
types like Standard, Premium • Support: Reaction and Resolve time • Updates: Core and Extensions • Report 1: TYPO3 Health • Report 2: Backup and Performance • Report 3: Cross-Platform Compatibility • Report 4: Monthly Activity If you want sample SLA template document, then feel free to connect with me.
Project Proposal ◦ Is major or minor upgrade? ◦ How many TER extensions installed and used? ◦ How many Custom extension installed and used? ◦ What templating method used? ◦ Is site does have multi-domain and/or multi-lingual feature? ◦ How many pages are in the site(s)? ◦ Try to prepare detailed report for your customer ◦ Check detailed report through EXT:ns_ext_compatibility
During TYPO3 Upgrade Projects • Extensions Compatibility Report • Automatic email notification for new version update • Compatible from TYPO3 4.x to 8.x • Export Feature for Customer • Extension Statistics Report • Server Compatibility Report • System Overview Report • Need Support? Connect with us at Github
replace with \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance() • Deprecation ◦ You may use quick and easy EXT:deprecationloganalyzer ◦ Should enable log: $GLOBALS['TYPO3_CONF_VARS']['SYS']['enableDeprecationLog'] = 'file'; ◦ It may includes deprecation of TYPO3, PHP, Fluid, TypoScript. ◦ Fix PHP PSR Standards with cool CGL PHP-CS-Fixer
LTS • Make a backup first (Code and Database) • Check the Server Compatibility Install > System Environment • Try the upgrade on a development system first, recommend to use Git • Uninstall extensions which are not compatible, before TYPO3 upgrade start • Use always symlink concept for TYPO3 core source code • Study the "Reports" module in the BE and take the recommended actions • Automated TYPO3 update: https://automated-typo3-update.readthedocs.io/en/develop/
(not in TER, maybe find out the latest compatible extension at Github) ◦ using a solution, which is more close to the core, (f.e. for content elements) ◦ dropping the functionality completely • EXT:smoothmigration (Specially useful for upgraders from TYPO3 4.x to 6.x) • EXT: compatibility6, EXT:compatibility7 extensions • Database charset should be UTF-8 [BE][forceCharset] = utf-8, [SYS][setDBinit] = set names utf8; • Try to get site’s specification from your customer.
and backend editors (freeze the content with [BE][adminOnly] = 1; • Temporary offline site EXT:ns_maintenance_mode • Read the release notes • Run scheduler to remove garbage • Debugging: Configuration Presets > Debug Settings • Enable the deprecation log and let it run for a while while the website is used to catch all deprecations
be deprecate from TYPO3 9 • Should setup rte_ckeditor instead of rtehtmlarea as it will be deprecate from TYPO3 9. https://www.nitsan.in/blog/post/simple-steps-to-configure-ckeditor-typo3/ • Keep aware with TypoScript Changes • Keep aware with Fluid Changes • Update TYPO3 Translation from Admin tools > Languages • Try to give quick demo to your customer for new TYPO3 version. #10 General Tips