Actions
Migration Typo3 v10 > v11¶
Some changes in php are needed to get QFQ work in v11.
Follow these steps:
- Install ig_ldap_sso_auth v3.7.1
- Install qfq v23.6.0 or higher
- Replace symlink typo3_src
- rm typo3_src
- ln -s /var/www/typo3_src-10.5.25/ typo3_src
- go to installtool: /typo3/install.php
- Upgrade: Run the upgrade wizard
- DO NOT Execute any of the upgrades that install extensions. Also not needed: "Sanitize existing SVG files in fileadmin folder"
- DO NOT execute "Migrate backend users' selected UI languages to new format."
- Maintenance:
- Database analyzer and apply the changes
- Flush Caches
- Environment: Directory Status" and autofix problems
- Upgrade: Run the upgrade wizard
1. Extensions Upgrades¶
Extension | Version |
---|---|
LDAP | V3.7.1 |
2. Custom CSS Files¶
The given token 'cd.stylesheet =' from uzh_cd extension would not work correctly anymore with relative paths in newer Typo3 versions. The reason are used pageSlugs, which changes the path for the given custom CSS in every visited page.
Here are two example results with following used TypoScript config: cd.stylesheet = fileadmin/templates/custom.css:
Working version:
Typo3 V8 with index.php and example page www.domain.com/index.php?id=10 -> www.domain.com/fileadmin/templates/custom.css
Not working version:
Typo3 V11 with pageSlug and example page www.domain.com/subpage -> www.domain.com/subpage/fileadmin/templates/custom.css
Solution: Use absolute paths for custom files in cd.stylesheet option.
Updated by Carsten Rose about 1 year ago · 22 revisions