typo3 error while installing, no error log available - typo3

while installing typo3 I faced some issues and now I'm stuck..
I just get the error page
"Oops, an error occurred!"
What's the best way to find the error?

Things you could do:
open typo3conf/LocalConfiguration.php and set displayErrors to 1 in the SYS section
have a look in the TYPO3 log file (see below)
go to domain.tld/typo3/install or domain.tld/typo3/install.php and check for errors there
Which TYPO3 version do you use? If it's TYPO3 8.7 or higher, you can find the error log in typo3temp/var/logs. In older versions, it's just typo3temp/logs.

Related

TYPO3 Upgrade Psr Problem vom 10.x to 11.5.8,

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.

Directory Status - Directory / should be a directory, but is of type link

I'm trying to update TYPO3 (current version: 9.5.20) to the most recent version, but I'm currently stuck at the following error message when using the 'Update Core' functionality to update to 9.5.32:
Automatic TYPO3 CMS core update not possible: Folder structure has errors or warnings.
I went to 'Environment' -> 'Directory Status' and saw the following error:
Directory / should be a directory, but is of type link
How should I go about fixing this error? I saw a handful of bug reports on the TYPO3 bugtracker but no clear way to fix this issue. Perhaps there is an option to temporarily disable the directory status checks?
The intention is obviously to update to the most recent TYPO3 version, but I'm starting with 9.5.32 as a first step.
Below are the errors I get when trying to update to v9.5.32:
Thanks in advance for the help! :)

Flux Error: Invalid configuration: "vendorName" is not set after upgrade to Flux 9.4 and Typo3 9.5

I have to make an update from Typo3 8 to Typo3 9.5 LTS. And i have some trouble with the Flux extension which causes some strange errors. I have used Flux 9.4.2 (latest) and Typo3 LTS (9.5.22). I have used Composer for the new version perhaps that causes the problem.
I have followed all the steps in this tutorial and some others instructions but all of them ends in the same error.
https://sigalambigha.home.blog/2020/04/29/how-to-migrate-fluidcontent-to-flux/
In Backend i get the following error:
And in the Frontend i get this error:
This depends on the Flux element which is on that page the Slider element. The Plug & Play configuration is disabled because of some other errors. Perhaps now i missed something in my configuration but i can't find something in the documentation to configure.
Edit
I have made some more tests an i think the problem is that the newest version of Flux is not really compatible with Typo3 9.5. So i changed to version 9.3.2 which is working better but has other bugs.
Make sure these 3 things in your template provider extension are set correct:
Register the provider extension key using the Vendor.ExtName syntax, not ext_name. Here is an example:
\FluidTYPO3\Flux\Core::registerProviderExtensionKey('Nng.MyExtname', 'Page');
\FluidTYPO3\Flux\Core::registerProviderExtensionKey('Nng.MyExtname', 'Content');
Place the above code in the ext_localconf.php of your extension, not the ext_tables.php. You can find this hint hidden in the documentation.
In older versions of FLUX you might also need to create a ClassAliasMap in EXT:myextensionkey/Migrations/Code/ClassAliasMap.php. Here is a simple example.
Did you try to set a small condition for the used parameter if it's null? that maybe can give an error message instead of the error in the page.
Or you should see if there's any error in the namespace
After upgrading Flux to Typo3 9.5 then you have to register "VendorName" with your content element using Typoscript like i did below.
tt_content {
mytemplate_wrapelement.20.vendorName = <vendorname>
}
here mytemplate is my template provider extension.
Wrapelement is the content element.
I was getting same error.

Typo3 cal (calendar Base) extension update error

have just updated typo3 calendar base extension and suddenly the typo3 backend and frontend displays disappeared and all i see is a blank display. This is the exact error I'm getting
... PHP Fatal error: require_once(): Failed opening required '/var/www/html/typo3conf/ext/cal/res/class.tx_cal_isCalNotAllowedToBeCached.php' (include_path='/var/www/html/typo3/contrib/pear/:.:/usr/share/pear:/usr/share/php') in /var/www/html/typo3temp/Cache/Code/cache_core/ext_localconf_6068a12d352941d6e5ee7dd31447d561068faea3.php on line 3617....
how do I clear this to get my typo3 back? I'm using typo3 6.2.12, my efforts of even deleting the cal extension don't work!
thanks in advance
Open the install tool and clear all caches in the "Important Actions" section. It seems there is some old code from before the update still cached. Note the path of the file doing the include, it is in typo3temp/Cache/Code/.

The page is not configured! [type= 0][]

I've migrated from typo3 4.1 to 4.5 LTS now I got this error.
The page is not configured! [type= 0][]
I've checked DB analyser and fixed the table issues any ideas. Please revert
Apparently TYPO3 can't find TypoScript use Web > Template tool and check if record exists, also if it includes TS from external files, make sure the files exists.