TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692020-06-17T17:35:27ZTYPO3 Forge
Redmine TYPO3 Core - Task #91667 (New): Optimization of workspace information dialoghttp://forge.typo3.org/issues/916672020-06-17T17:35:27ZManuel Selbachmanuel_selbach@yahoo.de
<p>The workspace information dialog shows some information, that could be optimized.</p>
<p>First of all there is the "t3_origuid" shown, which could be dropped IMO.</p>
<p>Furthermore there is the field "Columns" shown with one "translated" and readable column name and one with just a number which might be not that easy to be interpreted by an editor.</p>
<p>Please find both topics in the image:</p>
<p><img src="http://forge.typo3.org/attachments/download/35312/workspace-information-dialog.png" alt="" loading="lazy" /></p> TYPO3 Core - Task #89794 (Closed): Refactoring the database check in install toolhttp://forge.typo3.org/issues/897942019-11-28T17:41:31ZManuel Selbachmanuel_selbach@yahoo.de
<p>The current state of the check regarding database requirements is not separated properly.<br />Thus I suggest to refactor that to add platform and driver specific specification to have this maintainable.</p> TYPO3 Core - Task #89657 (Closed): Update doctrine/dbal requirement to minimum ^2.10http://forge.typo3.org/issues/896572019-11-12T18:51:47ZManuel Selbachmanuel_selbach@yahoo.de
<p>With the change in <a class="external" href="https://forge.typo3.org/issues/89614">https://forge.typo3.org/issues/89614</a> the new class Doctrine\DBAL\Types\Types is used to specify DBAL related types.</p>
<p>With that the minimum requirement has to be raised.</p> TYPO3 Core - Task #89593 (Closed): Update doctrine/dbal to 2.10.0http://forge.typo3.org/issues/895932019-11-06T11:52:36ZManuel Selbachmanuel_selbach@yahoo.de
<p>Due to new releases of doctrine/dbal, those package should be updated as it provides several bugfixes.</p>
<p><a class="external" href="https://github.com/doctrine/dbal/releases/tag/v2.10.0">https://github.com/doctrine/dbal/releases/tag/v2.10.0</a></p> TYPO3 Core - Task #89592 (Closed): Update doctrine/dbalhttp://forge.typo3.org/issues/895922019-11-06T11:38:07ZManuel Selbachmanuel_selbach@yahoo.de
<p>Due to new releases of doctrine/dbal, those packages should be updated.</p>
<p><a class="external" href="https://github.com/doctrine/dbal/releases/tag/v2.10.0">https://github.com/doctrine/dbal/releases/tag/v2.10.0</a></p> TYPO3 Core - Task #89424 (Closed): Update Microsoft docker images in testshttp://forge.typo3.org/issues/894242019-10-15T15:44:32ZManuel Selbachmanuel_selbach@yahoo.de
<p>As mentioned on <a class="external" href="https://hub.docker.com/r/microsoft/mssql-server-linux">https://hub.docker.com/r/microsoft/mssql-server-linux</a> the images have moved to another location and thus should updated in the local tests and bamboo docker-compose.yml files.</p> TYPO3 Core - Task #88579 (Closed): Update doctrine/dbal to ^2.9http://forge.typo3.org/issues/885792019-06-18T09:44:17ZManuel Selbachmanuel_selbach@yahoo.deTYPO3 Core - Task #88553 (Closed): Update doctrine/dbal to ^2.8.1http://forge.typo3.org/issues/885532019-06-13T09:40:58ZManuel Selbachmanuel_selbach@yahoo.deTYPO3 Core - Feature #85369 (New): Proper YAML configuration APIhttp://forge.typo3.org/issues/853692018-06-24T10:04:06ZManuel Selbachmanuel_selbach@yahoo.de
<p>In the core there should be a proper API to register, validate the definition and retrieve the parsed YAML configuration.</p>
<p>Things that should be covered:<br />- register YAML configuration files at one central place<br />- define a definition for YAML files to validate that the configuration provided is correct<br />- proper override / combining / extending of a YAML configuration by registering another file (useful if an extension extends some yaml configuration)</p> TYPO3 Core - Task #80317 (Closed): Deprecate BackendUtility::getRecordRawhttp://forge.typo3.org/issues/803172017-03-17T10:04:10ZManuel Selbachmanuel_selbach@yahoo.de
<p>Since we follow the principel of "prepared statement", the method getRecordRaw will break this behaviour.<br />Within the "where" parameter of the function it is possible to inject malicious code.</p>
<p>Thus we should remove it, as the queryBuilder should be used everywhere in the future<br /> to increase visiblity of which query will be processed at a concrete point of code and to<br /> force the concept of prepared statements.</p> TYPO3 Core - Task #79509 (Closed): Add group feature to functional testshttp://forge.typo3.org/issues/795092017-01-26T20:51:59ZManuel Selbachmanuel_selbach@yahoo.de
<p>To increase the performance of functional tests (as excluded groups would not be processed at all, not even be listed) and to ignore tests for certain DBMS the option "@group" should be used in the annotation of a test.</p>
<p>Example:</p>
<pre>
/**
* @test
*
* @group mysql
*/
public function collectGarbageWorksWithEmptyTableWithMysql()
{
$subject = $this->getSubjectObject(true);
$subject->collectGarbage();
}
</pre>
<p>To exclude a group follow the these examples:</p>
<pre>
// to exclude tests for MySQL
bin/phpunit -c ./components/testing_framework/core/Build/FunctionalTests.xml --exclude-group mysql
// to exclude tests for MySQL and PostgreSQL
bin/phpunit -c ./components/testing_framework/core/Build/FunctionalTests.xml --exclude-group mysql postgresql
</pre> TYPO3 Core - Task #79382 (Closed): Cleanup ActionService::getVersionedIdhttp://forge.typo3.org/issues/793822017-01-18T22:44:15ZManuel Selbachmanuel_selbach@yahoo.de
<p>Within the refactoring process the optional parameter $useDeleteClause was missed<br />to remove from the parameter list of the method, as it is not implemented in the body and<br />not used anywhere in the core.</p> TYPO3 Core - Task #79378 (Closed): Unused code in LocalizationController::process foundhttp://forge.typo3.org/issues/793782017-01-18T21:30:28ZManuel Selbachmanuel_selbach@yahoo.de
<p>Within the method TYPO3\CMS\Backend\Controller\Page\LocalizationController::process unused code was found.<br />Additionally the for loop should be refactored as it counts the array every loop.</p> TYPO3 Core - Task #78930 (Closed): Integrate driver into functional testshttp://forge.typo3.org/issues/789302016-12-09T10:44:48ZManuel Selbachmanuel_selbach@yahoo.de
<p>According to doctrine migration functional tests should be processed against different dbms.<br />Thus, we have to integrate the driver to the bootstrap.</p> TYPO3 Core - Task #78704 (Closed): BackendUtility: Refactor use of queryBuilder to use prepared s...http://forge.typo3.org/issues/787042016-11-15T15:09:08ZManuel Selbachmanuel_selbach@yahoo.de
<p>According to task <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Refactor use of queryBuilder to use prepared statements (Closed)" href="http://forge.typo3.org/issues/78437">#78437</a> queries should follow the prepared statement principle.<br />Thus method BackendUtiltiy::getRecordsByField() has to be refactored.</p>