TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692018-12-13T15:08:23ZTYPO3 Forge
Redmine TYPO3 Core - Bug #87149 (Closed): Cannot debug Generator outputhttp://forge.typo3.org/issues/871492018-12-13T15:08:23ZMathias Brodalambrodala@pagemachine.de
<p>If <code>DebuggerUtility::var_dump()</code> is used on a <code>\Generator</code>, an error occurs:</p>
<blockquote>
<p>Cannot rewind a generator that was already run</p>
</blockquote>
<p>This is due to the implicit <code>rewind()</code> call within <code>DebuggerUtility::renderCollection()</code> which should be avoided for generators.</p> TYPO3 Core - Bug #85988 (Closed): @cli annotation deprecated without replacementhttp://forge.typo3.org/issues/859882018-08-27T11:10:51ZMathias Brodalambrodala@pagemachine.de
<p>With <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Deprecate @cli annotation (Closed)" href="http://forge.typo3.org/issues/85977">#85977</a> the <code>@cli</code> annotation has been deprecated without replacement but hinting at a successor in TYPO3v10. No matter if and when this will really happen we cannot do a deprecation without a replacement so this change needs to be reverted.</p> TYPO3 Core - Bug #84580 (Closed): "Stop page tree" icon/label unclearhttp://forge.typo3.org/issues/845802018-04-03T12:24:52ZMathias Brodalambrodala@pagemachine.de
<p>The option <strong>Stop page tree</strong> which can be enabled for any page has an unclear icon/label.</p>
<p>The icon is a very simple red "+" and the label only reads <strong>Stop page tree</strong>. There is no clear indication that this option prevents the page tree to render the subtree of the page where this option was enabled.</p>
<p>A better icon/label/indication could be added here.</p> TYPO3 Core - Bug #84465 (Closed): "Status report" broken because of invalid routehttp://forge.typo3.org/issues/844652018-03-18T10:52:13ZMathias Brodalambrodala@pagemachine.de
<p>The <strong>Status report</strong> within the <strong>Reports</strong> module throws an exception due to an invalid route identifier:</p>
<blockquote>
<p>#1476050190: Unable to generate a URL for the named route "system_ReportsTxreportsm1" because this route was not found.</p>
</blockquote> TYPO3 Core - Bug #83260 (Closed): Cannot set "class" for file upload elementhttp://forge.typo3.org/issues/832602017-12-08T14:26:31ZMathias Brodalambrodala@pagemachine.de
<p>HTML classes set via <code>elementClassAttribute</code> for the <code>FileUpload</code> element are not respected.</p> TYPO3 Core - Bug #82518 (Closed): Broken composite form element check in RenderAllFormValuesViewH...http://forge.typo3.org/issues/825182017-09-20T13:51:32ZMathias Brodalambrodala@pagemachine.de
<p>The check for composite form elements in the <code>RenderAllFormValuesViewHelper</code> is broken:</p>
<pre>
if (
!$element instanceof FormElementInterface
|| $element->getType() === 'Honeypot'
|| (
isset($renderingOptions['_isCompositeFormElement'])
&& $renderingOptions['_isCompositeFormElement'] = true
)
) {
continue;
}
</pre>
<p>This was implicitly fixed for master in <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: EXT:form - do not show hidden field on confirmation page (Closed)" href="http://forge.typo3.org/issues/81770">#81770</a>.</p> TYPO3 Core - Bug #73035 (Closed): Broken path for GlobalDebugFunctions autoload in core extensionhttp://forge.typo3.org/issues/730352016-01-30T17:42:20ZMathias Brodalambrodala@pagemachine.de
<p>The <code>core</code> extension specifies a wrong path in its <code>composer.json</code> for autoloading the <code>GlobalDebugFunctions.php</code> file:</p>
<pre>
"files": ["typo3/sysext/core/Resources/PHP/GlobalDebugFunctions.php"]
</pre>
<p>This should be fixed for the case this extension is required separately via Composer in the future.</p> TYPO3 Core - Bug #72548 (Closed): Cannot install: phpwhois/idna-convert cannot be downloadedhttp://forge.typo3.org/issues/725482016-01-06T10:01:16ZMathias Brodalambrodala@pagemachine.de
<p>The Github repository of the package <a href="https://packagist.org/packages/phpwhois/idna-convert" class="external">phpwhois/idna-convert</a> is somehow gone which makes every Composer installation of TYPO3 fail:</p>
<pre>
- Installing phpwhois/idna-convert (v0.8.2)
Downloading
Failed to download phpwhois/idna-convert from dist: The "https://api.github.com/repos/phpWhois/idna-convert/zipball/ea337954b43ae47f5ebba97c19d309081bebc46e" file could not be downloaded (HTTP/1.1 404 Not Found)
Now trying to download from source
- Installing phpwhois/idna-convert (v0.8.2)
Cloning ea337954b43ae47f5ebba97c19d309081bebc46e
[RuntimeException]
Failed to clone git@github.com:phpWhois/idna-convert.git via git, https, ssh protocols, aborting.
- git://github.com/phpWhois/idna-convert.git
Cloning into '/.../vendor/phpwhois/idna-convert'...
fatal: remote error:
Repository not found.
- https://github.com/phpWhois/idna-convert.git
Cloning into '/.../vendor/phpwhois/idna-convert'...
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/phpWhois/idna-convert.git/'
- git@github.com:phpWhois/idna-convert.git
Cloning into '/.../vendor/phpwhois/idna-convert'...
Warning: Permanently added 'github.com,192.30.252.129' (RSA) to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
</pre>
<p>I am currently investigating the options since the whole issue is a mess.</p> TYPO3 Core - Bug #67838 (Closed): Cannot instantiate HttpRequesthttp://forge.typo3.org/issues/678382015-06-30T10:24:48ZMathias Brodalambrodala@pagemachine.de
<p>In the 7.x release line the <code>HttpRequest</code> class cannot be instantiated due to an upstream issue.</p>
<p>This should be fixed by bumping the dependency to a version which has a fix.</p> TYPO3 Core - Bug #67047 (Closed): Cannot access shortcut target in menushttp://forge.typo3.org/issues/670472015-05-20T12:18:54ZMathias Brodalambrodala@pagemachine.de
<p>With <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Invalid shortcut target on translated pages (Closed)" href="http://forge.typo3.org/issues/36822">#36822</a> links via overlaid shortcuts have been fixed but the original menu item data was kept unchanged.</p>
<p>This makes it impossible to e.g. mark active menu items with pure TypoScript. An <code>override</code> is not useful since both <code>CONTENT</code> as well as <code>RECORDS</code> perform overlays too.</p> TYPO3 Core - Bug #66473 (Closed): Cannot create object implementing Serializable on PHP 5.6http://forge.typo3.org/issues/664732015-04-17T18:05:51ZMathias Brodalambrodala@pagemachine.de
<p>Starting with PHP 5.6 classes implementing the <code>Serializable</code> interface are represented as <code>C</code> instead of <code>O</code> in the serialized output.</p>
<p>The <code>Container::getEmptyObject</code> method which creates objects with the unserialize hack to avoid calling the constructor thus yields an error like this:</p>
<blockquote>
<p>Warning: Erroneous data format for unserializing 'Foo' in ...<br />Notice: unserialize(): Error at offset 13 of 15 bytes in ...</p>
</blockquote>
<p>Starting with PHP 5.4 this usecase can be dealt with by <a href="http://php.net/manual/en/reflectionclass.newinstancewithoutconstructor.php" class="external"><code>ReflectionClass::newInstanceWithoutConstructor</code></a></p>
<p>This also needs to fixed for TYPO3 6.2 though which supports PHP 5.3, in which case checking for the <code>Serializable</code> interface and using <code>C</code> instead of <code>O</code> could work.</p> TYPO3 Core - Bug #66350 (Closed): 6.2 static template outdatedhttp://forge.typo3.org/issues/663502015-04-10T10:59:27ZMathias Brodalambrodala@pagemachine.de
<p>The <code>v6.2</code> static template of <code>css_styled_content</code> in the current master is not up to date with changes from the 6.2 branch, namely the title attribute rendering of File Links (see <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Title not used for Filelinks (Closed)" href="http://forge.typo3.org/issues/60429">#60429</a>) and a small style differnce.</p>
<p>This should be updated to ensure exactly the same rendering when using 7.x with the <code>v6.2</code> static template as it is in 6.2 with the latest static template.</p> TYPO3 Core - Bug #66347 (Closed): Alternative text used as link title in File Linkshttp://forge.typo3.org/issues/663472015-04-10T10:40:46ZMathias Brodalambrodala@pagemachine.de
<p>If an alternative text was specified for a file, it is used as link title for file, preview and icon in File Links.</p>
<p>This should be fixed to use the title instead.</p> TYPO3 Core - Bug #65345 (Closed): Cannot set select multiple conditionallyhttp://forge.typo3.org/issues/653452015-02-25T18:20:25ZMathias Brodalambrodala@pagemachine.de
<p>Currently one cannot set the <code>multiple</code> attribute of the SelectViewHelper conditionally like this:</p>
<pre>
<f:form.select property="foo" options="{options}" multiple="{multiple}"/>
</pre>
<p>As soon as the <code>multiple</code> attribute is used, it is rendered in any case with whatever value was passed. (Thus if you pass <code>true</code> as suggested currently, you get an invalid <code>multiple="true"</code>.</p>
<p>This should be fixed by converting <code>multiple</code> into a boolean argument.</p> TYPO3 Core - Bug #61529 (Closed): Cannot ensure checkbox for multiple valueshttp://forge.typo3.org/issues/615292014-09-11T12:10:41ZMathias Brodalambrodala@pagemachine.de
<p>In TYPO3.Fluid the <code><f:form.checkbox/></code> viewhelper has a <code>multiple</code> attribute to enforce field value processing as array. This is not possible with the CMS Fluid and only marked as <code>@todo</code>.</p>
<p>This should be fixed by adding the attribute and respecting it the same way as TYPO3.Fluid.</p>