TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692019-11-12T18:51:47ZTYPO3 Forge
Redmine 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 #88579 (Closed): Update doctrine/dbal to ^2.9http://forge.typo3.org/issues/885792019-06-18T09:44:17ZManuel Selbachmanuel_selbach@yahoo.deTYPO3 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> TYPO3 Core - Task #78578 (Closed): LiveSearch: Refactor use of queryBuilder to use prepared state...http://forge.typo3.org/issues/785782016-11-05T14:37:30ZManuel 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 the LiveSearch has to be refactored.</p> TYPO3 Core - Task #75463 (Closed): "old fashioned" icons in category treehttp://forge.typo3.org/issues/754632016-04-08T15:07:23ZManuel Selbachmanuel_selbach@yahoo.de
<p>"Old fashioned" icons are used within the category tree in the backend. <br />This is not consistent with the other icons in the backend.</p> TYPO3 Core - Task #68881 (Closed): Add backend routes for wizards (part 2)http://forge.typo3.org/issues/688812015-08-09T11:24:31ZManuel Selbachmanuel_selbach@yahoo.de
<p>Move all wizards to the Backend Routing.<br />Do not use the module registration for wizards in ext_tables.php<br />Use Configuration/Backend/Routes.php instead.</p>
<p>Instructions for testing the routings:</p>
<p>colorpicker wizard<br />------------------</p>
<p>To test colorpicker follow these steps:</p>
<p>- install introduction package<br />- create a bootstrap carousel element<br />- create a carousel item<br />- The wizard is located beside the "Text color" field<br />- Open the wizard. The route should now be visible in the location of the wizard window.</p>
<p>BackendLayout wizard<br />--------------------</p>
<p>- create a backend layout record per list view<br />- The wizard is located beside the field "Config" <br />- Open the wizard. The route should now be visible in the location of the wizard window.</p>
<p>Table wizard<br />------------<br />- create a content element of type "Table" <br />- save it<br />- go to tab "Table" <br />- The wizard is located beside the field "Text" <br />- Have a look at the href-attribute of the wizard link. The route should be visible there.</p>
<p>RTE wirzard<br />-----------<br />- create a text element and save it<br />- The wizard is located beside the RTE for field "Text" (Fullscreen Rich Text Editing)<br />- Have a look at the href-attribute of the wizard link. The route should be visible there.</p> TYPO3 Core - Task #68858 (Closed): Add backend routes for wizardshttp://forge.typo3.org/issues/688582015-08-08T15:19:16ZManuel Selbachmanuel_selbach@yahoo.de
<p>Move all wizards to the backend routing form ext_tables.php to Configuration/Backend/Routes.php</p>
<p>RTE Wizards:<br />You need the full RTE (demo mode in Extension Configuration).<br />If you have bootstrap package installed you should comment out the following line in ext_localconf.php:<br />\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPageTSConfig('<INCLUDE_TYPOSCRIPT: source="FILE:EXT:' . $_EXTKEY . '/Configuration/PageTS/RTE.txt">');</p>
<p>Otherwise the RTE configuration of the bootstrap package will overwrite everything ;)</p>
<p>OpenId:<br />Install the extension.<br />Within the backend user settings there is a new field "OpenID identifier".<br />The wizard is located beside the field.</p>
<p>compatibility6:<br />To test the form wizard you have to uninstall the form extension and to install the compatibility6 extension.<br />After that, create a form, save and go down to the config area.<br />The wizard is located beside the textarea</p> TYPO3 Core - Task #68814 (Closed): remove of base constant TYPO3_URL_ORGhttp://forge.typo3.org/issues/688142015-08-07T09:49:42ZManuel Selbachmanuel_selbach@yahoo.de
<p>Base constant TYPO3_URL_ORG defined in SystemEnvironmentBuilder::defineBaseConstants() can be removed.<br />It´s only for internal usage only and defined at 2 places in the core.</p>
<p>Use TYPO3_URL_GENERAL instead.</p>