TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692019-11-22T17:35:33ZTYPO3 Forge
Redmine TYPO3 Core - Task #89747 (Closed): Allow custom tables in record browserhttp://forge.typo3.org/issues/897472019-11-22T17:35:33ZMathias Brodalambrodala@pagemachine.deTYPO3 Core - Task #89746 (Closed): Make icon for record browser configurablehttp://forge.typo3.org/issues/897462019-11-22T17:34:51ZMathias Brodalambrodala@pagemachine.deTYPO3 Core - Task #89481 (Closed): Add security reporting procedure to READMEhttp://forge.typo3.org/issues/894812019-10-23T09:08:10ZMathias Brodalambrodala@pagemachine.de
<p>The current README does not have a single mention how security issues should be reported. This can lead to public reports which violates the <a href="https://en.wikipedia.org/wiki/Responsible_disclosure" class="external">responsible disclosure</a> principle.</p> TYPO3 Core - Task #85620 (Closed): Add hint about missing pages to Site Configuration modulehttp://forge.typo3.org/issues/856202018-07-23T14:46:00ZMathias Brodalambrodala@pagemachine.de
<p>If there are no pages, the Site <em>Configuration</em> module only shows some table headers without any hint, that first at least one page needs to be added through the <em>Page</em> module. There should be a hint similar to the <em>Redirects</em> module.</p> TYPO3 Core - Bug #85536 (Closed): Missing mail part content type in Test Mail Setuphttp://forge.typo3.org/issues/855362018-07-12T09:53:35ZMathias Brodalambrodala@pagemachine.de
<p>The <strong>Test Mail Setup</strong> in the <strong>Enviroment</strong> section of the maintenance area sends mails with a HTML body and a plain text part. However, the latter does not have a content-type which it should have for a cleaner mail structure.</p> TYPO3 Core - Bug #85415 (Closed): Missing space in inline record control buttonshttp://forge.typo3.org/issues/854152018-06-28T11:46:56ZMathias Brodalambrodala@pagemachine.de
<p>There is no space between the icon and text of inline record control buttons like <strong>Create new</strong> and <strong>Localize all records</strong>:</p>
<p><img src="http://forge.typo3.org/attachments/download/33560/inline-controls.png" alt="" loading="lazy" /></p> TYPO3 Core - Task #85358 (Rejected): Privately declare deprecated public methods/propertieshttp://forge.typo3.org/issues/853582018-06-23T10:57:48ZMathias Brodalambrodala@pagemachine.de
<p>There are two traits <code>PublicMethodDeprecationTrait</code> and <code>PublicPropertyDeprecationTrait</code>. These require defining a property map which methods/properties should be handled.</p>
<p>To ensure deprecations continue to work even in classes extending these and overwriting the property map the property map must be declared <code>private</code>:</p>
<p><a class="external" href="https://3v4l.org/Ejdue">https://3v4l.org/Ejdue</a></p> TYPO3 Core - Task #85344 (Closed): Use trait for public method access deprecationhttp://forge.typo3.org/issues/853442018-06-22T17:43:56ZMathias Brodalambrodala@pagemachine.de
<p>There are a few locations which use <code>debug_backtrace()</code> to determine whether a method was called internally or by 3rd party.</p>
<p>This should be replaced by the <code>PublicMethodDeprecationTrait</code>.</p> TYPO3 Core - Feature #85326 (Closed): Automatically add schema for TCA "descriptionColumn"http://forge.typo3.org/issues/853262018-06-21T11:27:24ZMathias Brodalambrodala@pagemachine.de
<p>The <code>DefaultTcaSchema</code> added with <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Auto create management DB fields from TCA ctrl (Closed)" href="http://forge.typo3.org/issues/85160">#85160</a> should be used for the TCA <code>descriptionColumn</code> too.</p> TYPO3 Core - Bug #85139 (Closed): Invalid arguments for method call matcherhttp://forge.typo3.org/issues/851392018-06-01T12:31:22ZMathias Brodalambrodala@pagemachine.de
<p>The changes from <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Deprecate usages of CharsetConverter in core (Closed)" href="http://forge.typo3.org/issues/85125">#85125</a> and <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Deprecate Backend Module Routing methods (Closed)" href="http://forge.typo3.org/issues/85113">#85113</a> introduced an invalid/incomplete argument configuration for the method call matcher. These should be fixed.</p> TYPO3 Core - Task #85034 (Closed): Log message when typolink failshttp://forge.typo3.org/issues/850342018-05-17T15:39:14ZMathias Brodalambrodala@pagemachine.de
<p><code>ContentObjectRenderer::typoLink()</code> catches the <code>UnableToLinkException</code> from link builders and only returns the link text. Additionally the exception details should be logged to simplify debugging.</p> TYPO3 Core - Bug #84497 (Closed): RsaEncryptionEncoder::getRsaPublicKey() must not be deprecatedhttp://forge.typo3.org/issues/844972018-03-20T12:16:24ZMathias Brodalambrodala@pagemachine.de
<p>With <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Extract request processing from RsaEncryptionEncoder (Closed)" href="http://forge.typo3.org/issues/84407">#84407</a> the <code>RsaEncryptionEncoder::getRsaPublicKey()</code> method was deprecated since it is used in the now deprecated request handling of that class.</p>
<p>However that method has value for 3rd party code too since otherwise people need to copy these lines into their code.</p>
<p>The method should not be deprecated. In fact <code>RsaPublicKeyGenerationController</code> should probably use it too to avoid code duplication.</p> TYPO3 Core - Task #84466 (Closed): Add separate HTTPS security check to reports modulehttp://forge.typo3.org/issues/844662018-03-18T11:27:03ZMathias Brodalambrodala@pagemachine.de
<p>The reports module needs to have a separate HTTPS security check independent from the suggestion added by <code>rsaauth</code> which is bound to be removed sooner or later. Using TYPO3 (or any website) without HTTPS is deemed insecure.</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 - Task #84462 (Rejected): RSA encryption hook should be moved from EXT:rsaauth to EXT:...http://forge.typo3.org/issues/844622018-03-18T10:08:32ZMathias Brodalambrodala@pagemachine.de
<p>The <code>rsaauth</code> extension currently registers a hook for the <code>felogin</code> extension for RSA encrypted login form submission.</p>
<p>This should be moved to the <code>felogin</code> extension instead.</p>