Bug #26494
closedhttps is always identified as an external page even for internal pages
0%
Description
Following configuration:
in the root template:
config.extTarget = _blank
In the Backend, edit a page, set in the tab "Behaviour" used protocol to https:// and set the link target to _self.
If i click now on the link to this page in the FE (the link is provided properly with https) i always get a new tab opened in the browser, even if i set _self into the link target input field.
So, the link target field has no effect.
SteffenR told me, that if a new url schema is set or a "." is set before a slash in a link, the link is identified as external.
The problem is in line: 5530 in tslib_content of branch 4-5if ($pU['scheme'] || ($isLocalFile != 1 && $urlChar && (!$containsSlash || $urlChar < $fileChar))) { // url (external): If doubleSlash or if a '.' comes before a '/'.
Updated by Steffen Ritter over 13 years ago
- Category set to Frontend
- Status changed from New to Accepted
- Priority changed from Could have to Must have
- Target version set to 4.5.3
- Estimated time set to 3.00 h
Updated by Oliver Hader over 13 years ago
- Target version changed from 4.5.3 to 4.5.4
Updated by Oliver Hader over 13 years ago
- Target version changed from 4.5.4 to 4.5.6
Updated by Chris topher about 13 years ago
- Target version changed from 4.5.6 to 4.5.8
Updated by Ernesto Baschny almost 13 years ago
- Target version changed from 4.5.8 to 4.5.12
Updated by Navi over 12 years ago
How many times are we gonna move this to a next version?
Updated by Alexander Opitz almost 10 years ago
- Status changed from Accepted to Needs Feedback
- Target version deleted (
4.5.12) - Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.9)?
Updated by Alexander Opitz over 9 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.