Project

General

Profile

Actions

Feature #62089

closed

error message: Wrong symbolic link to index.php.

Added by Franz Holzinger over 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
-
Target version:
Start date:
2014-10-07
Due date:
% Done:

100%

Estimated time:
PHP Version:
5.5
Tags:
Complexity:
Sprint Focus:

Description

TYPO3 gives a wrong error message in the Front End if you make an error in the link of index.php.

Wrong link:

index.php -> typo3/index.php

instead of correct

index.php -> typo3_src/index.php

(see #62074)
Write a better error message:
Wrong symbolic link to index.php.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #62074: Calculated absolute path to tslib directory does not exist.Closed2014-10-07

Actions
Actions #1

Updated by Markus Klein over 9 years ago

Background info

The typo3/index.php calls typo3/init.php which calls the bootstrap->baseSetup with parameter 'typo3/' as relative path.
This leads to the problem that getPathSiteByRelativePathPart() calculates the wrong path for the site as it removes the relative path from the current script path.

A possible way to check if the path is valid, would be to check in definePaths() whether PATH_site . 'index.php' does exist.

Actions #2

Updated by Gerrit Code Review over 9 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/33197

Actions #3

Updated by Markus Klein over 9 years ago

One more note: The Install Tool already detects if the index.php is a wrong symlink, but that does not help with the initial installation, if you access it with the website url only.

Example for an initial setup:

# ll
FIRST_INSTALL
index.php -> typo3/index.php
typo3 -> typo3_src/typo3
typo3_src -> ../typo3_23423

If the user now accesses http://example.com/ an error will appear as the bootstrap is triggered, which fails and therefore does not redirect to the Install Tool where this misconfiguration would have been reported.
If the users accesses http://example.com/typo3/install/ the Install Tool will come up and show the misconfiguration.
So we only need to handle the first case here.

Actions #4

Updated by Gerrit Code Review over 9 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/33197

Actions #5

Updated by Gerrit Code Review over 9 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/33197

Actions #6

Updated by Gerrit Code Review over 9 years ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/33197

Actions #7

Updated by Gerrit Code Review over 9 years ago

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/33197

Actions #8

Updated by Gerrit Code Review over 9 years ago

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/33197

Actions #9

Updated by Markus Klein over 9 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #10

Updated by Gerrit Code Review over 9 years ago

  • Status changed from Resolved to Under Review

Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/34339

Actions #11

Updated by Gerrit Code Review over 9 years ago

Patch set 2 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/34339

Actions #12

Updated by Markus Klein over 9 years ago

  • Status changed from Under Review to Resolved
Actions #13

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF