TYPO3 Core

Perhaps it would help to get some error messages and your php.ini (at least those parts which are different from the original .ini distributed with PHP). I have PHP 5.1.4 running without any problems, and recently I just had a 5.0.x running with TYPO3 4.0.

Hello again!

I can't show you my php.ini file it's on a web hotel...
However, recently some modules started working (weird) still, there's some that don't work...

Access Module:
Parse error: syntax error, unexpected $end in
typo3/typo3/mod/web/perm/index.php on line 724

Filelist:
Parse error: syntax error, unexpected $end in typo3/t3lib/class.t3lib_foldertree.php on line 338

More errors...

User Admin:
Parse error: syntax error, unexpected $end in typo3/t3lib/class.t3lib_foldertree.php on line 338

Element Browser
Parse error: syntax error, unexpected $end in typo3/t3lib/class.t3lib_foldertree.php on line 338

Ok, this may seem VERY weird.
I opened the typo3/t3lib/class.t3lib_foldertree.php file and read the code.
I was just about to close the file (I didn't find any errors) when I saw an extra space in the class declaration. I thought "Well hey, this couldn't hurt" and removed the extra space and uploaded the file to my server.

This is the weird part: It worked!
All the modules that had the "Parse error: syntax error, unexpected $end in typo3/t3lib/class.t3lib_foldertree.php on line 338" error works fine now!

The lined that I changed:
Before: "class t3lib_folderTree extends t3lib_treeView {"
After: "class t3lib_folderTree extends t3lib_treeView {"

(The extra space was located between "t3lib_treeView" and "{")

I'm confused...

I am not sure about what to do with this one:

- Relates to a quite old t3 version
- The whitespace shouldn't do any harm, its probably an error in an optimizer or something like that
- There is in fact a double whitespace in the class declaration, but it would be really embarrassing to fix this, only valid reason could be CGL, but that is extreme nitpicking.

I would say: Don't waste anybody elses time any longer, set bug to resolved, no change required.

I agree:

• With the information given we were not able to reproduce thgis for more than 2 years and I think we won't be in the future.
• No response from the original poster for more than 2 years
• This version of TYPO3 has really reached its "end of life"

Reasons to close: See above.