Bug #77535
closed8.2.1 install blank page windows
0%
Description
For testing I have installed 8.2.1.
Windows Server 2012 R2
PHP 64-bit 7.0.9
IIS_IUSRS has all access rights
After calling the page, it automatically switched to .../typo3/sysext/install/Start/Install.php but displays only a blank page.
If I do exactly the same handling with 7.6.10, everything works fine.
I tried also 8.1.2, same problem as 8.2.1.
php_erroes.log does not show any problem, but I have not enabled typo3 error logging, because install does not work.
There are also no additional files created.
My Homepage (7.6.10) runs on the same environment (server, PHP, ...) without any problem.
Files
Updated by Christian Kuhn over 8 years ago
Hmmm, if this is a fatal somewhere early in the install tool boostrap or in one of the early install tool steps, the LocalConfiguration is not loaded, yet.
You may need to enable display_errors in php then, to see the full error with backtrace. Other than that, your PHP log should indeed log something if configured correctly.
I'd be interested in the outcome of your investigation.
Updated by Hans-Georg Althoff over 8 years ago
- File typo3_8.2.1.png typo3_8.2.1.png added
- File php.ini php.ini added
- File phpinfo().pdf phpinfo().pdf added
Hi Christian,
in the php.ini
display_errors = On
Right, there is nothing loaded.
I will attach the php.ini, a dir view and the php info.
Thanks,
Hans-Georg
Updated by Benni Mack about 8 years ago
- Target version set to 8.3
- Sprint Focus set to Stabilization Sprint
Updated by Christian Kuhn about 8 years ago
Hmm, we still should be able to see some error response. The early phases of the install tool bootstrap are configured to not suppress errors, I wonder why you don't see anything there.
It's hard for me to help you there since I don't understand why a) your install tool fatals and b) why you don't receive an error message.
I need to ask you to dig a bit deeper on that, sorry.
Updated by Hans-Georg Althoff about 8 years ago
Hallo Christian,
I have updated to 8.4 with the same result.
When I start the web page with test8.althoff-fam.de the sever changed to http://test8.althoff-fam.de/typo3/sysext/install/Start/Install.php. But I still get an blank page. And even if I try to switch firefox to the scource text (Quelltext), is still a blank page.
I have added the dir typo3conf and a file LocalConfiguratin.php with the following content:
<?php return [ 'SYS' => [ 'displayErrors' => '1', 'enableDeprecationLog' => 'file', ], ];
Now I got a massage, see attachment.
But I am not sure, if it was the right way to add the dir and the LocalConfiguration.php.
Updated by Hans-Georg Althoff almost 8 years ago
- Assignee set to Christian Kuhn
Hi Christian,
now the target version , original was 8.3 is now changed to 8.6.
Is ther still a small chance to get a solution???
Updated by Hans-Georg Althoff almost 8 years ago
- File Typo3-851.png Typo3-851.png added
Hi Christian,
I have tried it with 8.5.1 without succes.
If I call the V8 side with http://Test8.althoff-fam.de it automatically switched to http://test8.althoff-fam.de/typo3/sysext/install/Start/Install.php.
But nothing happend.
I have uploaded a file Typo3-851.png which shows the directory structure.
For me it seems, that the install.php has not added any additional file or dir.
The user IIS_IUSRS has the full access right for the whole Test8 dir.
Updated by Benni Mack almost 8 years ago
- Target version changed from 8.6 to 8 LTS
Updated by Jasmina Ließmann over 7 years ago
I can not reproduce the behavior. I have tested with your last version 8.5.1 and with the current master (8.7.0-dev) with the following settings:
Local:
Apache 2.4.18 (Win64)
PHP 7.0.3
Xampp:
Apache 2.4.23 (Win32)
PHP 7.0.9
When calling the test domain you will be redirected to /typo3/sysext/install/Start/Install.php and prompted to create "FIRST INSTALL". After the installation the TYPO3 CMS can be used and everything works as expected.
Updated by Claus Due over 7 years ago
Sorry to just barge in here, but this looks very much like a class loading issue, specifically that TYPO3 is unable to load the FluidTemplateCache class - but potentially also others (hidden behind this error).
What I know is:
- Windows file paths have a 255 char max length and it is possible that this class ends up in a path that's longer than this (it doesn't look like it based on your phpinfo, but I'm not 100% sure how those files get loaded if you don't use composer to install).
- Windows file system is case sensitive and that might have an effect.
- Fluid template cache SHOULD not be active in the install tool. If it is, that could indicate an issue with either third party extensions or the TYPO3 core itself (attempting to get or write a compiled fluid template when this is not expected).
I hope this maybe adds some inspiration to detect the actual cause. I'm unable to do any deeper testing since I don't have a Windows setup.
Updated by Christian Kuhn over 7 years ago
- Status changed from New to Needs Feedback
Updated by Hans-Georg Althoff over 7 years ago
I am not using Apache.
My configuration is:
Windows Server 2012R2 x64 virtuell
IIS 8.5 x64
PHP 7.0.15 x64
By the way on the same server TYPO3 V7LTS is running fine.
If I should test something special. please let me know.
Updated by Benni Mack over 7 years ago
- Target version changed from 8 LTS to Candidate for patchlevel
Updated by Riccardo De Contardi over 7 years ago
- Status changed from Needs Feedback to New
Updated by Susanne Moog almost 7 years ago
- Status changed from New to Needs Feedback
- Assignee deleted (
Christian Kuhn)
I just tested installation / running TYPO3 with the following configuration:
IIS 10
PHP 7.1
MySQL 5.5
Which works fine, so I'm kinda stumped what could be the problem.
Did you install TYPO3 via Composer or downloaded the zip?
Updated by Hans-Georg Althoff almost 7 years ago
I have installed now a test version with 8.7.9 and PHP 7.2.
It works now!!!
Also 9.0!
Updated by Riccardo De Contardi almost 7 years ago
- Status changed from Needs Feedback to Closed
- Target version deleted (
Candidate for patchlevel)
Hans-Georg, thank you for your feedback; I close this issue for now, as it seems solved for the current TYPO3 version.
Feel free to reopen it if the issue occurs again and/or you have more information about how to reproduce it, or open a new issue with a reference to this one. Thank you.