Project

General

Profile

Actions

Bug #70546

closed

Suggest wizard not working for pages with long titles

Added by Thomas Schlumberger over 8 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Category:
Backend API
Target version:
Start date:
2015-10-09
Due date:
% Done:

100%

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

Description

The suggest wizard does not work for records with to long strings.
The label used for the suggest list is created of the records label defined in the TCA ($GLOBALS['TCA'][$table]['ctrl']['label']).

In the TYPO3\CMS\Backend\Form\Wizard\SuggestWizardDefaultReceiver in the queryTable() function the label is being used to create the array for JS to use.
The label is being taken from TYPO3\CMS\Backend\Utility\BackendUtility::getRecordTitle(). This function crops the title if exceeding a specific length and adds a span around the cropped title.

This causes the output to break and the record not being saved when selected


Files

patch.diff (3.88 KB) patch.diff Thomas Schlumberger, 2015-10-09 17:11

Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #69211: Suggest wizard freaks out on long / truncated resultsClosedBenjamin Kott2015-08-20

Actions
Actions #1

Updated by Thomas Schlumberger over 8 years ago

Here is a possible solution, that does not break anything else.
A new parameter is added to TYPO3\CMS\Backend\Utility\BackendUtility::getRecordTitle() and TYPO3\CMS\Backend\Utility\BackendUtility::getRecordTitlePrep().

Actions #2

Updated by Thomas Schlumberger over 8 years ago

  • Assignee changed from Thomas Schlumberger to Benni Mack
Actions #3

Updated by Mathias Schreiber over 8 years ago

  • Assignee changed from Benni Mack to Benjamin Kott
  • Sprint Focus set to Stabilization Sprint
Actions #4

Updated by Christian Kuhn over 8 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

I'm pretty sure this is a duplicate of #69211 and was just resolved with the patch merged for that.

Actions #5

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF