Project

General

Profile

Actions
Copy link

Bug #52181

closed

It seems as the domain record redirect handling is broken

Added by Jan-Hendrik Heuing about 11 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2013-09-23
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

http://dl.ivi-solutions.com/2013-09-23_1000.png

It used to forward to the redirect location, which is not the case:

- If the domain record is disabled, I get the "Ops..." error, as if the domain is not configured (realurl, domain records).

- If I add the domain record in a separate page folder (not part of the regular page tree), the domain is accepted in the browser, and the pages are shown. The domain is still the one which should be redirected, and it shows the homepage instead of the url given.

Actions
Copy link
 #1

Updated by Jan-Hendrik Heuing about 11 years ago

The thing is here:

function getDomainStartPage() in PageRepository.php, calling $this->where_hid_del in the sql statement to select domain records and their startpages. As that will add AND pages.doktype<200 to the query, domain records hosted in sys folders are not redirected anymore.

I can not say if this is new, or if I just have used ordinary pages for this case. Either way: It might not be a bug, but on purpose, so I just change to a regular page and it works.

If it is not on purpose, I'd vote for opening this up ;-)

JH

Actions
Copy link
 #2

Updated by Jan-Hendrik Heuing about 11 years ago

The thing is here:

function getDomainStartPage() in PageRepository.php, calling $this->where_hid_del in the sql statement to select domain records and their startpages. As that will add AND pages.doktype<200 to the query, domain records hosted in sys folders are not redirected anymore.

I can not say if this is new, or if I just have used ordinary pages for this case. Either way: It might not be a bug, but on purpose, so I just change to a regular page and it works.

If it is not on purpose, I'd vote for opening this up ;-)

JH

Actions
Copy link
 #3

Updated by Mathias Schreiber almost 10 years ago

  • Category set to Frontend
  • Target version set to 7.2 (Frontend)
Actions
Copy link
 #4

Updated by Benni Mack over 9 years ago

  • Target version changed from 7.2 (Frontend) to 7.4 (Backend)
Actions
Copy link
 #5

Updated by Susanne Moog over 9 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions
Copy link
 #6

Updated by Benni Mack about 9 years ago

  • Target version changed from 7.5 to 7 LTS
Actions
Copy link
 #7

Updated by Mathias Schreiber about 9 years ago

  • Target version deleted (7 LTS)
Actions
Copy link
 #8

Updated by Benni Mack about 6 years ago

  • Status changed from New to Needs Feedback

Hey,

this issue should be fixed with 9 LTS and site handling. Please let us know if the new version will solve your issue, otherwise we'll close this ticket in the next weeks.

Benni.

Actions
Copy link
 #9

Updated by Oliver Hader about 6 years ago

  • Assignee deleted (Oliver Hader)
Actions
Copy link
 #10

Updated by Riccardo De Contardi almost 6 years ago

  • Status changed from Needs Feedback to Closed

No feedback since the last 90 days => closing this issue.

If you think that this is the wrong decision or experience the issue again and have more information about how to reproduce your problem, please reopen it or open a new issue with a reference to this one.

Thank you and best regards

Actions
Copy link

Also available in: Atom PDF