TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692020-12-04T08:59:10ZTYPO3 Forge
Redmine TYPO3 Core - Bug #92985 (Rejected): Cannot show record history of pages anymore in TYPO3 v10.4.10http://forge.typo3.org/issues/929852020-12-04T08:59:10ZOliver Haderoliver.hader@typo3.org
<blockquote>
<p>(1/3) Doctrine\DBAL\Exception\InvalidFieldNameException<br />An exception occurred while executing 'SELECT `uid` FROM `tx_impexp_presets` WHERE `pid` = ?' with params > [81]: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'pid' in 'where clause'</p>
<p>...</p>
<p>at TYPO3\CMS\Core\Database\Query\QueryBuilder->execute()<br />typo3/sysext/backend/Classes/History/RecordHistory.php line 328</p>
</blockquote>
<p>How to reproduce:</p>
<ul>
<li>(update TYPO3 v10.4.9 to v10.4.10)</li>
<li>(impexp system extension must be enabled)</li>
<li>use context menu in page-tree to show record history</li>
</ul>
<p>Reasons:</p>
<ul>
<li>looks like <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/66582">https://review.typo3.org/c/Packages/TYPO3.CMS/+/66582</a> changes database definition and introduces new TCA table</li>
<li>records history iterates over all TCA tables - applying <code>pid</code> constraint for <code>pages</code></li>
<li><code>pid</code> column does not exist unless database migration in Install Tool was executed (which should not be required for patch level releases)</li>
<li>affects TYPO3 v10 only</li>
</ul> TYPO3 Core - Task #92521 (Rejected): Add random value generator for custom alphabethttp://forge.typo3.org/issues/925212020-10-08T17:40:28ZOliver Haderoliver.hader@typo3.org
<p>Add library functions that allow generating random values for a particular alphabet - this also avoids duplications in user-land code.</p> TYPO3 Core - Bug #87303 (Rejected): Disable autocomplete for login formshttp://forge.typo3.org/issues/873032018-12-27T14:12:09ZOliver Haderoliver.hader@typo3.org
<p>In order to apply strong security defaults it is suggested to disable autocomplete of login forms.</p>
References:
<ul>
<li><a class="external" href="https://portswigger.net/kb/issues/00500800_password-field-with-autocomplete-enabled">https://portswigger.net/kb/issues/00500800_password-field-with-autocomplete-enabled</a></li>
</ul> TYPO3 Core - Feature #85051 (Rejected): Add possibility to deny setting cookies on client sidehttp://forge.typo3.org/issues/850512018-05-19T14:22:19ZOliver Haderoliver.hader@typo3.org
<p>In the scope of GDPR and ePrivacy regulations inside the EU it become required that users provide agreement before any cookies are set.<br />Since the TYPO3 core sets a couple of cookie automatically it is required to introduce an API that is capable of individually allow/deny cookies by individual handlers that might be provided by one or some 3rd party extensions.</p> TYPO3 Core - Bug #85000 (Rejected): Cannot add image using element browserhttp://forge.typo3.org/issues/850002018-05-14T15:40:54ZOliver Haderoliver.hader@typo3.org
<a name="Steps"></a>
<h2 >Steps<a href="#Steps" class="wiki-anchor">¶</a></h2>
<ul>
<li>backend, edit tt_content in FormEngine of type text/image</li>
<li>open add new image dialog</li>
<li>after selecting image (SVG in this case) console error is shown</li>
</ul>
<a name="Misbehavior"></a>
<h2 >Misbehavior<a href="#Misbehavior" class="wiki-anchor">¶</a></h2>
<p>Console error <code>Uncaught TypeError: Cannot read property 'data-52-tt_content-472-image-sys_file_reference' of undefined</code><br />Refers to <code>jsfunc.inline.js</code> in method <code>getContext: function(objectId)</code></p> 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 - 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 - Feature #39729 (Rejected): Allow to disable Extbase TypoScript parsing in backendhttp://forge.typo3.org/issues/397292012-08-12T15:39:41ZOliver Haderoliver.hader@typo3.org
<p>This is basically related to Extbase and the fact that the frontend TypoScript is loaded and parsed for each dispatching acting for backend modules. In case the frontend TypoScript does not have any valuable information on dependency injection nor on persistence settings, the parsing part could be skipped completely by an according configuration.</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 #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 - 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 #25223 (Rejected): Enable TCA property displayCond for IRRE child recordshttp://forge.typo3.org/issues/252232011-03-02T14:54:11ZOliver Haderoliver.hader@typo3.org
<p>Imagine that particular fields of an IRRE child record shall only be shown depending on a value in the parent record. Currently there is no easy way to access evaluate the parent record and define a behaviour.</p>
<p>For Flexforms a similiar solution with displayCond is available, e.g.:<br /><pre>FIELD:parentRec.header:REQ:true</pre></p>
<p>However, it's problematic if the parent record is brand new and was not saved yet. In that case the field values of the parent should be transfered to the server side with the accordant AJAX request.</p>
<p>(issue imported from #M17824)</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> TYPO3 Core - Feature #20605 (Rejected): Add more information to logoff() method in user authentic...http://forge.typo3.org/issues/206052009-06-10T12:06:08ZOliver Haderoliver.hader@typo3.org
The TYPO3 user authentication (t3lib_userAuth) has a method logoff() that is called at several places but has no information what kind of "logoff" happens:
<ul>
<li>regular logoff, since user requested it (status=logout)</li>
<li>automatic logoff from old session when a new frontend user logs in</li>
<li>automatic logoff if session of logged in frontend user expired or no frontend user is logged in at all</li>
</ul>
Tasks:
<ul>
<li>constants shall be integrated and added to the logoff-calls, e.g. logoff(self::LOGOFF_ByUser)</li>
<li>logoff-status must be transferred to affected hooks in the logoff() method</li>
</ul>
<p>(issue imported from #M11313)</p> TYPO3 Core - Feature #17102 (Rejected): EM should inform admin if a local extension is outdated a...http://forge.typo3.org/issues/171022007-03-09T14:35:21ZOliver Haderoliver.hader@typo3.org
<p>This issue is more related to system extension as to others.<br />Imagine a site was running TYPO3 4.0.1 for several month and e.g. the RTEhtmlarea was installed locally from TER (with security patches, etc.). Now the admin decides to update to TYPO3 4.1.0. The RTEhtml will not work anymore, because the local installation of this extension (made for TYPO3 4.0.x) is not compatible to TYPO3 4.1.0 anymore.</p>
<p>The Extension Manager (perhaps additionally the update wizard of the install tool) should inform the admin, that the newer system extension is required and that he has to uninstall his local extension.</p>
<p>Just read bug-id <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: RTE does not load (Closed)" href="http://forge.typo3.org/issues/17082">#17082</a> to see what could happen.</p>
<p>(issue imported from #M5178)</p>