Project

General

Profile

Actions

Feature #14531

closed

check in Typoscript parser on copying of certain value/properties

Added by Peter Niederlag almost 20 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Category:
Backend API
Target version:
-
Start date:
2005-02-04
Due date:
% Done:

0%

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

Description

there seems to be a hirsatirical(?) ceck for Typoscript version1. Also I get this message every once in a while it never turns out to be a problem at all.

Maybe it's obsolete?

Line 1743: Object copied in this line "parseFunc < lib.parseFunc_RTE" would leave either the value or properties untouched in TypoScript Version 1. Please check that this is not a problem for you.
(issue imported from #M751)

Related issues 1 (0 open1 closed)

Has duplicate TYPO3 Core - Task #32012: A message about non-existing TypoScript errorClosedDmitry Dulepov2011-11-23

Actions
Actions #1

Updated by Mathias Schreiber over 18 years ago

TYPO3 Version too old.
The reported version is no longer maintained.

If this bug still persists in 4.0.1, please re-open it again and set the field "Product Version" to the corresponding version.

Actions #2

Updated by Peter Niederlag over 18 years ago

This "bug" is still valid for 4.0.1:

t3lib/class.t3lib_tsparser.php: if ((isset($setup[$string]) && !isset($value0)) || (isset($setup[$string.'.']) && !isset($value1))) {$this->error('Line '.($this->lineNumberOffset+$this->rawP-1).': Object copied in this line "'.trim($this->raw[($this->rawP-1)]).'" would leave either the value or properties untouched in TypoScript Version 1. Please check that this is not a problem for you.',1);}

I have never seen where it actually would have caused a problem. But before remving this annoying message it still would require some investigations I assume.

Actions #3

Updated by Michael Stucki over 18 years ago

I suppose Kasper knows about this very well. I will ask him and let you know.

Actions #4

Updated by Kasper Skårhøj about 18 years ago

Hi Guys,

If its all about removing the message, go ahead. But do not change how TYpoScript is parsed...

Actions #5

Updated by Jules Piccotti about 18 years ago

I've been able to replicate this error message with the following typoscript statement:

1 = TMENU
1 {
NO {
allWrap = pre | post
}
IFSUB =1
IFSUB < .NO
IFSUB {
allWrap = pre2 | post2
}

getting this error message in the TypoScript Object Browser:

1: Line 1762: Object copied in this line "IFSUB < .NO" would leave either the value or properties untouched in TypoScript Version 1. Please check that this is not a problem for you.

I easily fixed everything swapping two rows like this:

IFSUB < .NO
IFSUB =1

Seems I have to copy the NO object in IFSUB before setting it to true.

Omitting the line:
IFSUB =1
seems to produce strange behaviours, I will investigate it further soon

Actions #6

Updated by Thomas Noest almost 15 years ago

I had a replica of this on typo3 4.3.1. But the error message was significant, sort of. The solution reported above of swapping the two statements worked but why is it not needed everywhere?

I use this ts for the main menu:
CUR=1
NO {
....
}
CUR < .NO
This is on entrylevel 0 and it works. The Object browser gives the errormessage but also shows that the NO object is copied as expected.

Without the CUR=1 rule my CUR-markup was not applied. This seems strange to me as the 1 value is overwritten (and this is shown by the Object browser)

Now for the subpages (entrylevel 1) I make an extra menu. I used the same ts but the CUR markup was not applied. After finding Jules Picotti's Note (above) I swapped the =1 assignment with the object copy and the errormessage was gone, CUR=1 is shown in the objectbrowser(obvious) and the CUR-markup is applied.

I'm glad my menu's work, but... This behaviour seems inconsistent to me and imho could point to an error

Actions #7

Updated by Gabriel Kaufmann over 14 years ago

The error is still present in TYPO3 4.4.

Actions #8

Updated by Simon Schaufelberger about 13 years ago

The error is still present in TYPO3 4.5.

Actions #9

Updated by Alexander Opitz over 11 years ago

  • Target version deleted (0)
  • TYPO3 Version changed from 4.0 to 4.5
  • PHP Version deleted (4)
Actions #10

Updated by Tymoteusz Motylewski almost 10 years ago

  • Status changed from Accepted to Resolved
Actions #11

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF