Project

General

Profile

Actions

Bug #78148

closed

form.select ViewHelper only likes alphanumeric chars

Added by Dominik Hahn over 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Fluid
Target version:
-
Start date:
2016-10-05
Due date:
% Done:

0%

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

Description

Hey guys,

I have stumbled upon a rather strange problem with the form.select ViewHelper in TYPO3 CMS 7.6.11 and PHP 5.6.19

I am using the ViewHelper on an array {sites} which looks like this:

   0 => ArrayObject
      label => 'Test Test123'
      expanded => 'Test123, Test'
      value => '73'
   1 => ArrayObject
      label => 'TestBla - TestTestTest'
      expanded => 'TestTestTest, TestBla'
      value => '43'

<f:form.select property="sites" options="{sites}" prependOptionValue="" prependOptionLabel="{f:translate(key: 'label.any')}" optionLabelField="label" optionValueField="value" sortByOptionLabel="1" multiple="1" size="5" />

The generated HTML looks like this:

  <select size="5" multiple="multiple" name="tx_extension[query][sites][]">
    <option value="">any</option>
    <option value="73">Test Test123</option>
    <option value="43">TestBla - TestTestTest</option>
  </select>

The exact same thing runs on a second server, but this time with PHP 5.6.24.
I would have expected the same output but I get an Internal Server Error instead. The TYPO3 log is empty, the PHP error log is empty…

The only way I can get it to work is by stripping almost everything from the "label" leaving just the alphanumeric chars.

This array works on both versions of PHP:

   0 => ArrayObject
      label => 'TestTest123'
      expanded => 'Test123, Test'
      value => '73'
   1 => ArrayObject
      label => 'TestBlaTestTestTest'
      expanded => 'TestTestTest, TestBla'
      value => '43'

… as soon as the label includes a dot, a space or even a Sonderzeichen I get the Internal Server Error.

If you need any more information just ask.

Actions #1

Updated by Claus Due over 7 years ago

You are sure there is no log output whatsoever, including possible segmentation fault messages in system log? Did you fully enable error reporting and set Development context for your TYPO3 site?

I ask because I definitely would expect to see at least some logging happening. Even segmentation faults (which prevent php itself from logging) should be logged to your system! An error message would help greatly.

Actions #2

Updated by Wouter Wolters over 7 years ago

  • Status changed from New to Needs Feedback
Actions #3

Updated by Riccardo De Contardi about 7 years ago

  • Status changed from Needs Feedback to Closed

No feedback since 90+ days > Closing.

If you think that this is the wrong decision, experience the issue again or have more information about it, then please reopen it or open a new issue with a reference to this one.

Thank you.

Actions

Also available in: Atom PDF