TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692015-10-10T10:58:11ZTYPO3 Forge
Redmine TYPO3 Core - Task #70563 (Rejected): Reduce overridden wrapper methodshttp://forge.typo3.org/issues/705632015-10-10T10:58:11ZOliver Haderoliver.hader@typo3.org
Make use of class inheritance and remove superfluous specific methods
<ul>
<li>getLanguageService()</li>
<li>getBackendUserAuthentication()</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 - Feature #50828 (Rejected): Fallback storage "zero" shall be read-onlyhttp://forge.typo3.org/issues/508282013-08-06T15:27:20ZOliver Haderoliver.hader@typo3.org
<p>The fallback storage "zero" (uid:0) shall be read-only since it is used as fallback for /uploads/* and /typo3conf/ext/* resources.</p> TYPO3 Core - Task #45151 (Rejected): IRRE 1n:csv parent records point to workspace placeholderhttp://forge.typo3.org/issues/451512013-02-04T23:12:00ZOliver Haderoliver.hader@typo3.org
<p>IRRE 1n:csv parent records point to workspace placeholder instead of using the specific versioned record on copying.<br />If records are copied or newly created on a workspace, a version placeholder is created and overlayed by the specific version of the record.</p>
<p>The fix is to resolve the specific version uid of the record.</p> TYPO3 Core - Task #45132 (Rejected): Faulty translation behavior of IRRE using workspaceshttp://forge.typo3.org/issues/451322013-02-04T13:41:54ZOliver Haderoliver.hader@typo3.org
<p>The translation behavior of IRRE child records on workspaces is wrong on plain new records.</p>
<p>Inline Relational Records editing used the most specific version of a record for references. In case of creating new records on a workspace, a version placeholder record will be generated as well as a specific version to overlay that placeholder. Translations of a record will copy the accordant record and refer to it by using the l18n_parent field ("transOrigPointerField" in TCA). For historic reasons the uid of the placeholder record is used in that case instead of the most specific version - otherwise relations between original and translation are not recognized in several places in TYPO3 (which is actually the real bug, but cannot be resolved easily on the fly for historical reasons).</p>
<p>Thus, the bug fix is to use the uid of the placeholder record in those cases instead and to adopt the form view component of IRRE to recognize those placeholders as translation parents as well.</p> TYPO3 Core - Bug #39968 (Rejected): Collections use t3lib_BEfunchttp://forge.typo3.org/issues/399682012-08-19T15:43:17ZOliver Haderoliver.hader@typo3.org
<p>t3lib_collections use e.g. t3lib_BEfunc calls that won't work in the frontend.</p> TYPO3 Core - Bug #39727 (Rejected): Calculating percentage of differences is slowhttp://forge.typo3.org/issues/397272012-08-12T15:32:20ZOliver Haderoliver.hader@typo3.org
<p>The workspace view in the backend has a feature to calculate the percentage of differences between live and workspace version.<br />This implementation iterates over each record and each field by using the PHP method similar_text().<br />The complexity of similar_text() is measured with O(n^3) which quickly can turn into a nice waiting period if string length is more than approx 4000 characters.</p>
Changes:
<ul>
<li>use a different approach if string length is more than 2048 or 4096 characters</li>
<li>remove MD5 sums on files which also can turn out in a nice waiting period</li>
<li>do not resolve fields that hold m:n relations to reduce tree complexity and database queries</li>
</ul>
<p>Maybe disable this feature in newer versions at all or us a simple MD5 based comparison of the field contents which reads then "n% of the all fields have been modified".</p> TYPO3 Core - Feature #38239 (Rejected): Introduce context based URL processing of FAL resourceshttp://forge.typo3.org/issues/382392012-06-20T23:36:55ZOliver Haderoliver.hader@typo3.org
<p>If one would like to modify an URL of a file that is served by an external FAL storage, this needs to be done for a given rendering context.<br />This change (re-)introduces a hook in tslib_cObj that passes the accordant file and the context TypoScript configuration along.</p> TYPO3 Core - Feature #38233 (Rejected): Add event handling to bootstrap mechanismhttp://forge.typo3.org/issues/382332012-06-20T19:58:14ZOliver Haderoliver.hader@typo3.org
<p>Add several events like "database is initialized", "bootstrap is initialized", etc. to the whole bootstrap mechanism.<br />The concrete situation to be solved is the registration of Extbase Signal Slots in ext_localconf.php - which fails since autoloader and caching framework are not yet initialized at the time the ext_localconf.php gets executed.</p> TYPO3 Core - Task #38087 (Rejected): Streamline typo3/classes naminghttp://forge.typo3.org/issues/380872012-06-15T16:09:26ZOliver Haderoliver.hader@typo3.org
<p>Streamline typo3/classes naming to be typo3/Classes</p> TYPO3 Core - Bug #31613 (Rejected): pi_list_browseresults misses SPAN_BEGIN substitutionhttp://forge.typo3.org/issues/316132011-11-06T13:11:53ZOliver Haderoliver.hader@typo3.org
<p>This issues happens in combination with tt_news which defines the label "pi_list_browseresults_displays" with a SPAN_BEGIN marker.<br />The replacement of this marker is already if the wrapper array does not define the "showResultsNumbersWrap" property, however it is missing if the property is defined.</p>
<p>The faulty result might look like this:<br /><pre>
<div class="showResultsWrap">News ###SPAN_BEGIN###%s bis %s von ###SPAN_BEGIN###%s</div>
</pre></p> TYPO3 Core - Task #31245 (Rejected): Integrate possibility to modify caching configurationshttp://forge.typo3.org/issues/312452011-10-24T23:45:47ZOliver Haderoliver.hader@typo3.org
<p>Once the caching framework was initialized and the caching configurations loaded - there is no way to add more caches during runtime. However this is required e.g. on installing extensions and initialize accordant caching tables.</p> TYPO3 Core - Bug #28955 (Rejected): Flushing database caches truncates table before dropping ithttp://forge.typo3.org/issues/289552011-08-12T21:38:37ZOliver Haderoliver.hader@typo3.org
<p>The database backend of the caching framework first truncates tables before dropping them.<br />This happens on calling the flush() method there and seems not to be required at all.</p> TYPO3 Core - Feature #26514 (Rejected): Add possibility to include files for the global variable ...http://forge.typo3.org/issues/265142011-04-29T19:42:36ZOliver Haderoliver.hader@typo3.org
<p>Since many global statements have been cleaned-up for TYPO3 4.6, a generic way to include files is required by respecting the possible global context.<br />The new functionality shall behave similar to t3lib_div::requireOnce().</p> TYPO3 Core - Feature #9754 (Rejected): Module: Implement Workspaces List tabhttp://forge.typo3.org/issues/97542010-09-16T12:01:32ZOliver Haderoliver.hader@typo3.org
<p>Implement Workspaces List tab</p>