TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-11-10T20:19:18ZTYPO3 Forge
Redmine TYPO3 Core - Task #95954 (Closed): Reduce inline JavaScript in FormEngine AJAX responseshttp://forge.typo3.org/issues/959542021-11-10T20:19:18ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Bug #24439 (Closed): TYPO3 fails to install on Windows due to faulty disposal of MCR...http://forge.typo3.org/issues/244392010-12-29T16:35:54ZOliver Haderoliver.hader@typo3.org
<p><b>This was reported by direct mail by Jan Reilink (janreilink (at) vevida (dot) com):</b></p>
<p>Typo3 (version 4.4.6) fails to install on Windows, due to improper<br />checking of MCRYPT_DEV_URANDOM capabilities. As you know, /dev/urandom<br />is not available on Windows. In the last week, two customers couldn't<br />install TYPO3 on their web site as a result.</p>
<p>I hacked my patch in the existence checking of the PHP-function<br />mcrypt_create_iv (also attached as .patch-file).</p>
<p>It could also be hacked in the class.t3lib_div.php file on/after line<br />1610, with a simple "elseif" line.</p>
<p>(issue imported from #M16871)</p> TYPO3 Core - Bug #24096 (Closed): Call to undefined method SC_mod_tools_em_index::uploadExtension...http://forge.typo3.org/issues/240962010-11-17T09:01:57ZOliver Haderoliver.hader@typo3.org
<p>Uploading an extension to TER is not possible in the Extension Manager due to the PHP fatal error:<br />Call to undefined method SC_mod_tools_em_index::uploadExtensionToTER()</p>
<p>(issue imported from #M16436)</p> TYPO3 Core - Bug #23521 (Rejected): Flash Uploader does not work if cookieHttpOnly is enabledhttp://forge.typo3.org/issues/235212010-09-09T13:10:57ZOliver Haderoliver.hader@typo3.org
<p>The Flash Uploader does not work if the TYPO3_CONF_VARS setting "cookieHttpOnly" is enabled. After uploading a file, the uploader just shows a "303" error.</p>
<p>"303" is a HTTP status code and tells that there was a redirect since the backend user could not be authorized to have access to the TYPO3 backend.</p>
<p>(issue imported from #M15673)</p> TYPO3 Core - Bug #22349 (Closed): RTE is collapsed when loaded inside a hidden tab in Safarihttp://forge.typo3.org/issues/223492010-03-29T21:58:15ZOliver Haderoliver.hader@typo3.org
<p>The rich text editor is not loaded when it's placed on a hidden tab in Safari on Mac OS X. If the accordant tab gets enabled, RTE won't load correctly (see the attached screenshot). Could not reproduce this behaviour in Firefox.</p>
<p>The RTE is loaded, but the editing area is collapsed (height is zero). Resizing makes it appear.</p>
<p>The problem exists when loading the RTE in a hidden tab in all browsers except Firefox.<br />(issue imported from #M13956)</p> TYPO3 Core - Bug #21726 (Closed): Updating translations from repository in extension manager fail...http://forge.typo3.org/issues/217262009-11-28T15:53:33ZOliver Haderoliver.hader@typo3.org
<p>Updating translations from repository in extension manager fails in Safari 4.0.4 on Mac OS X. Just a white page is shown - after a while, when all packages have been downloaded, suddenly the full status appears. Thus, showing the process dynamically does not work.</p>
<p>In Firefox everything works as expected.</p>
<p>(issue imported from #M12822)</p> TYPO3 Core - Bug #21557 (Closed): Use flash messages to show SQL debug errors in the backendhttp://forge.typo3.org/issues/215572009-11-15T17:32:22ZOliver Haderoliver.hader@typo3.org
<p>If sqlDebug is enabled to visualize SQL errors this currently breaks the document and in TCEforms buttons cannot be clicked anymore.</p>
<p>Flash messages should be used to solve this issue.</p>
<p>(issue imported from #M12598)</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 #21427 (Closed): Integrate checks concerning Suhosin/Hardened PHP in Install Toolhttp://forge.typo3.org/issues/214272009-11-02T18:28:26ZOliver Haderoliver.hader@typo3.org
The Suhosin/Hardened PHP Project allows to set limits to several PHP transmission (e.g. number of POST arguments) that might result to misbehaviours in TYPO3, in e.g.
<ul>
<li>Install-Tool: All configuration</li>
<li>Install-Tool: DB Analyzer</li>
<li>Inline Releational Record Editing with nested child records</li>
</ul>
A part in the install tool should check whether Suhosin is active and whether the PHP configuration for that should be changed - e.g.:
<ul>
<li>suhosin.request.max_vars - default is 200, should be 500 or more</li>
<li>suhosin.post.max_vars - default is 200, should be 400 or more</li>
</ul>
<p><a class="external" href="http://www.hardened-php.net/suhosin/configuration.html">http://www.hardened-php.net/suhosin/configuration.html</a><br />(issue imported from #M12436)</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 #21044 (Closed): Do not show E_DEPRECATED messages on productive systemshttp://forge.typo3.org/issues/210442009-09-12T23:03:39ZOliver Haderoliver.hader@typo3.org
<p>With PHP 5.3 the error level E_DEPRECATED was introduced that shows messages concerning deprecated PHP methods and behaviours.</p>
<p>To avoid displaying these messages on productive systems, the error_reporting (e.g. used in index_ts.php) should be extended like this:</p>
<p>error_reporting (E_ALL ^ E_NOTICE ^ E_DEPRECATED);</p>
<p>Branches: Trunk, 4_2, 4_1 <br />(issue imported from #M11937)</p> TYPO3 Core - Feature #20294 (Closed): Integrate possibility to validate custom links for RTEhtmla...http://forge.typo3.org/issues/202942009-04-08T13:12:09ZOliver Haderoliver.hader@typo3.org
<p>In RTEhtmlarea there's a possibility to define custom links, e.g. by using a link handler. It might happen, that the name of the linkhandler (defined in $TYPO3_CONF_VARS['SC_OPTIONS']['tslib/class.tslib_content.php']['typolinkLinkHandler']) is different to the used link prefix (e.g. "linkhandler" vs. "myOwnLinkhandler:"). Furthermore it can happen that those custom links are not defined using a linkhandler at all.<br />Links that could not be validated by the current strict mechanism are shown as invalid in RTEhtmlarea.</p>
<p>The solution is to integrate a new hook that can take care of that validation in general.</p>
<p>(issue imported from #M10872)</p> TYPO3 Core - Bug #19264 (Closed): External URLs cannot be set in RTEhtmlarea anymorehttp://forge.typo3.org/issues/192642008-08-29T14:31:33ZOliver Haderoliver.hader@typo3.org
<p>Since of revision 4006 in SVN Trunk, setting links on the tab "External URL" does not work anymore. On trying to set "http://www.google.com/" and hitting the "Set Link" some JavaScript error occurs and the browse link window gets closed without setting the link.</p>
<p>This bug only occurs in Firefox.</p>
<p>With SVN rev. 4005, everything is fine<br />With SVN rev. 4006 and any later revision, this error occurs.</p>
<p>(issue imported from #M9255)</p> TYPO3 Core - Bug #17828 (Closed): RTEhtmlarea doesn't work with IRRE anymorehttp://forge.typo3.org/issues/178282007-11-21T17:59:15ZOliver Haderoliver.hader@typo3.org
<p>In FF2, when having some IRRE elements, the error occours on opening them:<br />uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMNSHTMLDocument.queryCommandEnabled]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: <a class="external" href="http://www.fotobuch.de/typo3temp/rtehtmlarea/htmlarea_ed1449a90a31a33b666f.js">http://www.fotobuch.de/typo3temp/rtehtmlarea/htmlarea_ed1449a90a31a33b666f.js</a> :: anonymous :: line 227" data: no]</p>
<p>Works in IE7</p>
<p>(issue imported from #M6788)</p>