TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692020-11-25T09:37:55ZTYPO3 Forge
Redmine TYPO3 Core - Feature #92929 (Closed): Allow registering additional "trees" in Configuration Modulehttp://forge.typo3.org/issues/929292020-11-25T09:37:55ZSebastian Michaelsenmichaelsen@t3seo.de
<p>The list of available "trees" (<code>$GLOBALS['TYPO3_CONF_VARS']</code>, <code>$GLOBALS['TCA']</code>, ..., <code>Event Listeners</code>) of the Configuration module is hardcoded in the <a href="https://github.com/TYPO3/TYPO3.CMS/blob/73bcf9a1d971308f3ad66638ca1587a8dac8f681/typo3/sysext/lowlevel/Classes/Controller/ConfigurationController.php#L64" class="external">ConfigurationController</a> . An item for the form extension is <a href="https://github.com/TYPO3/TYPO3.CMS/blob/73bcf9a1d971308f3ad66638ca1587a8dac8f681/typo3/sysext/lowlevel/Classes/Controller/ConfigurationController.php#L179" class="external">added</a> via <code>if (ExtensionManagementUtility::isLoaded('form'))</code>.</p>
<p>Instead there should be an interface to add configration trees. The <code>form</code> extension and other extensions that maintain a configuration can then just add themselves to the module.</p> TYPO3 Core - Feature #49805 (Rejected): Access extConf in displayCondhttp://forge.typo3.org/issues/498052013-07-09T10:14:18ZSebastian Michaelsenmichaelsen@t3seo.de
<p>The displayCond directive allows to disable/enable a tceform field or flexform field based on various conditions.</p>
<p>Until now it's not possible to use the extConf (settings from ext_conf_template.txt) as condition.</p>
<p>Introduce new displayCond: EXT:EXTCONF:[settingsname]:[operator]:[value]</p>
<p>Allow the same operators like FIELD, which are: <, >, <=, >=, REQ, <del>, !</del>, IN, !IN, =, !=</p> TYPO3 Core - Feature #46460 (Closed): Introduce TCA displayCond type "USER"http://forge.typo3.org/issues/464602013-03-20T13:18:21ZSebastian Michaelsenmichaelsen@t3seo.de
<p>With displayCond you can evaluate each form field whether it should be displayed or not. There is a number of options, but you can't define a UserFunction if the options provided by the core don't fit your needs.</p>
<p>Usage example:<br />'displayCond' => 'USER:\\MyVendor\\MyExt\\UserFunction\\MyClass->displayCondition'</p> TYPO3 Core - Feature #45022 (Closed): Utility function to deprecate public method calls.http://forge.typo3.org/issues/450222013-01-31T13:50:38ZSebastian Michaelsenmichaelsen@t3seo.de
<p>At the moment we have a lot of public methods which are not intended for being public. We need a way to deprecate calling them publicly, therefore a Utility Function is introduced.</p>
<p>Usage:</p>
<pre>
/**
* @publicCallDeprecated Since 6.1. Will be protected 2 versions later
*/
public function privateFoo() {
GeneralUtility::logDeprecatedPublicMethodCall();
// do stuff
}
</pre>
<p>If the method is called publicy an entry like this is being made to the deprecation log:<br /><pre>
Deprecated public method call: MyClass->privateFoo() was called publicly which is deprecated (Since 6.1. Will be protected 2 versions later). [DEBUG TRAIL]
</pre></p>
<p>I'm not sure if it is ok to just invent a new phpDoc annotation. But it's the best solution I found to store information about the deprecation strategy.</p> TYPO3 Core - Task #44744 (Closed): Cleanups for sysext beloghttp://forge.typo3.org/issues/447442013-01-23T12:09:15ZSebastian Michaelsenmichaelsen@t3seo.de
<ul>
<li>Fix references to old classes</li>
<li>Use property injection where possible</li>
</ul> TYPO3 Core - Bug #43874 (Closed): array_merge_recursive_overrule: __UNSET can't unset array valueshttp://forge.typo3.org/issues/438742012-12-11T11:17:09ZSebastian Michaelsenmichaelsen@t3seo.de
<p>If the $enableUnsetFeature parameter is true, array_merge_recursive_overrule you can unset values from the first array.<br />The phpDoc says:<br /><pre>
* @param boolean $enableUnsetFeature If set, special values "__UNSET" can be used in the second array in order to unset array keys in the resulting array.
</pre><br />But in fact keys are only unset if they don't hold an array value. I see no reason why this should be like this. There should be the possibility to unset array values.</p> TYPO3 Core - Task #40870 (Closed): Add Utility Functions to retreive Information from Class Nameshttp://forge.typo3.org/issues/408702012-09-12T16:23:02ZSebastian Michaelsenmichaelsen@t3seo.de
<p>My intention is to introduce these 2 Utility Functions:</p>
<p>\TYPO3\CMS\Core\Extension\ExtensionManager::getClassNameWithoutVendorAndProduct($className)<br />\TYPO3\CMS\Core\Extension\ExtensionManager::getExtensionKeyFromClassName($className)</p>
<p>These can be used in the the Autoloader for example (will be a separate patch, when this one is done).<br />Also Extbase can make use of these functions to resolve #40742.</p> TYPO3 Core - Bug #40673 (Closed): sysexts cli and integrity have no ext_emconf.phphttp://forge.typo3.org/issues/406732012-09-06T14:05:27ZSebastian Michaelsenmichaelsen@t3seo.de
<p>There are two new sysext folders which have no ext_emconf.php and therefore do not appear in the EM: cli and integrity</p>
<p>Is this by intention?</p> TYPO3 Core - Feature #36669 (Closed): Add Hook to manipulate BE login formhttp://forge.typo3.org/issues/366692012-04-27T16:28:05ZSebastian Michaelsenmichaelsen@t3seo.de
<p>With TYPO3 4.7 the old deprecated way of defining Login News ($TYPO3_CONF_VARS['BE']['loginNews']) was removed and the sys_news database table is the only source for login news now.<br />But you may want to add items from another source (e.g. RSS-Feed).</p>
<p>This is why I want to implement a hook to manipulate the Login News Records.</p> TYPO3 Core - Feature #34922 (Closed): Allow .ts file extension for static typoscript templateshttp://forge.typo3.org/issues/349222012-03-16T12:15:45ZSebastian Michaelsenmichaelsen@t3seo.de
<p>At the moment the following static typoscript filenames are allowed:</p>
<p>setup.txt<br />constants.txt<br />include_static.txt<br />include_static_files.txt</p>
<p>My intention is to also allow ".ts" as file extensions because they're commonly used and IDEs can recognize those file as TypoScript.</p>
<p>I was already playing around with the code and what makes me worry is performance. It's quite expensive to check all the allowed filenames and read them.</p>
<p>I benchmarked different situations (folder with only .txt / only .ts / both / none) and in average it slows down the reading of static templates by about 48%. I don't know if this is acceptable in change for the convenience you get.<br />Maybe there's a possibility for a smart caching solution or other ideas on improving the performance. Ideas are welcome.</p>
<p>I will add my best effort patch here shortly.</p> TYPO3 Core - Bug #30406 (Closed): TCA: Fields with eval md5 can not be clearedhttp://forge.typo3.org/issues/304062011-09-29T08:41:29ZSebastian Michaelsenmichaelsen@t3seo.de
<p>Try this: Open a Backend User record and try to use the little 'x' to clear the password field. The field is not cleared.</p>
<p>I pinned it down to the 'eval' => 'md5' configuration. Any fields with this md5-option (most likely password fields) will produce this error.</p> TYPO3 Core - Bug #24336 (Closed): <img> Tags are rendered with border attribute in HTML5 modehttp://forge.typo3.org/issues/243362010-12-14T12:13:54ZSebastian Michaelsenmichaelsen@t3seo.de
<p>By default <img> Tags are rendered with a border attribute in HTML5. Only with XHTML they are omitted.<br />This is a bug. in HTML5 the border attribute is not allowed.</p>
<p>You can disable the border attribute by using config.disableImgBorderAttr = 1, but it should be disabled by default when using html5 to produce valid code.<br />(issue imported from #M16740)</p> TYPO3 Core - Bug #22340 (Closed): Automatically hiding Option Checkboxes and search fields on "em...http://forge.typo3.org/issues/223402010-03-29T13:54:44ZSebastian Michaelsenmichaelsen@t3seo.de
<p>When you open a page in list view which has no records to display, it still shows up Checkboxes for "Extended View" and "Localization view" and a search form.<br />The functionality to hide these automatically is implemented but does not work anymore.</p>
<p>After computing the list of tables the list module checks if it has any output. If it's empty Checkboxes and searchform are hidden.</p>
<p>The problem ist that the "list of tables" output is never empty because t3lib_recordlist::writeBottom adds some Hardcoded HTML to the bottom of the table list.</p>
<p>Additionally note that rendering of the clipboard is inside the mentioned condition, so when no records are there the clipboard would also be hidden (you don't want that because you may want to paste records into an empty page). So the Clipboard rendering needs to be moved outside the if-statement<br />(issue imported from #M13942)</p> TYPO3 Core - Feature #22279 (Closed): Add .numberFormat function to stdWraphttp://forge.typo3.org/issues/222792010-03-15T11:49:49ZSebastian Michaelsenmichaelsen@t3seo.de
<p>When handling prices or other special formated Numbers in TypoScript there's no reasonable way to format it properly. When there's a price like 0.8 in your Database you can't transform it to 0,80 easily.</p>
<p>There's already an extension adding this functionality by XCLASSing (am_stdwrap_number_format) and requests for such a feature (<a class="external" href="http://www.typo3.net/forum/list/list_post//89143/">http://www.typo3.net/forum/list/list_post//89143/</a> [german]), so I think a general interest for this functionality is given.<br />(issue imported from #M13815)</p> TYPO3 Core - Feature #22107 (Closed): Add a Hook to add Sub Categories to the Constant Editorhttp://forge.typo3.org/issues/221072010-02-11T10:42:37ZSebastian Michaelsenmichaelsen@t3seo.de
<p>Currently the Sub Categories of the Constant Editor are hardcoded (Enable Features, Dimensions, etc).<br />Especially when you develop a flexible TypoScript Library which should be configurable with the Constant Editor it would be great if you could add custom Sub Categories.</p>
<p>I added a constructor to t3lib_tsparser_ext, which can also be used for other hooks or initialization stuff. Currently it only includes my Hook (callUserFunction) to add Sub Categories.<br />(issue imported from #M13510)</p>