Project

General

Profile

Actions

Bug #21632

closed

Can't access 'Basic Configuration' on a fresh install

Added by Johann Maurer over 14 years ago. Updated almost 13 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2009-11-21
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Creating a new installation with typ3_src+dummy-4.3.0RC1 i'm able to login to the Install Tool. But can't set the basic's. On a click on 'Basic Configuration' this message ist displayed:
-- The current username, password or host was not accepted when the connection to the database was attempted to be established! --

Setting the connection parameters is not possible.

(issue imported from #M12691)


Files

phpinfo.html (23.6 KB) phpinfo.html Administrator Admin, 2009-11-24 17:45

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #20786: PHP-5.3 Warnings concerning missing timezone settingsClosedTobias Liebig2009-07-27

Actions
Related to TYPO3 Core - Bug #21824: Install Tool is not able to select database in 1-2-3 modeClosed2009-12-08

Actions
Actions #1

Updated by Johann Maurer over 14 years ago

Sorry! Install tool works when I use 1-2-3 Install before!

Actions #2

Updated by Chris topher over 14 years ago

I thought the 1-2-3-installer would come up automatically. But it doesn't?

Actions #3

Updated by Johann Maurer over 14 years ago

I'm not using 1-2-3 install for all my installation until now! I started with setting ENABLE_INSTALL_TOOL in typo3conf and then typo3/install/. The Install Tool started with asking me a new install password. Next call opened part 5 'All Configurations'. From this point on I could not start 'Basic Configuration'.
HTH ?

Actions #4

Updated by Markus no-lastname-given over 14 years ago

I am experiencing a similar or the same problem.
Neither the 1-2-3 Installer nor the Advanced Installer will write any changes to localconf.php (Installer Password changes, DPI number for TTF, Database connection). After submitting the above err msg will show.

Permissions have been double checked; I have no reason to believe that apache cannot access/write there. Database connection (MySQL 5.1) works on the console via TCP and socket. This is a manual install on Debian sid.

BTW: After Install on my system the 1-2-3 comes up as default.

Actions #5

Updated by Markus no-lastname-given over 14 years ago

Another observation:
I manually inserted these 3 lines

$typo_db_username = '*********'; // Modified or inserted by TYPO3 Install Tool.
$typo_db_password = '*********'; // Modified or inserted by TYPO3 Install Tool.
$typo_db_host = '************'; // Modified or inserted by TYPO3 Install Tool.

after the

  1. INSTALL SCRIPT EDIT POINT TOKEN - all lines after this points may be changed by the install script!

line. The install tool then worked fine and was also able to modify localconf.php without a problem in either mode (1-2-3/advanced). Maybe some database checks are run to early... ??

Actions #6

Updated by Jochen Weiland over 14 years ago

I can confirm the same behaviour:

trying to set db parameters through either the 1-2-3 tool or the basic configuration screen in a fresh installation does not work, since the parameters are not written to localconf.php

If you enter the database parameters manually in localconf.php, subsequent writes to localconf.php work. You then can also change the db parameters through the install tool.

Environment: PHP 5.3.0, TYPO3 4.3RC1, Gentoo Linux, safe_mode is off

Actions #7

Updated by Oliver Hader over 14 years ago

Markus, which PHP version are you using?
I sucessfully installed TYPO3 4.3-RC1 on two Mac OS X server using PHP 5.2 and PHP 5.3.
Can someone dig into it deeper? Thanks in advance!

Actions #8

Updated by Markus no-lastname-given over 14 years ago

I could reproduce the problem on debian's latest (experimental) PHP apache module
libapache2-mod-php5 5.3.0-3
If it helps I can try and downgrade tonight to sid's libapache2-mod-php5 5.2.11
Any pointers how to enable verbose debugging and provide more information?! Have no typo3 developing background...

Actions #9

Updated by Nikolas Hagelstein over 14 years ago

Confirmed on php4.3rc1 fast_cgi php 5.2.11

Actions #10

Updated by Oliver Hader over 14 years ago

Phew, does this occur in TYPO3 4.2 as well?
Are there any settings for Suhosin active on the server?

Actions #11

Updated by Markus no-lastname-given over 14 years ago

I tried Typo3 4.2 on the same machine, which works. (Although generation of an encryption key fails...)

Typo 4.3RC1 Installer (Advanced Mode/Basic Settings) reports "Suhosin/Hardened PHP is not loaded".
I also attached my phpinfo report. Maybe this helps.

Actions #12

Updated by Oliver Hader over 14 years ago

Markus, TYPO3 4.2.10?

Actions #13

Updated by Markus no-lastname-given over 14 years ago

Yes, Typo3 4.2.10.
It can set the DB connection parameters to localconf.php.

I also installed PHP 5.2.11 (as apache module) which yields the same problem for Typo3 4.3RC1.

Actions #14

Updated by Oliver Hader over 14 years ago

Can somebody give me access to the install tool on a TYPO3 development installation where this occurs?
You can contact me via privat mail to

Actions #15

Updated by Markus no-lastname-given over 14 years ago

"I also installed PHP 5.2.11 (as apache module) which yields the same problem for Typo3 4.3RC1."

I have to withdraw this information; I am sorry - with 5.2.11 and a fresh install of Typo3 4.3RC1 just now works. Don't know what I did wrong the last time. With PHP 5.3+ it still doesn't work.

Actions #16

Updated by Oliver Hader over 14 years ago

Markus provided me access to his development system on PHP 5.3.
It turned out that a missing timezone-setting in php.ini caused this problem since before the localconf.php is written a temporary file is created using date values.

Thus, concerning PHP 5.3, this is no TYPO3 bug.

If others can reproduce it with PHP 5.2, please tell. Maybe you can give me access to your development systems - just write to

Actions #17

Updated by Steffen Kamper over 14 years ago

there is a pending patch for this too in core list: #20786

Actions #18

Updated by Lars Smit over 14 years ago

I can confirm that a missing timezone-setting in php.in caused the problem. Simply setting the timezone-setting solved the problem.

Actions #19

Updated by Chris topher about 14 years ago

The fix for #20786 is part of TYPO3 4.4beta2.

Can someone please test, if the problem still appears with that version?

Actions #20

Updated by Dave almost 14 years ago

I just had the same problem. TYPO3 4.3.3, on PHP Version 5.2.12 with Suhosin Patch 0.9.7 (FreeBSD ports)

BTW my timezone-setting was set in the php.ini. I would dig further but I am time limited.

I did a test install of TYPO3 4.4beta2 and the problem HAS gone away for me in that version.

Actions #21

Updated by Oliver Hader almost 14 years ago

Hi Dave,
did you have the same problems with the "basic settings" part? Was your localconf.php file updated with the accordant settings?

Actions #22

Updated by Dave almost 14 years ago

The problem was for both the 1-2-3 Install and Basic Configuration. It wouldn't get past the error message. I would have to physically go in and add the connection settings in localconf.php manually to get anything working. Once the connection vars existed in localconf.php I could then modify as normal from the install tool.

Actions #23

Updated by Sebastian Schindler almost 14 years ago

Problem still exists. When not using the 1-2-3 install wizzard I could set the databaseuser, password and hostname. When this settings has been written to localconf.php I still get the information "Could not connect to SQL database!". At the point I normally could select a database or create a new one only the message "(Can only select database if username/password/host is correctly set first)" is shown. The username, password and host are correct.

TYPO3 Version 4.4.0
PHP 5.2.6-1+lenny8
MySQL 5.0.51a-24+lenny4

Actions #24

Updated by Susanne Moog almost 13 years ago

  • Status changed from Needs Feedback to Closed
  • Target version deleted (0)

I could not reproduce this problem anymore and there were no new therefore close this bug. If this is still a problem, please just reopen the bug report.

Actions

Also available in: Atom PDF