I am starting the process of updating TYPO3 to higher versions (from the base 6.2.X version). The process of updating to version 7.6.X was ok. Being logged in 6.2 version, I switched to version 7.6 and updated elements in InstalTool, plugins etc. The problem appears when I log out. After entering my login address, I have a blank page - white page without any code. I can log into InstallTool but unfortunately not to BE.
The [FE] page works fine after the update. Any ideas what went wrong or where is the problem?
first: blank page normally means: there is an error but all error information was disabled.
If you just changed the source it might be a mismatch between cache and source: clear all caches in Install Tool.
Also your first step should be look into the server log.
If that does not give enough hints enable all debugging and error information in the Install Tool.
If that still gives no clue: disable all extensions (remove from PackageStates.php and don't forget to clear caches afterwards, maybe manually too)
Related
I tried to upgrade from 10.x to 11.5.8 and nothing was working anymore. If I try to open the url I recieve the following error message:
Fatal error: Declaration of TYPO3\CMS\Extbase\Mvc\Controller\AbstractController::processRequest(TYPO3\CMS\Extbase\Mvc\RequestInterface $request, TYPO3\CMS\Extbase\Mvc\ResponseInterface $response) must be compatible with TYPO3\CMS\Extbase\Mvc\Controller\ControllerInterface::processRequest(TYPO3\CMS\Extbase\Mvc\RequestInterface $request): Psr\Http\Message\ResponseInterface in C:\inetpub\wwwroot\typo3\sysext\extbase\Classes\Mvc\Controller\AbstractController.php on line 243
So the next step was to disable all my extensions.
If I try to open the backend, I recieve the same message as above.
The next step was to use the Install Tool, which was working. But if I try to use some functions like "Upgrade Wizard", "Analyze Database Structure", "
Remove Temporary Assets", ....
But the sys_log and the log files under typo3temp are empty!
And also the firefox degugger is not showing any information.
PHP 7.4.15, no composer installation and chaches all deleted!
What should I do next?
The first error message says that there are Extbase extensions which are not compatible with v11. See https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/11.0/Breaking-92502-MakeExtbaseHandlePSR7ResponsesOnly.html
For the second error I'd recommend to look into the dev console of your browser. There you might see more information about the error when there is nothing in the logs. (Maybe there is an error when writing log?)
The mentioned file "AbstractController.php" exists only in version 10 and was removed afterwards.
So TYPO3 is using some old files, probably from the file-cache.
You wrote that you use an installation without composer-setup. Those installations have the file-cache saved in typo3temp/var/cache. This folder can be deleted completely and will be rebuilt automatically.
Afterwards TYPO3 version 11 should run and the error-message should never be shown again.
Due to my experiences with updating TYPO3 to a new mayor release, i did the following steps.
Renamed fileadmin dir
Deleted all TYPO3 dirs
Installed the new version of TYPO3
Start TYPO3 from scratch with an new database (use the ID and passwort from the final database, use the right sitename)
Rename the fileadmin dir back to fileadmin
Go into LocalConfiguration.php and switch under DB to the original database
(Maybe) enable 'debug' => true, for BE and FE and set 'displayErrors' => 1, under SYS
Try to start the BE, if failed go to the Install tool.
Start Upgrade Wizard under Upgrade
In the Install tool start the Analyze Database Structure, but be carefull. that you dont't delete any database of your extensions, which not installed yet!
Now the BE should work now and you can upgrade your extensions!
Good Look.
I got to work on a Typo3 page and I have to say I'm at the very beginning if it comes to TYPO3.
So I wanted to fix a bug and updated the plugin "fluidpages" from version 4.1.0 (I guess) to 4.3. That cause the "Oops, an error occurred!" in the backend and frontend, so I dont have access from that side. I still have the FTP login for the website. The version of TYPO3 is 8.7.18.
The errorcode I get is that one:
Could not analyse class:
"FluidTYPO3\Flux\Configuration\ConfigurationManager" maybe not loaded
or no autoloader?
Class FluidTYPO3\Flux\Configuration\ConfigurationManager does not exist
So does anyone know what I need to do?
From my research I think I need to update another plugins to make it back to work? And can I update them just by uploading them through FTP?
Thanks in advance!
Edit: After I tried to get the old version of the plugin running, I'm getting this error code from the log file:
Mon, 17 Feb 2020 22:59:56 +0100 [ALERT] request="fec23f8baf6dc" component="TYPO3.CMS.Frontend.ContentObject.Exception.ProductionExceptionHandler": Oops, an error occurred! Code: 2020021722595594039a4d - {"exception":"TYPO3\CMS\Extbase\Mvc\Exception: The default controller for extension \"Flux\" and plugin \"Page\" can not be determined. Please check for TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin() in your ext_localconf.php.
You can enter the Install Tool via https://example.org/typo3/install.php and start with Check for broken extensions. If that doesn't yield the extension in question, you can always manually change the PackageStates.php file and remove the extension you want to unload. Afterwards you should flush all caches through the Install Tool.
In the long term you should consider a few things:
Use a local development environment which mirrors your production environment. You can safely perform all steps without any risk here before deploying.
Use a deployment strategy/tool which allows for rollbacks. This allows you to quickly revert to a working version of your instance in case all other checks have failed. A simple but flexible solution is Deployer, you'll need SSH for this though.
Have you tried dumping autoload from Install Tool? Generally, it would help for the class not loaded problem. Otherwise, you may want to check the log at typo3/temp/var/log/ and find the errors in code.
I was fixing things on a not well-maintained typo3 installation and it resulted in blank pages of frontend, backend and install tool.
I wanted to fix extensions because the powermail-extension was not working anymore even after updating to latest compatible version (tried emptying cache and database compare).
I deactivated an extension "compatibility6" to see if it was interfering and since then all pages have been blank including Install Manager. I reactivated the extension via PackageStates.php, emptied the cache but it did not change anything. I was not able to see any error messages even though I set the parameter in LocalConfiguration.php which made it hard to try to find out what is wrong. Then I restored a backup using vmware. Still, backend and frontend are blank.
I am using Apache and Typo3 7.6.23.
I do not know what might be causing the problem and would like to know what else to look for?
It means you have a PHP error there. The first thing would be to examine logs. If you see anything like "class not found", then your next action would be composer dumpautoload --no-dev.
Long time ago I had an article about blank pages in TYPO3 FE. Not up to date but still can be helpful: https://www.dmitry-dulepov.com/2009/03/blank-empty-page-in-typo3.html
Dmitry already wrote it: you have an error.
In production environment nothing is shown for not revealing any information about your system.
So the only information about the error can be found in the error log of your webserver.
What can you do to get more information about your error?
Enter the install tool and switch to develop mode. This will also enable deprecation logging into a file. Try to avoid filling your system with deprecation warnings by disabling deprecation logging.
Disable the default exceptionhandler by adding this to your typoscript setup:
config.contentObjectExceptionHandler = 0
Now you should see a call stack instead of blank screens.
Be aware that this might reveal confidential information from your system.
because of this you should use a copy of the live-system.
I am using Tiki Wiki, and I change to login with an LDAP server, I already made all the configurations but when I try to login with a user from my LDAP server give me a blank page. I saw a solution on TIKIWIKI doc's, they say to clear the cache but I dont know how to clear.
You can clear the Tiki caches by going to tiki-admin_system.php when logged in as an admin, there is a link on the Settings part of the main Tiki menu, and one on the Quick Admin module (if enabled).
You can also clear the cache from the command line by doing
php console.php cache:clear
More info here
(however, if you are running Tiki 16.2 there is a bug in LDAP which also produces this sort of blank page error. This will be fixed in 16.3 which will be released soon, in the mean time you can download a nightly build from here)
I have a plain naked TYPO3 8 lts installation.
But I cant login with the backend user.
Install Tool works fine
When I create a new BE user in install tool it does not work as well ...
any ideas?
Check in Localconfiguration the [BE][loginSecurityLevel] and change it to normal if it is rsa
For me the solution was deleting the cookies from the browser, then login form works good.
I ran to a problem where I couldn't login to backend, even if I had [BE][loginSecurityLevel] set to normal. Nether did it work on a unix system or windows. The reason I found out was, because the extension 'sv' was disabled (not in PackageStates.php array).
So I went to PackageStates.php and added following to the array:
'sv' => [
'packagePath' => 'typo3/sysext/sv/',
],
Before that happened, I downgraded TYPO3 from 9 to 8. I was able to log in first, but not the next day, after the first logout.
This extension contains core default services.
Use the Debugger for your browser, e.g. Firefox Developer, and check if an error is given there.
Loading failed for the <script> with source “http://www.my-typo3-website.de/typo3/sysext/core/Resources/Public/JavaScript/Contrib/jquery/jquery-3.2.1.js”.
If you copy and past the above url into a web browser, you will see this outpu:
The requested URL /typo3/sysext/core/Resources/Public/JavaScript/Contrib/jquery/jquery-3.js was not found on this server.
The file name jquery-3.2.1.js has been abbreviated into jquery-3.js!
It can happen that the jquery used by the login form is not included as needed. This can happend by a Rewrite rule in the .htaccess file which transforms the filename jquery-3.2.1.js into a smaller name jquery-3.js which will not be found, because it simply does not exist on the file system.
At least you should try out the original .htaccess file named "_.htaccess" which is shipped with TYPO3.