TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692006-12-14T16:08:07ZTYPO3 Forge
Redmine TYPO3 Core - Feature #16787 (Closed): New feature: config.softExcludehttp://forge.typo3.org/issues/167872006-12-14T16:08:07ZKasper Skårhøjkasper2007@typo3.com
<p>The feature config.sys_language_softMergeIfNotBlank sets the "mergeIfNotBlank" for a field in the frontend context through TypoScript. It can be useful to have the same for "exclude" localization mode so a field is always overlaid in the frontend output. This patch simply copies the code from "softMergeIfNotBlank" and does the same for "exclude".</p>
<p>See Additional below for documentation snipped for TSref.</p>
<p>TSref documentation, CONFIG object:<br />Property: sys_language_softMergeIfNotBlank<br />Data Type: string<br />Description: Setting additional "exclude" flags for l10n_mode in TCA for frontend rendering. Works exactly like sys_language_softMergeIfNotBlank (see that for details - same Syntax!).<br />Fields set in this property will override if the same field is set for "sys_language_softMergeIfNotBlank" <br />(issue imported from #M4656)</p> TYPO3 Core - Bug #15869 (Closed): Selection of Template Records in a draft workspace doesn't filt...http://forge.typo3.org/issues/158692006-03-21T12:24:57ZKasper Skårhøjkasper2007@typo3.com
<p>In t3lib_tstemplate.php the template records from the root line is collected by a series of SQL statements. Template Records are filtered with $this->whereClause which includes check for "enableFields" and "deleted", all initialize in the init() function.<br />Under preview in draft workspaces the correct behaviour would be to select all records and filter away those which are marked deleted, hidden in the workspace, start/endtime in workspace etc. This doesn't happen at the moment.<br />However, I don't consider the fix trivial because it must be made sure that any draft composition of template records is _NOT_cached (which could affect online site).</p>
<p>(issue imported from #M2946)</p> TYPO3 Core - Bug #15861 (Closed): Recent "fixes" in t3lib_loaddbgroup introduces potentially hard...http://forge.typo3.org/issues/158612006-03-20T12:27:34ZKasper Skårhøjkasper2007@typo3.com
<p>The internal variable ->itemArray in t3lib_loaddbgroup doesn't use numerical keys that indicates order of elements. The key is now a string, being a combination of table and uid.</p>
<p>This introduces the following problems:<br />- Applications like sys_refindex (core), TemplaVoila (external!) are using the key as sorting key (0,1,2...) etc. We can't know how many other applications are relying on this (for years!)<br />- Using table_uid will disallow duplicate entries in the array - an obvious feature of TYPO3!!!<br />- The implementation is probably buggy; in function readList() values are put into $this->itemArray[$itemKey] and $this->itemArray[$key] suggesting an incomplete implementation.</p>
<p>I would like this reverted immediately or otherwise be presented for compelling evidence why this is necessary!</p>
<p>I would also like to know how Rene will defend that a (de facto) "public API" like ->itemArray should change so radically.</p>
<p>(issue imported from #M2932)</p> TYPO3 Core - Bug #15832 (Closed): Undo/Redo button doesn't work - and History view has bad usabil...http://forge.typo3.org/issues/158322006-03-15T15:27:22ZKasper Skårhøjkasper2007@typo3.com
<p>When editing records the Undo/Redo button which is a part of the panel of buttons for saving/closing a form etc. can usually be clicked and it will revert to previous state of record. Currently this links to the history module but stays there instead of reverting and redirecting back! This must be a bug Sebastian introduced during his re-wamp.<br />And talking about the history module: Its just fine with all those nice selectors, checkboxes etc. but there <em>must</em> be a simple, intuitive button like before which one can click to revert. I was desperately looking for a "commit" button somewhere after having selected, click etc on diverse buttons and seen nice previews of this and that - but the simple button was missing. We need that pencil with the arrow back in!</p>
<p>(issue imported from #M2880)</p> TYPO3 Core - Bug #15772 (Closed): "NOT NULL" removed from SQL gives error with MySQL 3.23.52http://forge.typo3.org/issues/157722006-03-06T19:54:31ZKasper Skårhøjkasper2007@typo3.com
<p>Lines 324ff in class.t3lib_install.php</p>
<pre><code>// Remove NOT NULL statements (they are not needed)<br /> $parts[1] = str_replace(' NOT NULL', '', $parts[1]);</code></pre>
<p>results in an error with MySQL 3.23.52 because two new tables (sys_refindex + sys_preview) in TYPO3 4.0 uses a varchar(32) field as primary key and primary keys in that MySQL version seems to require the "NOT NULL" attribute.<br />This will surely be a problem when people begin to upgrade sites.</p>
<p>(issue imported from #M2777)</p>