TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-12-07T09:29:03ZTYPO3 Forge
Redmine TYPO3 Core - Task #96267 (New): Add dedicated error for class construction without dependencieshttp://forge.typo3.org/issues/962672021-12-07T09:29:03ZMathias Brodalambrodala@pagemachine.de
<p>Right now if <code>GeneralUtility::makeInstance()</code> is used to construct a class which uses constructor dependency injection and has not being marked as <code>public</code>, a low-level <code>\ArgumentCountError</code> is thrown by PHP.</p>
<p>This should be improved by catching this case and replacing the error with a custom one (e.g. <code>MissingDependenciesError</code>). Either that custom error already hints at possible solutions or its dedicated error code is used to link to the docs with more details. The docs could then suggest to mark the class as <code>public</code> or manually pass the dependencies as arguments.</p> TYPO3 Core - Bug #94815 (Closed): Cannot link to pages with doktype > 200http://forge.typo3.org/issues/948152021-08-11T13:16:54ZMathias Brodalambrodala@pagemachine.de
<p>Pages with <code>doktype</code> > 200 will be muted in the page tree, just as Sysfolders. Thus you cannot set links to pages with <code>doktype</code> > 200 or content elements on these pages.</p> TYPO3 Core - Bug #94814 (Closed): Cannot use page with doktype > 200 as shortcut targethttp://forge.typo3.org/issues/948142021-08-11T13:16:20ZMathias Brodalambrodala@pagemachine.de
<p>A shortcut to a page with a <code>doktype</code> > 200 does not work in Shortcut Mode <strong>First subpage of selected/current page</strong>.</p>
<p>Subpages of the current page with a @doktypeq > 200 will not be considered and thus not called in the frontend, even if they clearly are the first subpage of the shortcut.</p> 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 #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 - Bug #87035 (Closed): AdditionalFactoryConfiguration.php not used anymorehttp://forge.typo3.org/issues/870352018-11-29T10:32:53ZMathias Brodalambrodala@pagemachine.de
<p>The <code>typo3conf/AdditionalFactoryConfiguration.php</code> file can be used to provide additional default values to be put into <code>typo3conf/LocalConfiguration.php</code> upon TYPO3 setup.</p>
<p>However, this file is not used anymore since TYPO3v9 and currently must be placed one level above instead, so basically next to <code>index.php</code>.</p>
<p>This is a regression introduced with <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Replace further path usages with Environment API (Closed)" href="http://forge.typo3.org/issues/85560">#85560</a>.</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 - 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 #84491 (Closed): Breaks field in EXT:styleguidehttp://forge.typo3.org/issues/844912018-03-20T09:21:36ZMathias Brodalambrodala@pagemachine.de
<p>EXT:styleguide, elements basic > text_17 breaks with</p>
<blockquote>
<p>Argument 2 passed to TYPO3\CMS\Backend\Controller\Wizard\TableController::configurationStringToArray() must be of the type integer, null given, called in /.../typo3/sysext/backend/Classes/Controller/Wizard/TableController.php on line 496</p>
</blockquote> 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 - 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 #81524 (Closed): Cannot send mails with special characters in local parthttp://forge.typo3.org/issues/815242017-06-09T12:47:40ZMathias Brodalambrodala@pagemachine.de
<p>Currently it is impossible to send mails with special characters in their local part, e.g. <code>john.lötzsch@example.org</code>. Swiftmailer fails with the following error:</p>
<pre>
[ Swift_RfcComplianceException ]
Address in mailbox given [john.lötzsch@example.org] does not comply with RFC 2822, 3.6.2.
thrown in file er/lib/classes/Swift/Mime/Headers/MailboxHeader.php
in line 345
</pre>
<p>The mentioned <a href="https://tools.ietf.org/html/rfc2822" class="external">RFC 2822</a> has been extended by <a href="https://tools.ietf.org/html/rfc5335" class="external">RFC 5335</a> which is <a href="https://github.com/swiftmailer/swiftmailer/commit/e7cf4bd807b44be83d8922b3a1abe4d11a3fb15a" class="external">supported by Swiftmailer 6.x and newer</a>, thus an upgrade is necessary. This implies a few <a href="https://github.com/swiftmailer/swiftmailer/blob/v6.0.0/CHANGES#L4" class="external">breaking changes</a> however.</p> TYPO3 Core - Task #71521 (Closed): Clean up ObjectManager injection in CommandControllerhttp://forge.typo3.org/issues/715212015-11-12T15:55:23ZMathias Brodalambrodala@pagemachine.de
<p>The <code>ObjectManager</code> injection method in the Extbase <code>CommandController</code> is misused to initialize a lot of objects. This should be cleaned up.</p> TYPO3 Core - Bug #60338 (Closed): Changing view format does not affect partial formathttp://forge.typo3.org/issues/603382014-07-15T15:35:24ZMathias Brodalambrodala@pagemachine.de
<p>When using one view object to render a template in different formats (e.g. email in text and HTML), the template respects the requested format. However, partials are always rendered in the first rendered format. Example:</p>
<p><strong>Content of templates/partials</strong>:</p>
<p>Content of <code>Foo.txt</code>:<br /><pre>
Hello
<f:render partial="Bar"/>
</pre></p>
<p>Content of <code>Partials/Bar.txt</code>:<br /><pre>
World
</pre></p>
<p>Content of <code>Foo.html</code>:<br /><pre>
<p>Text</p>
<f:render partial="Bar"/>
</pre></p>
<p>Content of <code>Partials/Bar.html</code>:<br /><pre>
<p>World</p>
</pre></p>
<p><strong>1st invocation</strong>:</p>
<pre>
// Let $view be an instance of \TYPO3\CMS\Fluid\View\TemplateView
$view->setFormat('txt');
$view->render('Foo');
</pre>
<p>Result:<br /><pre>
Hello
World
</pre></p>
<p><strong>2nd invocation</strong>:</p>
<pre>
// $view is the same instance as above
$view->setFormat('html');
$view->render('Foo');
</pre>
<p>Result:<br /><pre>
<p>Hello</p>
World
</pre></p>
<p>As you can see, the 2nd output was rendered using the txt-Partial.</p>
<p>This is due to the local partial identifier cache in <code>AbstractTemplateView</code> which only considers the partial name, not the current request format. If that one is incorporated, separate cache entries for each partial formats are created.</p>