Project

General

Profile

Actions

Bug #24371

closed

TS parser blocks on parenthesis syntax if no carriage return is put

Added by Alban Cousinie almost 14 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-12-20
Due date:
% Done:

0%

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

Description

When entering a long value using typoscript, the parenthesis syntax is usefull for multiline values :
allowTags (
a, abbr, acronym, address, b, bdo, big, blockquote, br, caption, center, cite, code, col, colgroup, del, dfn, div, em,
h2, h3, h4, h5, h6, hr, i, img, ins, kbd, label, li, link, meta, ol, p, pre, q, samp, sdfield, small,
span, strike, strong, style, sub, sup, table, thead, tbody, tfoot, td, th, tr, title, tt, u, ul, var
)

However there are times where you may keep the same syntax, but for some reason you change your value to a shorter value
denyTags(
h1, font
)

Then if you are a methodical programmer, you could want to compact your code as :
denyTags( h1, font )

This parenthesis / brace rearangement would work with any language parser. But with TS it doesn't. Not only will it not evaluate the value, but also this will prevent the parser to evaluate ANY TS CODE following the line with this syntax.

This looks trivial, but this is the kind of bug one wouldn't expect. In my case it took me 2 days to figure out why my TS code did no longer work.
So a fix could be nice.

Regards

(issue imported from #M16787)

Actions #1

Updated by Alexander Opitz almost 11 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions #2

Updated by Alexander Opitz over 10 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF