Project

General

Profile

Actions

Bug #52834

closed

INCLUDE_TYPOSCRIPT on save does not write if destination-file does not exist

Added by Stefan Neufeind about 11 years ago. Updated almost 10 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
TypoScript
Target version:
-
Start date:
2013-10-15
Due date:
% Done:

0%

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

Description

There is also an issue on save when there is a BEGIN/END-comment for an INCLUDE_TYPOSCRIPT but the destination-file does not exist. However there is no real reason for that.

Being able to use it like this would allow adding BEGIN/END-comments "by hand" into an existing TypoScript and by that way splitting TypoScript into separate files.

Relevant from 4.5 onward.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #52833: TS parse: saving a non-accessible results in JS errorClosed2013-10-15

Actions
Actions #1

Updated by Stefan Neufeind about 11 years ago

Currently it throws an error that the destination-file does not exist.

Actions #2

Updated by Gerrit Code Review about 11 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/24784

Actions #3

Updated by Gerrit Code Review about 11 years ago

Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/24784

Actions #4

Updated by Gerrit Code Review about 11 years ago

Patch set 3 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/24784

Actions #5

Updated by Christian Kuhn almost 10 years ago

  • Status changed from Under Review to Rejected

Rejected, this one will not make it. TS files should not be created by INCLUDE_TYPOSCRIPT statement on the fly.

Actions

Also available in: Atom PDF