[TYPO3-dev] BACK_PATH

Dmitry Dulepov dmitry.dulepov at gmail.com
Wed Oct 29 19:23:57 CET 2008


Hi!

Martin Kutschker wrote:
> BACK_PATH sucks. mod.php is better but it's only a sad little wrapper
> that includes the module script. More fun would be if a module is a
> class that implements a certain interface.

It will not be enough... Currently BACK_PATH must be set for
init.php to work. I actually never understood it. It is always
possible to find the back path. It should be perfectly traceable
from the current URL. If URL looks like
/typo3/extkey/module1/whateverelse/index.php, nothing prevents TYPO3
from calculating the back path. Patch should take TYPO3_mainDir into
account.

Even now BACK_PATH should not be necessary because we have
t3lib_div::getIndpEnv('TYPO3_SITE_URL').

Probably BACK_PATH is just a relic from old good times.

-- 
Dmitry Dulepov
TYPO3 translations support
My TYPO3 book: http://www.packtpub.com/typo3-extension-development/book
In the blog:
http://typo3bloke.net/post-details/max_os_x_use_php_help_in_chm_format/




More information about the TYPO3-dev mailing list