[TYPO3-dev] TYPO3 V4.0 produces coredump

Alex alex at pluvia.net
Mon Apr 10 01:48:25 CEST 2006


> I'm sorry if that's the case. It was meant as an addition (not
> replacement!) to the release notes, and by reading the mailing list
> posts, it seems like people are doing exactly those things wrong, which
> are listed on the Upgrade wiki page, so it would have helped them.
> 
Hmmm...I see now why I wasn't successful. I'm using the symlink setup as 
described in the install docs (Using the source distribution effectively 
-> 
http://typo3.org/documentation/document-library/installation/doc_inst_upgr/current/view/3/3/ 
)

> Well, you *have* to remove the old typo3/ directory (and others) before
> you copy the new 4.0 source into your installation. That's exactly the
> point: You can't upgrade by just copying all new files *over* the old
> source, but have to move the old source completely out of the way (that
> is by removing it or moving it to a backup location).
> 
On my server those aren't really folders or files but merely symlinks. 
So I'm not actually "copying over" anything ;).

> I agree. Could you please coordinate that effort, and gather all upgrade
> related documentation on a wiki page? Than we can put that finished
> upgrade guide as an article or manual to typo3.org.

What confused me was that your instructions never mentioned (re)creating 
any of the symlinks. Since I don't know how many people are actually 
using the "symlink setup". I'll just add my upgrade Method to the Wiki 
rather than change yours.

It would probably be possible to create a "smallish" shell script to do 
all of the removal of symlinks, recreation of symlinks and setting of 
permissions. However, until there is more consistency on how people 
install typo3 this would only cause more problems right now. In the 
future, there could be a shell script that automates the unix install 
(permissions, symlinks etc.) which would bring more manageable 
consistency to the installed environment and could make an upgrade 
script a real possibility.




More information about the TYPO3-dev mailing list