TYPO3 Forge: Issues
http://forge.typo3.org/
http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?1705866169
2012-05-04T12:35:02Z
TYPO3 Forge
Redmine
TYPO3 Core - Feature #36839 (Closed): Add getUid method to abstract record collection
http://forge.typo3.org/issues/36839
2012-05-04T12:35:02Z
Ingmar Schlecht
ingmar@typo3.org
<p>Add getUid method to abstract record collection</p>
TYPO3 Core - Feature #36810 (Closed): Filtering "group" and "inline" field items in TCEMain
http://forge.typo3.org/issues/36810
2012-05-03T14:25:44Z
Ingmar Schlecht
ingmar@typo3.org
<p>For some situations it would be great if it was possible to allow relations to only certain foreign records in a "group" type relationship.</p>
<p>In "select" fields that is possible via the "foreign_where_clause", but for "group" fields there is no such possibility.</p>
<p>This patch implements that functionality in a versatile way, which is also used by the FAL core parts, to ensure only relations to allowed file types (such as "images only") are ensured as configured in specific locations.</p>
TYPO3 Core - Feature #33045 (Closed): Enable TCA type field to depend on field of foreign table b...
http://forge.typo3.org/issues/33045
2012-01-08T14:45:02Z
Ingmar Schlecht
ingmar@typo3.org
<p>Sometimes it would be useful to make a TCA type switch not directly based on a value of the current record, but based on a value of another table.</p>
<p>This is e.g. useful for IRRE when used with an intermediate table (making a relation to a third table). Sometimes it's useful to make the fields dependent on the type field of the third table.</p>
<p>Say you have a relation between "houses" and "building objects" and an "intermediate table" for making the relation and storing some properties on how exactly the building objects are used in that particular house. Now, depending on the "building object" that the user makes a relation to, the intermediate table should show different fields.</p>
<p>The patch (as pushed to gerrit) implements this.</p>
TYPO3 Core - Feature #33044 (Closed): Add possitbility to create hidden palettes in TCEForms
http://forge.typo3.org/issues/33044
2012-01-08T14:17:47Z
Ingmar Schlecht
ingmar@typo3.org
<p>Hi guys,</p>
<p>sometimes it's useful to have fields rendered in TCEForms, but never display them anywhere.</p>
<p>One such occasion, where that is useful, is for the "foreign_field" feature of IRRE. As you might know, IRRE makes it possible to render something called a "foreign_selector" which lets the user choose from records of another (third) table (not the IRRE child table) to create relations to by using an intermediate table (the IRRE child table). However, there is one problem with it: IRRE requires the field of the intermediate table, which carries the link to the third table, to be always displayed in the form, even though it only carries technical information (the relation) which the user doesn't need to see at all. Of course, one could also change IRRE to not require the field to be present any more, but that would be technically much more challenging and more error prone.</p>
<p>Also, there might be other cases where it's useful to render a field but not display it anywhere, e.g. when you want to set a value of a (hidden) field by some JavaScript of a user-defined (other) field. Therefore, the feature to hide a field is rather universally useful.</p>
<p>Now: Why go the way of "hidden palettes" instead of "hidden fields" directly?</p>
There are two points speaking in favour of implementing the hide functionality per palette instead of per field:
<ul>
<li>It's more flexible: Fields can be hidden in one scenario and displayed in another scenario (depending on which palette they're rendered in)</li>
<li>it's easier to implement: For palettes, you can simply hide the link to the palette. For fields, it's hard to do, because fields always go into a strict template for which a new table row is created by TCEForms, so they remain visible.</li>
</ul>
TYPO3 Core - Feature #29296 (Closed): Add possibility to define foreign_match_fields for IRRE inl...
http://forge.typo3.org/issues/29296
2011-08-27T15:13:32Z
Ingmar Schlecht
ingmar@typo3.org
<p>This patch request adds the possibility to define foreign_match_fields (similar to MM_match_fields) for IRRE inline relations. This is required for the upcoming file abstraction layer in TYPO3.</p>
<p>New documentation:</p>
<p>For TYPO3 Core API, Chapter: ['columns'][fieldname]['config'] / TYPE: "inline"</p>
<p><a class="external" href="http://typo3.org/documentation/document-library/core-documentation/doc_core_api/4.3.0/view/4/2/#id2529282">http://typo3.org/documentation/document-library/core-documentation/doc_core_api/4.3.0/view/4/2/#id2529282</a></p>
<p>parameter name: foreign_match_fields<br />parameter type: array<br />parameter description: Array of field=>value pairs to both insert and match against when writing/reading IRRE relations. This feature is useful if you want to use the same child table in two inline fields within the same parent table. In that case you can then define an "identifier" field in the child record to distinguish the two relations.</p>
TYPO3 Core - Bug #23731 (Closed): Felogin shouldn't show the permalogin form controls when permal...
http://forge.typo3.org/issues/23731
2010-10-14T18:32:31Z
Ingmar Schlecht
ingmar@typo3.org
<p>The subject says it all:</p>
<p>Felogin shouldn't show the permalogin form controls when permalogin is set to "forced on" in intall tool.</p>
<p>(issue imported from #M15993)</p>
TYPO3 Core - Bug #25621 (Closed): Creation of late task
http://forge.typo3.org/issues/25621
2009-10-10T11:27:40Z
Ingmar Schlecht
ingmar@typo3.org
<p>I have a question (or maybe a feature request) regarding the creation of single (not recurring) tasks.</p>
<p>When I enter a date as "start date" that lies in the past, the BE module detects that and on-save changes the record to "disabled". So directly after saving the status of the newly created task is "Disabled, will not be executed, except manually".</p>
<p>Wouldn't it be nicer if it was instead "Late, will run with next execution"? I think people would expect that and also it would be a very convenient way to make tasks execute at the next occasion: Just set the date to something in the past, and it will appear as "Late".</p>
<p>(issue imported from #M12177)</p>
TYPO3 Core - Bug #20716 (Closed): ChangeLog is quite big and could be split to multiple files
http://forge.typo3.org/issues/20716
2009-07-04T14:46:02Z
Ingmar Schlecht
ingmar@typo3.org
<p>The ChangeLog file is getting bigger and bigger, though usually people are only interested in the changes since the last major revision.</p>
<p>In order to shorten (i.e. split up into multiple files) the file, Marcus Krause suggested the following to the dev mailing list:<br />_<em><i></em></i>__<em>_</em>___________________________<br />If there's a consensus to shorten the file, we could handle it the way<br />e.g. apache does:<br /><a class="external" href="http://svn.apache.org/viewvc/httpd/httpd/trunk/CHANGES?revision=790587">http://svn.apache.org/viewvc/httpd/httpd/trunk/CHANGES?revision=790587</a></p>
<p>Example for 4-2:</p>
<p>At the bottom of the file:<br />Changes with TYPO3 4-1:</p>
<ul>
<li><a class="external" href="https://svn.typo3.org/TYPO3v4/Core/branches/TYPO3_4-1/ChangeLog">https://svn.typo3.org/TYPO3v4/Core/branches/TYPO3_4-1/ChangeLog</a><br />_<em><i></em></i>__<em>_</em>___________________________</li>
</ul>
<p>(issue imported from #M11473)</p>
TYPO3 Core - Bug #18934 (Closed): Default value of fileDenyPattern allows arbitrary code executio...
http://forge.typo3.org/issues/18934
2008-06-11T08:22:57Z
Ingmar Schlecht
ingmar@typo3.org
<p>See <a class="external" href="http://typo3.org/teams/security/security-bulletins/typo3-20080611-1/">http://typo3.org/teams/security/security-bulletins/typo3-20080611-1/</a></p>
<p>(issue imported from #M8674)</p>
TYPO3 Core - Feature #16462 (Closed): AJAX Page Tree
http://forge.typo3.org/issues/16462
2006-08-12T23:54:22Z
Ingmar Schlecht
ingmar@typo3.org
<p>The page tree should only load needed parts when the user expands/collapses branches of the tree.</p>
<p>(issue imported from #M4031)</p>
TYPO3 Core - Bug #15188 (Closed): EM doesn't check for dependancies on Extension update
http://forge.typo3.org/issues/15188
2005-11-08T06:19:01Z
Ingmar Schlecht
ingmar@typo3.org
<p>The EM doesn't check for dependancies when you upgrade an extension.</p>
<p>That causes the following error message when you update from an older version of tt_products to the latest: "TYPO3 Fatal Error: Extension key "fh_library" was NOT loaded! (t3lib_extMgm::extPath)".</p>
<p>(issue imported from #M1807)</p>
TYPO3 Core - Bug #15050 (Closed): Gremlin: Filelist module should have "New" button
http://forge.typo3.org/issues/15050
2005-10-14T06:02:02Z
Ingmar Schlecht
ingmar@typo3.org
<p>At the moment, the only way to create files or folders in the Filelist module is by clicking the clickmenu.<br />Most newcomers seem to look for it in the module itself (right frame). Would be cool, if a "new" button could be inserted there.</p>
<p>(issue imported from #M1599)</p>
TYPO3 Core - Bug #15049 (Closed): Gremlin: "Useradmin" BE Module should have "Create BE User" button
http://forge.typo3.org/issues/15049
2005-10-14T05:56:58Z
Ingmar Schlecht
ingmar@typo3.org
<p>The BE module "Useradmin" should have a "Create BE User" button.<br />That's the place where all newcomers are looking for it.</p>
<p>(issue imported from #M1598)</p>
TYPO3 Core - Bug #14694 (Closed): Help->About module broken
http://forge.typo3.org/issues/14694
2005-04-20T18:16:33Z
Ingmar Schlecht
ingmar@typo3.org
<p>The Help->About module is broken.</p>
<p>This is the string it shows:</p>
<p>"TYPO3 is a flexible and professional Open Source Web-CMS based on PHP4 and MySQL.br /br /TYPO3 is bfreely available/b under the a href=http://typo3.com/1244.0.html target=_blankTYPO3-license (GNU/GPL)/a.br /br /TYPO3 Ver. 3.8.0beta2.1, Copyright © 1998-2005 Kasper Skårhøjbr /"</p>
<p>It seems like the string is passed thru htmlspecialchars() but shouldn't.</p>
<p>Would be cool if one of the bug fixers could care about this.</p>
<p>The file in question is probably typo3/mod/help/about/index.php<br />(issue imported from #M1009)</p>
TYPO3 Core - Feature #14240 (Closed): A memory_limit of NULL should be interpreted as "no limit" ...
http://forge.typo3.org/issues/14240
2004-07-15T14:40:48Z
Ingmar Schlecht
ingmar@typo3.org
<p>Well, the subject line basically says it:<br />A memory_limit of NULL should be interpreted as "no limit" instead of 0 MB.</p>
<p>(issue imported from #M218)</p>