Project

General

Profile

Actions
Copy link

Bug #87786

closed

Scheduler runs fail if TYPO3 installed via modular composer

Added by Martin Basgier over 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
scheduler
Target version:
-
Start date:
2019-02-26
Due date:
% Done:

0%

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

Description

Hi,

I noticed the following. All scheduler runs broke, when I switched the install base for a TYPO3 8.x project from composer

"require": {
        "typo3/cms": "^8.7",
                (...)

to the new modular structure:

"require": {
        "typo3/cms-about": "^8.7",
        "typo3/cms-belog": "^8.7",
        "typo3/cms-beuser": "^8.7",
        "typo3/cms-context-help": "^8.7",
        "typo3/cms-documentation": "^8.7",
        "typo3/cms-felogin": "^8.7",
        "typo3/cms-fluid-styled-content": "^8.7",
        "typo3/cms-form": "^8.7",
        "typo3/cms-func": "^8.7",
        "typo3/cms-impexp": "^8.7",
        "typo3/cms-info": "^8.7",
        "typo3/cms-info-pagetsconfig": "^8.7",
        "typo3/cms-rte-ckeditor": "^8.7",
        "typo3/cms-setup": "^8.7",
        "typo3/cms-sys-note": "^8.7",
        "typo3/cms-t3editor": "^8.7",
        "typo3/cms-tstemplate": "^8.7",
        "typo3/cms-viewpage": "^8.7",
        "typo3/cms-wizard-crpages": "^8.7",
        "typo3/cms-wizard-sortpages": "^8.7",
                (...)

Doing some investigation why the sudden breaking of all scheduler runs happened, reveals that it seems to be connected with the symbolic links being set using the typo3/cms package. When the scheduler is run, it looks for the autoload.php it does not find it, as it uses relative paths and wants to use the symlink route (which is shorter).
The difference in the installation was confirmed here: https://stackoverflow.com/a/51791055

The difference in the project setup would be fine, but the breaking schedulers caused by it, seem like a serious bug. Please check it out.

Actions
Copy link
 #1

Updated by Michael Stucki over 5 years ago

  • Project changed from 9 to TYPO3 Core
  • Category deleted (Development)
  • TYPO3 Version set to 9

Wrong project.

Actions
Copy link
 #2

Updated by Michael Stucki over 5 years ago

  • TYPO3 Version changed from 9 to 8
Actions
Copy link
 #3

Updated by Mathias Brodala over 5 years ago

  • Status changed from New to Needs Feedback

Actually TYPO3 does not use any symlinks at all by default. Please make sure you have really removed the typo3/cms package.

Actions
Copy link
 #4

Updated by Martin Basgier over 5 years ago

Mathias Brodala wrote:

Actually TYPO3 does not use any symlinks at all by default. Please make sure you have really removed the typo3/cms package.

I also started a fresh project using the typo3/cms-* packages and can confirm that the simlinks where not created, but scheduler runs where broken then.

As described:
When using typo3/cms package
From your webroot...

index.php (symlinks to ../vendor/typo3/cms/index.php)
typo3 (symlinks to ../vendor/typo3/cms/typo3/)
When using typo3/cms-* packages
From your webroot...

index.php (not a symlink)
typo3 (not a symlink)

Actions
Copy link
 #5

Updated by Helmut Hummel over 5 years ago

When using TYPO3 in composer mode, the TYPO3 binary must be called using the composer installed binary, which works regardless whether typo3/cms or individual packages are used.

To make this clear, it would be helpful to show the correct path in scheduler module and maybe also remove the cli entry script

Actions
Copy link
 #6

Updated by Susanne Moog over 5 years ago

  • Category set to scheduler
Actions
Copy link
 #7

Updated by Benni Mack over 4 years ago

  • Status changed from Needs Feedback to Closed

Closin this issue as helmut already explained the reasoning, and we didn't get any more feedback. If you feel different - let me know, so I can re-open the issue.

Actions
Copy link

Also available in: Atom PDF