https://stackoverflow.com/questions/21671496
italiano
english
français
española
中国
日本の
العربية
Deutsch
한국어
Português
RussianSome simple ways to find out the errors/issues after upgrading typo3!
Check the symlinks. Usually we point the typo3, t3lib, index.php to the folders/files inside typo3_src folder which is symlinked to the typo3 source package (typo3_src_4.5 etc). Sometimes even after symlinking the source folder, symlinks may point to the older version. In this case we need to symlink the typo3, t3lib &index.php to the folders/files inside the typo3 source folder after symlinking the typo3 source (typo3_src) folder to the new typo3 source.
Use upgrade wizard. If you’re not sure whether the upgrade is complete or not then check the “Install tool > Upgrade Wizard” for current typo3 version and do the steps mentioned in it.
Set Display errors to 2. Getting a blank backend or front end is very common after upgrade. This might be due to some php errors, compatibility issues etc. An easy way to find the error is to set “Install tool> All Configuration > displayerrors” to 2 and add our IP address to “Install tool> All Configuration > devIPmask” so that the errors will be visible only for our IP.
Clear typo3temp. Empty the typo3temp folder. Otherwise rename the existing one and create a new one.
Delete the cached files. Remove the typo3_cached files in “typo3conf” folder.
Find out extension conflicts. If none of the above methods allow you to work with the new typo3 version, then there’s a chance for extension conflict. A simple way is to rename the “typo3conf/ext” folder (to something like “typo3conf/ext_renamed”) and create a new empty “typo3conf/ext” folder. Check the backend. If it works fine, then it’s clear that there’s an extension conflict. Bring back the “typo3conf/ext” folder and test the extensions inside it (here also the renaming method can be used – rename the extensions one by one and check whether the backend is ready or not).
Check the error log. Go through the error log and findout what’s missing or what’s problem with our new installation. Make sure that source file/folder permissions are correct.
Debug “typo3conf/localconf.php” file. Comment all the details in localconf.php file except the data needed for database connection. If backend is available after doing so, the comment it sectionwise and continue debugging. Make sure that required extensions mentioned in localconf.php are available. (like : $TYPO3_CONF_VARS['EXT']['requiredExt'] = ‘cms,lang,sv,restrictlogin’; ) We can also find out the errors by adding ini_set(‘display_errors’,'On’); at the end of localconf file.
Note: While upgrading to typo3 4.6 make sure that you’re using Php 5.3 and the SOAP module is enabled. Before you upgrade always have a look at the typo3 version requirements in typo3 wiki.
Other notes
Shortcut links not working after typo3 upgrade for multilingual sites.
In multilanguage websites after typo3 upgrade the shortcuts works fine for default language pages but not in other languages. The reason is – for alternative language the pages will be in “Standard” mode which worked old typo3 versions but not in latest typo3 versions. So just changing “Standard” mode to “Shortcut” mode for alternative page languages will solve the issue.
New extension manager.
The new extension manager may appear a little bit confusing but it’s very simple and efficent. Even though our eyes may not find the options that we’d used earlier very easily, they still exist. eg: How to get the old version of a typo3 extension?
Merging css files and java-script as a built in feature.
From typo3 4.6 onwards we can merge and minify the css and js files that are used in our website by using the new typo3 features like: config.concatenateJsAndCss = 1 config.concatenateJs = 1 config.concatenateCss = 1
Check status report.
typo3 status report notice Check the typo3 status report to get an overview of the site’s parameters as well as any problems detected with the installation.
Reference link: How to upgrade typo3?
