[TYPO3-core] RFC #17118: Bugfix: ForceAbsoluteUrl not working with installations in a subdirectory
Susanne Moog
typo3 at susannemoog.de
Sat Jan 22 16:31:15 CET 2011
On 22.01.2011 15:56, Susanne Moog wrote:
> Hey,
>
> This is an SVN patch request.
>
> Type:
>
> Bugtracker references:
> http://bugs.typo3.org/view.php?id=17118
>
> Branches:
> 4-4 and trunk
>
> Problem:
> If you set forceAbsoluteUrl (or enforce ssl, which does in turn force
> the absolute url) you'll get wrong links when linking to the current
> domain without config.typolinkCheckRootline set.
>
> Solution:
> At the moment HTTP_HOST is used as domain but TYPO3_SITE_URL should be
> instead. See the attached patches.
>
>
> Notes / How to test:
> Installation in a subdirectory:
> page.60 = TEXT
> page.60.value = test
> page.60.typolink.parameter = 123
> page.60.typolink.forceAbsoluteUrl = 1
attached v2 which uses rtrim instead of preg_replace (thanks SteffenG!)
--
What's worth the price is always worth the fight
Every second counts 'cause there's no second try
TYPO3 Core Team Member
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 17118_v2.diff
Type: text/x-diff
Size: 584 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20110122/5fb477d9/attachment.diff>
More information about the TYPO3-team-core
mailing list