TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692019-07-19T14:15:54ZTYPO3 Forge
Redmine TYPO3 Core - Feature #88805 (Closed): Add type to TYPO3\CMS\Core\Database\Query\QueryBuilder::sethttp://forge.typo3.org/issues/888052019-07-19T14:15:54ZManuel Selbachmanuel_selbach@yahoo.de
<p>It turned out, that the method <strong><code>TYPO3\CMS\Core\Database\Query\QueryBuilder::set</code></strong> does not allow to define the type if it is forced to use <strong><code>createNamedParameter</code></strong>.</p> TYPO3 Core - Bug #87938 (Closed): Avoid superfluous cast and creation of instances DocumentTypeEx...http://forge.typo3.org/issues/879382019-03-16T22:12:38ZManuel Selbachmanuel_selbach@yahoo.de
<p>It turned out, that the implementation uses multiple cast to integer and multiple instances of DocumentTypeExclusionRestriction are created.</p> TYPO3 Core - Bug #87658 (Rejected): Admin panel simulate date / time broken under some circumstanceshttp://forge.typo3.org/issues/876582019-02-05T16:59:58ZManuel Selbachmanuel_selbach@yahoo.de
<p>The feature to simulate a date / time with the admin panel is broken under some circumstances.</p>
<p>This happens, as the "hidden" and the field that only "displays" the date / time have the same name but for the "display" field appended with "_hr".<br />You end up with:</p>
<p>hidden field name:<br /><pre>
TSFE_ADMIN_PANEL[preview_simulateDate]
</pre></p>
<p>field name that just displays the date / time<br /><pre>
TSFE_ADMIN_PANEL[preview_simulateDate]_hr
</pre></p>
<p>In some environments (combination of webserver, security modules, reverse proxy for caching, etc.) those parameters are combined in the request or modified in a way, that the value of "TSFE_ADMIN_PANEL[preview_simulateDate]" is the value from the "display field", which leads to be broken system in the frontend. As those settings are stored in the backend user profile in the database, the only way to fix is to reset the user settings, otherwise the frontend will be broken with the logged in user in the backend.</p> TYPO3 Core - Bug #85912 (Closed): Button "Paste after this record" or "Paste into this column" is...http://forge.typo3.org/issues/859122018-08-20T18:57:24ZManuel Selbachmanuel_selbach@yahoo.de
<p>If a content element get's copied and tried to insert directly via the buttons defined in the subject, nothing happens.</p>
<p>How to reproduce:</p>
<p>- Open a page in the page module with some content on it<br />- Copy a content element<br />- try to paste it via the button "Paste after this record" or "Paste into this column"</p>
<p>Result:<br />- Nothing happens</p>
<p>This issue seems to be located in the DragDrop.js or in Paste.js</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 #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 - Bug #76513 (Rejected): diff-view not working for categories if default changeshttp://forge.typo3.org/issues/765132016-06-08T09:10:41ZManuel Selbachmanuel_selbach@yahoo.de
<p>Hi,</p>
<p>the diff-view of a translated record shows "N/A" if there are changes made to the default language.</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 #69038 (Closed): Move record-related entrypoints to backend routinghttp://forge.typo3.org/issues/690382015-08-14T08:18:01ZManuel Selbachmanuel_selbach@yahoo.deTYPO3 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 - Bug #68880 (Closed): Save, save & view, save & close not working in RTE Wizardhttp://forge.typo3.org/issues/688802015-08-09T11:04:46ZManuel Selbachmanuel_selbach@yahoo.de
<p>The button Save, save & view and save & close donĀ“t work in the RTE wizard (Fullscreen Rich Text Editing).</p>
<p>JavaScript error appears:<br /><pre>
Uncaught TypeError: document.getElementsByName(...).submit is not a function
</pre></p>
<pre>
submitForm: function() {
if (TBE_EDITOR.doSaveFieldName) {
document[TBE_EDITOR.formname][TBE_EDITOR.doSaveFieldName].value=1;
}
// Set a short timeout to allow other JS processes to complete, in particular those from
// EXT:backend/Resources/Public/JavaScript/FormEngine.js (reference: http://forge.typo3.org/issues/58755).
// TODO: This should be solved in a better way when this script is refactored.
window.setTimeout(function() {
document.getElementsByName(TBE_EDITOR.formname).submit(); <----------------- here the error appears
}, 10);
},
</pre> TYPO3 Core - Bug #68860 (Closed): SelectImage Eventlistener throws execptionhttp://forge.typo3.org/issues/688602015-08-08T16:02:21ZManuel Selbachmanuel_selbach@yahoo.deTYPO3 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 #68756 (Closed): Add config "base" to stdWraphttp://forge.typo3.org/issues/687562015-08-05T15:04:49ZManuel Selbachmanuel_selbach@yahoo.de
<p>Follow up: <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Filelist should use IEC prefixes and appropriate units for filesize. (Closed)" href="http://forge.typo3.org/issues/22175">#22175</a></p>
<p>The following function was updated and added with a new optional parameter $base:<br />TYPO3\CMS\Core\Utility\GeneralUtility::formatSize($sizeInBytes, $labels = '', $base = 0)</p>
<p>This impacts the function:<br />TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->stdWrap_bytes</p>
<p>It is not possible now, to set the base parameter via TypoScript if you add custom labels.</p>