Additional info: Yesterday I upgraded website "A" to Typo3 4.2.1, hoping this would also solve the PHP warning and error. But it did not. The update as such did not seem to cause any problem, but the BE is still not accessible. However, I can access the configuration tool in the normal way.
H. Hahn --------- H. Hahn schreef: > Hello, > > I did run into problems that seem to be caused by such an update. > I am running several websites. One of the, let me call it A, is hosted > with an ISP that offered PHP 5.0.5 or so. That could not run Typo3 > 4.2.1. So I asked them to upgrade to PHP 5.2.x. They did nit seem very > willing to do so. I even suggested that they may loose most of their > Typo3 customers if they don't upgrade. > > In the meantime I worked on another project for some weeks. Last week > I just checked again and to my amazement I found that they already > have upgraded to PHP 5.2.6. > > The website's front end (still on Typo3 4.0.5 at that moment) seemed > to run well, but the backend was inaccessible. Each time when I tried > to get the BE login screen, I got the following messages: > > "Warning: session_start() [function.session-start]: SAFE MODE > Restriction in effect. The script whose uid is 1152609 is not > allowed to access /var/tmp/ owned by uid 0 in > /usr/local/WWW/A/.5c2/p/pels4/htdocs/cheider2007/typo3/index.php > on line 202" > > and > > "Fatal error: session_start() [<a > href='function.session-start'>function.session-start</a>]: > Failed to initialize storage module: files (path: ) in > /usr/local/WWW/A/.5c2/p/pels4/htdocs/cheider2007/typo3/index.php > on line 202" > > This ISP's servers normally do not run in safe mode. So I had set safe > mode "on" in a php.ini file in cgi-bin. This has always worked and > still works (checked with PhpInfo). > > I deliberately did not try what happens when I switch off safe mode. > One reason for this is that two other websites (say "B" and "C") are > hosted with a differnt ISP, who runs PHP 5.2.3 and Linux (site A rus > on Unix), do not show this problem at all. So there must be something > wrong with the conversion from PHP 5.0 to 5.2(.6), I would say. > More details: > > Site "A": > CMS: TYPO3 4.2.1 > Server: Apache/1.3.37 (Unix) mod_ssl/2.8.28 OpenSSL/0.9.7d > Serverscripts: PHP 5.2.6 > Database: MySQL 5.0.26-log > OS: Unix (don't know what version) > Sites "B" and "C": > CMS: TYPO3 4.2.1 > Server: Apache/2.0.59 (Unix) > Serverscripts: PHP 5.2.3 > Database: MySQL 5.0.37-log > OS: Linux (don't know what version) > All three sites run exactly the same Typo3 version (all copies of the > same download!). > > Does anyone know what causes this problem and how I can solve it? > Please note that I have good reasons to prefer to run the sites in > safe mode. > Thanks in advance! > H. Hahn > > > Xavier Perseguers schreef: >> Hi Katja, >> >>> My virtual server system is now >>> - php 5.1.6 >>> - mysql 5.0.27 >>> >>> And as you know one must update to php 5.2 in order to update from >>> 4.1.x to TYPO3 4.2. >>> >>> I have many production sites in the server and now my big wonder >>> (and scare) is, if I order from my provider the php update 5.1.6 -> >>> 5.2 and mysql 5.0.27 -> 5.0.54, what happens (if anything). >>> >>> I guess the worst that could happen is that some extensions wouldn't >>> work...? >> >> Upgrading MySQL won't lead you into trouble, for sure! Now for PHP >> 5.1 to 5.2 I'm pretty sure it is the same as the big jump was PHP4 to >> PHP5 and will be PHP5 to PHP6 but otherwise, no problem I'm aware of. >> >> Upgrading 4.1.x to 4.2 may lead to problems but I personnaly upgraded >> a few websites without problems as all used extensions had been made >> compatible to the new version of TYPO3. >> _______________________________________________ TYPO3-english mailing list TYPO3-english@lists.netfielders.de http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
