TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-09-10T14:40:15ZTYPO3 Forge
Redmine TYPO3 Core - Bug #95181 (Needs Feedback): FlexForm – String returned for empty sections instead o...http://forge.typo3.org/issues/951812021-09-10T14:40:15ZPierrick Caillon
<p>When using the section feature of FlexForm, and empting a section, the result parsed flexform will contain an empty string instead of an empty array.<br />This behaviour existed before the introduction of FlexFormService.</p>
<p>To reproduce, a contributor must remove all elements in a flexform section and save. The flexform will then contain:<br /><pre>
<field index="my_field">
<el index="el"></el>
</field>
</pre></p>
<p>In EXT:core/Classes/Service/FlexFormService.phpL49, when discovering a node named <code>el</code>, the parser is recursively called. When <code>$nodeValue</code> is an empty string, it should return an empty array. Not doing so force developers to test again empty, which can not always be done straightforwardly. It is expected to be able to test with <code>count()</code>.</p>
<p>I attached an example flexform to test with.</p> TYPO3 Core - Bug #94714 (Closed): SvgFilesSanitization prevent subsequent file searchhttp://forge.typo3.org/issues/947142021-08-04T17:26:23ZPierrick Caillon
<p>The method <code>SvgFilesSanitization::resolveSvgFiles</code> set up a file extension filter in every resource storage. However, it does not reset the filter after use.</p>
<p>It prevents the usage of <code>FormPersistenceManager::listForms</code> to retrieve the forms to check them in some own update wizard. Or any other file searching which expect the filters to be defaulted.</p>
<p>A trivial fix would be in <a class="attachment" href="http://forge.typo3.org/attachments/36221">svgfilessanitization.patch</a>.</p>
<p>Another solution would be to update <code>FormPersistenceManager</code> to replace the filters instead of adding, in <a class="attachment" href="http://forge.typo3.org/attachments/36222">formpersistencemanager.patch</a>.</p>
<p>Or maybe do both?</p>
<p>Introduced since <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Introduce t3g/svg-sanitizer (Closed)" href="http://forge.typo3.org/issues/94492">#94492</a></p> TYPO3 Core - Bug #81806 (Closed): Unescaped value in FormEngine.removeOption selector queryhttp://forge.typo3.org/issues/818062017-07-05T16:30:05ZPierrick Caillon
<p>I have a form field whose values comes from a list of subscribed classes for some roles.</p>
<p>The flexform TCA for this form field looks like that:<br /><pre><code class="XML syntaxhl" data-language="XML"><span class="nt"><providers></span>
<span class="nt"><TCEforms></span>
<span class="nt"><label></span>LLL:EXT:my_ext/Resources/Private/Language/locallang.xlf:flexform.sheets.general.providers<span class="nt"></label></span>
<span class="nt"><config></span>
<span class="nt"><type></span>select<span class="nt"></type></span>
<span class="nt"><itemsProcFunc></span>Vendor\MyExt\Flexform\Helper-<span class="ni">&gt;</span>renderProviderList<span class="nt"></itemsProcFunc></span>
<span class="nt"><maxitems></span>100<span class="nt"></maxitems></span>
<span class="nt"><size></span>4<span class="nt"></size></span>
<span class="nt"></config></span>
<span class="nt"></TCEforms></span>
<span class="nt"></providers></span>
</code></pre></p>
<p>The computed items list looks like:<br /><pre><code class="PHP syntaxhl" data-language="PHP"><span class="p">[</span>
<span class="p">[</span> <span class="s1">'First provider'</span><span class="p">,</span> <span class="s1">'Vendor\\MyExt\\FirstProvider'</span> <span class="p">],</span>
<span class="p">[</span> <span class="s1">'Second provider'</span><span class="p">,</span> <span class="s1">'Vendor\\MyExt\\SecondProvider'</span> <span class="p">]</span>
<span class="p">]</span></code></pre></p>
<p>Manipulating the form element does not work well.</p>
<p>The issue is removing an element from the selected box is not working. After step by step debugging, it looks like the value <code class="JavaScript syntaxhl" data-language="JavaScript"><span class="nf">$</span><span class="p">(</span><span class="k">this</span><span class="p">).</span><span class="nf">attr</span><span class="p">(</span><span class="dl">'</span><span class="s1">value</span><span class="dl">'</span><span class="p">)</span></code> needs selector string escaping on line 569 of <code>EXT:backend/Resources/Public/JavaScript/FormEngine.js</code>.</p>
<p>Also affect 8 LTS. The affected code portion is the same. Only one line down.</p> TYPO3 Core - Bug #79568 (Closed): baseURL determination of EXT:rtehtmlarea fails in frontend editinghttp://forge.typo3.org/issues/795682017-01-31T11:39:49ZPierrick Caillon
<p>The htmlarea RTE fails to correctly determine the baseURI to define in the editing iframe when a slash is present unencoded in the url parameters.<br />The case happens with frontend editing. When editing an existing record. An unencoded return url is added to the edit frame parameters. In backend the URL is already properly encoded when present, for example, when searching a record with the global search box and clicking on the record.</p>
<p>Occurs with Mozilla Firefox 51. Does not occur with Google Chrome. Not Verified with Internet Explorer.</p>
Reproduction steps:
<ol>
<li>Set up frontend editing (<a class="external" href="https://wiki.typo3.org/Frontend_editing">https://wiki.typo3.org/Frontend_editing</a> and <code>Content Elements (fluid_styled_content)</code> template included for editpanel)</li>
<li>Create or choose a <code>Text & Image</code> or <code>Text & Media</code> or any other content with a Rich Text Editor</li>
<li>Put a table with default settings in the RTE, it will make the fix visible without inspection</li>
<li>Go to the page in frontend and click the edit icon of the created or chosen content</li>
<li>In the edit popup, the URL ends with <code>&returnUrl=sysext/backend/Resources/Private/Templates/Close.html</code></li>
<li>In the RTE, table borders are not visible despite activating the <code>show table borders</code> button</li>
</ol> TYPO3 Core - Task #70932 (Closed): stdWrap_bytes.base ignored in certain caseshttp://forge.typo3.org/issues/709322015-10-21T23:10:51ZPierrick Caillon
<p>Follow up: <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Add config "base" to stdWrap (Closed)" href="http://forge.typo3.org/issues/68756">#68756</a></p>
<p>The TypoScript reference update for stdWrap_bytes function should mention the base property is ignored if a keyword is used in the label property or something like that, as documented by GeneralUtility::formatSize function.</p> TYPO3 Core - Task #67606 (Closed): eval() in data handler testhttp://forge.typo3.org/issues/676062015-06-18T15:52:21ZPierrick Caillon
<p>See <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Get rid of eval() in unit tests (Closed)" href="http://forge.typo3.org/issues/67468">#67468</a><br />On EXT:core, unit test for DataHandling/DataHandler</p> TYPO3 Core - Task #67604 (Closed): eval() in mailer testhttp://forge.typo3.org/issues/676042015-06-18T15:18:45ZPierrick Caillon
<p>See <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Get rid of eval() in unit tests (Closed)" href="http://forge.typo3.org/issues/67468">#67468</a><br />On EXT:core, unit test for Mail/Mailer</p> TYPO3 Core - Task #67600 (Closed): eval() in general utility testshttp://forge.typo3.org/issues/676002015-06-18T12:59:31ZPierrick Caillon
<p>See <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Get rid of eval() in unit tests (Closed)" href="http://forge.typo3.org/issues/67468">#67468</a><br />On EXT:core, unit test for Utility/GeneralUtility</p> TYPO3 Core - Task #67596 (Closed): eval() in path utility testshttp://forge.typo3.org/issues/675962015-06-18T12:23:30ZPierrick Caillon
<p>See <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Get rid of eval() in unit tests (Closed)" href="http://forge.typo3.org/issues/67468">#67468</a><br />On EXT:core, unit test for Utility/PathUtility</p> TYPO3 Core - Task #67594 (Closed): eval() in version number utility testhttp://forge.typo3.org/issues/675942015-06-18T11:52:20ZPierrick Caillon
<p>See <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Get rid of eval() in unit tests (Closed)" href="http://forge.typo3.org/issues/67468">#67468</a><br />On EXT:core, unit test for Utility/VersionNumberUtility</p> TYPO3 Core - Task #67591 (Closed): eval() in tree data provider testhttp://forge.typo3.org/issues/675912015-06-18T11:05:22ZPierrick Caillon
<p>See <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Get rid of eval() in unit tests (Closed)" href="http://forge.typo3.org/issues/67468">#67468</a><br />On test EXT:core, unit test for Tree/TableConfiguration/TreeDataProviderFactory</p> TYPO3 Core - Task #67572 (Closed): Update calls to formatSize to adjust to new unitshttp://forge.typo3.org/issues/675722015-06-17T18:40:34ZPierrick Caillon
<p>Follow up of <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Filelist should use IEC prefixes and appropriate units for filesize. (Closed)" href="http://forge.typo3.org/issues/22175">#22175</a>.</p>
<p>The references and documentation in the following file should be updated to reflect the new feature: typo3/sysext/t3editor/res/tsref/tsref.xml</p>
<p>The label for "byteSizeUnits" should be updated in typo3/sysext/lang/locallang_common.xlf to use the IEC prefixes. (Ki Mi …)</p>
<p>The constant value and comment of constant <code>styles.content.uploads</code> should be updated typo3/sysext/css_styled_content/static/constants.txt to reflect the new feature and use "iec" as default.</p> TYPO3 Core - Bug #24515 (Closed): alt_doc.php does not keep default values given in URL.http://forge.typo3.org/issues/245152011-01-11T17:23:03ZPierrick Caillon
<p>The defVals url parameter is undefined after first saving of the record.<br />When using the "save and new" button, the behaviour I expected was to provide again these default values. However TYPO3 unsets them and they are no more available.</p>
<p>This behaviour is understandable in the case the other buttons are used. it saves little bandwith, processing and memory.</p>
<p>File typo3/alt_doc.php line 262<br /> unset($this->R_URL_getvars['defVals']);</p>
<p>(issue imported from #M16969)</p> TYPO3 Core - Feature #19419 (Closed): Content in generated page or editing is messed uphttp://forge.typo3.org/issues/194192008-10-06T10:53:07ZPierrick Caillon
<p>Even if the content is correct in the database, when the page is generated or the content edited in the backend, its rte text is messed up. An example is attached to this report.</p>
<p>Server: Debian etch<br />Php: 5.2.0-8etch11<br />(issue imported from #M9491)</p>