[TYPO3-dev] Removing symlinks in V 4.0

[dan frost]

Rene,

Hi - hope you're well.

direct response / my 2 euro cents:

- if it makes deployment easier then yes
- if it makes cross-platform stuff easier then yes

As for existing extensions etc, then my view is 
that the expected change from v4->v5 of TYPO3 is 
so massive (classes, APIs etc) then just do it!

And besides, basically most TYPO3 "developers" 
work around what's available in the TYPO3 core - 
if the core changes, they will to.

dan


René Fritz wrote:
> Hi everybody
> 
> The core developers discussed today the possibility to change TYPO3 that 
> symlinks are no longer needed. The advantage is that installation is much 
> simpler, especially when people have a ftp account only.
> 
> I'm already working on a transition and have a site running without symlinks. 
> Only a few things needs to be fixed. In fact the whole backend worked already 
> (except the icons) after changing one code line .
> 
> The main changes are:
> 
> - t3lib/gfx/ will be moved to typo3/gfx/
> 99% of the icons are used by the BE only
> 
> - typo3/t3lib/ will be removed
> 
> - gfx/fileicons/ will be copied to tslib/media/ for FE usage
> 
> - new index.php for FE which include typo3/sysext/cms/tslib/index_ts.php
> - new showpic.php for FE which include typo3/sysext/cms/tslib/showpic.php
> 
> 
> All works fine if you use in your extensions:
> $BACK_PATH.'gfx/...'
> PATH_tslib
> 
> instead of 
> $BACK_PATH.'t3lib/gfx/...'
> PATH_site.'tslib/...'
> 
> And that's the point. I'm sure there are extensions out there which will break 
> because they use hardcoded references. But the good thing is when you use 
> symlinks again everything works like before.
> 
> What do you think?
> 
> @Kasper: please comment
> 
> René
>