TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692016-10-27T15:10:19ZTYPO3 Forge
Redmine TYPO3 Core - Task #78469 (Rejected): Acceptance Test for changing extension configurationhttp://forge.typo3.org/issues/784692016-10-27T15:10:19ZMarco Breschmarco.bresch@starfinanz.de
<p>This Test will change the backend logo</p> TYPO3 Core - Task #78453 (Closed): Acceptance test for TER search in ExtensionManagerhttp://forge.typo3.org/issues/784532016-10-26T18:32:10ZMarco Breschmarco.bresch@starfinanz.de
<p>The followup (<a class="external" href="https://review.typo3.org/#/c/50391/">https://review.typo3.org/#/c/50391/</a>) of <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> shows us the need of another acceptance test. :-)</p> TYPO3 Core - Task #78441 (Closed): Improve acceptance test for extension managerhttp://forge.typo3.org/issues/784412016-10-26T11:17:18ZMarco Breschmarco.bresch@starfinanz.de
<p>The solution in <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Acceptance Test for Extension Manger fails since #77820 (Closed)" href="http://forge.typo3.org/issues/78185">#78185</a> is time restricted. If the first acceptance test for recycler is coming this test will fail again.</p>
<p>New idea is to switch back to the beuser extension and change the order of installation and deinstallation of beuser.</p> TYPO3 Core - Bug #78401 (Closed): Workspaces preview page is brokenhttp://forge.typo3.org/issues/784012016-10-24T16:15:07ZMarco Breschmarco.bresch@starfinanz.de
<p>Since <a class="issue tracker-1 status-5 priority-4 priority-default closed child" title="Bug: replace extjs panels with pure css and get rid of the overhead (Closed)" href="http://forge.typo3.org/issues/52877">#52877</a> the JavaScript at the preview page of workspaces is broken:</p>
<p>JavaScript Error in sysext/backend/Resources/Public/JavaScript/ContextHelp.js line 48:<br /><code>Uncaught DOMException: Blocked a frame with origin "http://t3.dev" from accessing a cross-origin frame.</code></p> TYPO3 Core - Bug #78185 (Closed): Acceptance Test for Extension Manger fails since #77820http://forge.typo3.org/issues/781852016-10-07T18:37:46ZMarco Breschmarco.bresch@starfinanz.de
<p>The acceptance tests for beuser extension need to be installed as default. The acceptance test for the extension manager try to install the beuser extension. this test fail because the beuser extension is still loaded.</p>
<p>Solution: Switch to another extension which is not loaded by default (f.e. recycler).</p> TYPO3 Core - Bug #43032 (Closed): redirectPageLogout conflicts with $TYPO3_CONF_VARS['FE']['pageN...http://forge.typo3.org/issues/430322012-11-16T17:29:49ZMarco Breschmarco.bresch@starfinanz.de
<p>Logout-Button is located on a page not accessible for logged out users.<br />RedirectPageLogout of felogin is set to a page with no access restrictions.<br />This configuration worked fine, I will be redirected to the specified page after logout.<br />After setting $TYPO3_CONF_VARS['FE']['pageNotFound_handling'] to another accessible page I will always be redirected to this page and not to the one specified in redirectPageLogout.<br />It seems the problem arises in class.t3lib_userauth.php. There the function checkAuthentication is called and performs the log off. It seems that after that the protected page would be simply recognized as „not accessible or missing“ and therefor the pageNotFound_handling is called instead of checking for any redirectPageLogout settings.</p> TYPO3 Core - Bug #32040 (Closed): BE-User Admin module column 'workspaces membership' needs to be...http://forge.typo3.org/issues/320402011-11-23T17:22:53ZMarco Breschmarco.bresch@starfinanz.de
<p>The column 'workspaces membership' have a XSS vulnerability.</p>
<p>As described in <a class="external" href="http://buzz.typo3.org/teams/security/article/incident-handling-of-typo3-core-issues">http://buzz.typo3.org/teams/security/article/incident-handling-of-typo3-core-issues</a> this bug can be public. I will submit my fix to Gerrit soon.</p> TYPO3 Core - Bug #31762 (Closed): Quotes in workspace title is displayed &qout; in workspaces tabshttp://forge.typo3.org/issues/317622011-11-11T16:23:26ZMarco Breschmarco.bresch@starfinanz.de
<p>Because of double htmlspecialchar for the tabs. In all other places the workspace title is rendered correctly.</p>
<p>Toolbar, toolbarmenu and grid seems to be okay.</p> TYPO3 Core - Bug #30659 (Closed): 'next stage'-button is not visible when the stage title is to longhttp://forge.typo3.org/issues/306592011-10-08T15:02:27ZMarco Breschmarco.bresch@starfinanz.de
<p>The minimal column width is calculated by the stage title only. It is necessary to calculate the width of the stage title plus the width of icons.</p> TYPO3 Core - Feature #10439 (Closed): Data array used in ws-grid should be cachedhttp://forge.typo3.org/issues/104392010-10-25T19:31:15ZMarco Breschmarco.bresch@starfinanz.de
<p>The hole data array is build at each request. To prevent server time a caching mechanism is needed.</p>
<p>see <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Implement serverbased sorting for the grid (Closed)" href="http://forge.typo3.org/issues/10045">#10045</a></p> TYPO3 Core - Feature #10045 (Closed): Implement serverbased sorting for the gridhttp://forge.typo3.org/issues/100452010-10-04T11:15:48ZMarco Breschmarco.bresch@starfinanz.de
<p>Now the grid support local sorting. To make the pagening work as expected - the pagening sould be use the current sorting - the romote sorting is necessary.</p>