Bug #14205
closedmisleading warnings in 123 setup
0%
Description
HI not sure if I'm in the rite place but I found a big problem with setup. I am connected to a remote host who is running a linux appache 3.1 system.
During my setup sequence, when I was in the 123 setup, there was a warning about a posssible problem and it looked as though I should address that issue before I continued.
However, as soon I clicked on the link I found that the warning was telling me to diable the install feature once done with install, fine.
Problem is, because I got there before I was finished with install, I was kicked out of the setup.
As I had not completed the install I can do nothing.
I have removed entire package typo3 and the quickstart and then did a full reinstall, however I am NO further ahead.
I can get to the directory tree in Typo but no Frontend.
Also I could find the tool installer and tried to access it, I have the password but I have no idea as to the user name (or if this would even help)
I have been trying for days to get around the original install but can't fool the program.
Also I have got to the admin panel and signed in but I get errors - not unexpectedly as the database has yet to be initiallized...
Warning: fopen(/home/zeek/zeek/typo3/typo3temp/charset_iso-8859-1.tbl): failed to open stream: No such file or directory in /raid/home/zeek/zeek/typo3/t3lib/class.t3lib_div.php on line 2012
(Warning: Cannot modify header information - headers already sent by (output started at /raid/home/zeek/zeek/typo3/t3lib/class.t3lib_div.php:2012) in /raid/home/zeek/zeek/typo3/typo3/template.php on line 596)
when I was kicked out during initial install I got "can not find localconf file. I still get that also even after I have entered my user name and passwords directly.
QUES: Isn't there a way to bypass the security protocals to "reinstall" as from scratch?
I sure would like to get this thing running.
thanks in advance
Glen
(issue imported from #M164)
Updated by Ingmar Schlecht over 20 years ago
I think your problem is something that should be posted to and discussed in the install mailinglists rather then here in the bug tracker.
I'm thus closing this bug.