Upgrade composer dependencies (mainly TYPO3 v9) #340
Comments
josefglatz
pushed a commit
that referenced
this issue
Nov 20, 2018
composer req roave/security-advisories:dev-master --dev Related: #340
josefglatz
pushed a commit
that referenced
this issue
Nov 20, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 20, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
…stallable Since there are still some used 3rd party extensions which are not compatible to TYPO3 >= 9.0, we have to disable them per default. Some of them will be added per default, if they are updated to work with TYPO3 9 LTS. # composer.json require removals - apache-solr-for-typo3/solr (install only if you need it) - causal/image_autoresize - cmsexperts/unlocalizedcrop due the lack of v9 support - dmitryd/typo3-dd-googlesitemap is superfluous - dmitryd/typo3-realurl is superfluous too - fluidtypo3/vhs must be installed on a per project step as not every TYPO3 project needs it as a base - georgringer/backend-debug is superfluous - georgringer/deprecationloganalyzer isn't v9 ready yet - georgringer/logging isn't v9 ready yet - instituteweb/unroll is superfluous - lochmueller/staticfilecache need - spooner-web/be_secure_pw isn't v9 ready yet - t3monitor/t3monitoring_client isn't v9 ready yet # composer.json require typo3 core packages The required packages were updated based on the available one after the TYPO3 upgrade. Features like felogin must be installed on a per project step. The amount of per default required core packages is a purely subjective decision based on my usual project defaults. # composer.json suggest The suggested section was removed. It inflates the file unnecessarily. An alternative will be added within the documentation of the project. # composer.json repositories: remove ckeditor-dev The repo and the package was removed, as this repo is mainly only relevant if you write CKEditor plugins. If you need the CKEditor core as a reference for writing plugins you have to import it in your project by your own. # composer.json require-dev removals - mask/mask was removed due their lack of v9 support - ichhabrecht/mask-export was removed - macopedia/mess_detector was removed - maxserv/yaml_configuration was removed and needs some love to work again with v9 - sgalinski/lfeditor was removed and needs some love to work again with v9 Related: #340
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
- update misc. TYPO3 core API calls - update EmConfiguration to support upgraded extConf API Related: #340
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
as suggested by the TYPO3 documentation about extensions. Related: #340
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
…pped by the TYPO3 core - custom robots.txt controller is removed - pages.tx_theme_robot_* fields are removed - pages.tx_theme_opengraph_* fields are removed - pages.tx_theme_twitter_* fields are removed - superfluous cropVariants configuration is removed - opengraph, twitter and robot TCA palettes are removed Related: #340
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
as they are not available in TYPO3 9 LTS context Related: #340
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
The field was removed in the TYPO3 core. I really like that! https://forge.typo3.org/issues/82878 Related: #340
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
according to official extension development documentation Related: #340
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 21, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 22, 2018
- Migrate all of them as long as the operational blindness
does not occur
- This also adds a body class `develop-local`
Some Examples:
[getTSFE().beUserLogin === 1]
[applicationContext matches "/^Development/"]
[applicationContext matches '/^Production\\\\\\\\/Dev/']
["{$site.dummyFrontend}" == 1]
[{$theme.debug} == 1]
[tree.level == 2]
Related: #340
josefglatz
pushed a commit
that referenced
this issue
Nov 22, 2018
as it might be not needed anymore, due the new site handling Related: #340
josefglatz
pushed a commit
that referenced
this issue
Nov 22, 2018
…Language Please see https://forge.typo3.org/issues/86915#change-391029 for more details about the issue in the core (9.5.1) Related: #340
josefglatz
pushed a commit
that referenced
this issue
Nov 22, 2018
Per default, a normal TYPO3 page is used to display the 404 error Related: #340
josefglatz
pushed a commit
that referenced
this issue
Nov 22, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 22, 2018
add some working config options. See https://forge.typo3.org/issues/86978 for the core bug Related: #340
josefglatz
pushed a commit
that referenced
this issue
Nov 22, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 22, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 22, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 24, 2018
josefglatz
pushed a commit
that referenced
this issue
Nov 27, 2018
…se the site configuration in TYPO3 9 LTS config.absRefPrefix -> removed / is set to "auto" if we use site configuration config.typolinkEnableLinksAcrossDomains -> removed (not needed anymore) config.linkVars don't need any L var Related: #340
|
IMO issue can be closed @josefglatz |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and all other activated packages
The text was updated successfully, but these errors were encountered: