TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692017-10-19T14:46:38ZTYPO3 Forge
Redmine TYPO3 Core - Task #82811 (Closed): Extend WorkspaceServiceTests for fetchPagesWithVersionsInTablehttp://forge.typo3.org/issues/828112017-10-19T14:46:38ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Task #55177 (Closed): Add concept of a default storagehttp://forge.typo3.org/issues/551772014-01-20T17:41:35ZOliver Haderoliver.hader@typo3.org
<ul>
<li>default storage is exclusively</li>
<li>is a substitute to previous /fileadmin/ directory</li>
<li>storage model get additional "isDefaultStorage" flag (boolean)</li>
<li>default storage can only exist once amongst all storages (unique)</li>
<li>new method ResourceFactory::getDefaultStorage() resolves this storage</li>
</ul> TYPO3 Core - Task #55083 (Rejected): Add prepared statement support for default database connectionhttp://forge.typo3.org/issues/550832014-01-16T17:44:36ZOliver Haderoliver.hader@typo3.org
<p>Albeit there is the PreparedStatement object, it is actually not used in the default database connection.<br />Using these prepared statements, e.g. for cache look ups, would gain some more speed (if database caching backends are used).</p> TYPO3 Core - Task #11162 (Closed): Suggest to Core and other extensions to increase the type of t...http://forge.typo3.org/issues/111622010-11-30T12:40:17ZOliver Haderoliver.hader@typo3.org
<p>Currently the field t3ver_stage which is defined by each module/extension that supports workspaces is defined as TINYINT and thus supports up to 255 stages. This was way enough until now - however since we have custom stages right now and each workspace can also have stages, it might happen that 255 is not enough anymore.</p>
<p>Thus, we should consider to give the suggestion to the Core and Extension Developers to use INT as storage type for the t3ver_stage field.</p> TYPO3 Core - Bug #11143 (Closed): Editing workspaces record shows PHP warninghttp://forge.typo3.org/issues/111432010-11-29T19:15:18ZOliver Haderoliver.hader@typo3.org
<p>PHP Warning<br />PHP Warning: parse_url(/typo3/alt_doc.php?returnUrl=http://myhost.com/typo3/mod.php?M=web_WorkspacesWorkspaces&workspace=2&tx_workspaces_web_workspacesworkspaces%5Baction%5D=index&tx_workspaces_web_workspacesworkspaces%5Bcontroller%5D=Review&id=0&edit[pages]<sup><a href="#fn212">212</a></sup>=edit) [function.parse-url]: Unable to parse URL in typo3/alt_doc.php line 216</p>
<p>-> returnUrl shall be URL encoded</p> TYPO3 Core - Feature #9820 (Closed): Module: Show legend below new grid componenthttp://forge.typo3.org/issues/98202010-09-18T17:56:11ZOliver Haderoliver.hader@typo3.org
<p>Module: Show legend below new grid component</p> TYPO3 Core - Feature #9758 (Closed): Module: Implement handler on the PHP side for the accordant ...http://forge.typo3.org/issues/97582010-09-16T12:10:30ZOliver Haderoliver.hader@typo3.org
<p>Implement handler on the PHP side for the accordant actions in the grid view in a new controller (Classes/Controller/).</p> TYPO3 Core - Feature #9753 (Closed): Module: Extend the ExtJS grid view and visualize the data de...http://forge.typo3.org/issues/97532010-09-16T11:58:56ZOliver Haderoliver.hader@typo3.org
<p>The data that is delivered must be visualized in the ExtJS grid view.</p> TYPO3 Core - Feature #9750 (Closed): Module: Take over wslib from versions extensionshttp://forge.typo3.org/issues/97502010-09-16T11:36:10ZOliver Haderoliver.hader@typo3.org
<p>Copy the required methods in the old wslib of the versions extension to the new workspaces manager.</p> TYPO3 Core - Bug #21428 (Closed): Recycler produces some scroll barshttp://forge.typo3.org/issues/214282009-11-02T18:55:19ZOliver Haderoliver.hader@typo3.org
<p>The recycler produces some scrollbars and this look a bit ugly.</p>
<ul>
<li>the recycler should use the whole dimension available in the viewport (no hardcoded dimensions)</li>
<li>the "recycler" title is not required</li>
<li>the "delete" and "undelete" buttons should be inside the panel and not below</li>
</ul>
<p>See the attached screenshot at a resolution of 1024x768 in Firefox 3 - even the action buttons below the panel are not visible.</p>
<p>(issue imported from #M12437)</p> TYPO3 Core - Bug #21382 (Closed): Context menu of page tree does not work anymorehttp://forge.typo3.org/issues/213822009-10-27T16:40:35ZOliver Haderoliver.hader@typo3.org
<p>If the "Disable Popup Context Menus" setting in "User Settings > Edit & Advanced functions" is enabled, the context menu of the page tree does not show up anymore.</p>
<p>top.loadTopMenu is not a function<br /><a class="external" href="http://website.com/typo3/js/clickmenu.js">http://website.com/typo3/js/clickmenu.js</a><br />Line 74</p>
<p>(Thanks to Sven Härtwig for pointing this out)</p>
<p>Tested with Firefox 3.5.3<br />(issue imported from #M12368)</p> TYPO3 Core - Bug #21364 (Closed): Integrate check to the install tool and reports module concerni...http://forge.typo3.org/issues/213642009-10-26T15:23:27ZOliver Haderoliver.hader@typo3.org
<p>There are some parts in the TYPO3 Core that require annotation parsing, e.g. Extbase and the unit tests. These parts grab the PHPdoc comments and search for annotations like "@test".</p>
<p>However, since eAccelerator can be compiled to strip all comments away, this would produce strange behaviours. Thus it's recommended to compile eAccelerator with this configuration:<br /><pre>--with-eaccelerator-doc-comment-inclusion</pre></p>
<p>See also first section concerning Extbase in the 4.3-alpha3 release notes:<br /><a class="external" href="http://news.typo3.org/news/article/typo3-43-alpha-3/">http://news.typo3.org/news/article/typo3-43-alpha-3/</a><br />(issue imported from #M12347)</p> TYPO3 Core - Bug #21077 (Closed): Remove reference operators for objectshttp://forge.typo3.org/issues/210772009-09-17T16:52:14ZOliver Haderoliver.hader@typo3.org
<p>Since PHP5 objects are used as reference by default. Thus, using the reference operator is not required anymore.</p>
<p>(issue imported from #M11984)</p> TYPO3 Core - Bug #20759 (Closed): Changing the workspace by the workspace selector produces JavaS...http://forge.typo3.org/issues/207592009-07-15T17:19:14ZOliver Haderoliver.hader@typo3.org
<p>On changing the workspace from e.g. live to draft by using the workspace selector, JavaScript errors appear. Firefox can handle them without any problem, however Internet Explorer has some severe problems with it.</p>
<p>Solution:<br />When the workspace got changed the selector puts a location.href to the top of the backend.php's JavaScript. It's preferred to use a real HTTP redirect instead of the JavaScript hack.</p>
<p>(issue imported from #M11541)</p> TYPO3 Core - Feature #20708 (Closed): Integrate possibility to disable redirects on the flyhttp://forge.typo3.org/issues/207082009-07-01T19:48:36ZOliver Haderoliver.hader@typo3.org
<p>The felogin extensions does not use and proper namespace to transfer data back to the TYPO3 system. Thus, it's not clear whether felogin or any other frontend login extension with an expected different behaviour submitted data.</p>
<p>Imagine a different second login form performs some actions (e.g. in a checkout process) and redirects should be disabled in this specific case.</p>
<p>(issue imported from #M11460)</p>