TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-07-13T11:47:17ZTYPO3 Forge
Redmine TYPO3 Core - Task #94553 (Closed): Enforce trailing commas in multi line arrays with PHP CS Fixerhttp://forge.typo3.org/issues/945532021-07-13T11:47:17ZSebastian Michaelsenmichaelsen@t3seo.de
<p>The PHP CS Fixer rule <code> trailing_comma_in_multiline => ['arrays']</code> ensures that multi line arrays always have a trailing comma.</p>
<pre><code class="php syntaxhl" data-language="php"><span class="nv">$array</span> <span class="o">=</span> <span class="p">[</span>
<span class="s1">'one'</span><span class="p">,</span>
<span class="s1">'two'</span>
<span class="p">];</span>
</code></pre>
<p>becomes</p>
<pre><code class="php syntaxhl" data-language="php"><span class="nv">$array</span> <span class="o">=</span> <span class="p">[</span>
<span class="s1">'one'</span><span class="p">,</span>
<span class="s1">'two'</span><span class="p">,</span>
<span class="p">];</span>
</code></pre>
<p>Having trailing commas makes it easier to rearrange entries and when an entry is added to the list the line before doesn't need to be changed. This results in smaller git changes for a better overview and less likely merge conflicts.</p> TYPO3 Core - Task #92971 (Closed): Don't try to create language switch for non-persisted recordshttp://forge.typo3.org/issues/929712020-12-01T14:57:31ZSebastian Michaelsenmichaelsen@t3seo.de
<p><code>EditDocumentController->languageSwitch()</code> generates the language dropdown menu in the backend record edit form.</p>
<p>When creating a new record, the result is always that no dropdown form is displayed.</p>
<p>However also for new records the function performs DB queries and runs a lot of code. Instead it should not be called in this case.</p> TYPO3 Core - Task #90237 (Closed): Show property path on hover in Template Tree Viewhttp://forge.typo3.org/issues/902372020-01-29T07:58:21ZSebastian Michaelsenmichaelsen@t3seo.de
<p>This is about the tree view that is used for TypoScript constants/setup in the Template module and also the Page TSconfig view in the info module.</p>
<p>Especially in Page TSconfig (where all nodes are always expanded) for deeply nested properties it's often not so easy to find out the whole path of a property. It can involve a lot of scrolling and sticking fingers to your screen to keep track of the indention.</p>
<p>So I suggest to put the whole property path in the title-Attribute of the property name, so it can easily be seen by hovering over it.</p> TYPO3 Core - Task #69381 (Rejected): Move the images field of the images CE to the first form tabhttp://forge.typo3.org/issues/693812015-08-28T08:50:19ZSebastian Michaelsenmichaelsen@t3seo.de
<p>Historically the images of the images content element were always configured in the second tab.<br />Back in the times before FAL this might have been a good idea, because there were many fields that would have cluttered the first view on the record.</p>
<p>Now with FAL and the image config details hidden the collapsed inline records it's time to move the images to the first tab. In fact they are the most important property of the record and should be directly visible.</p> TYPO3 Core - Task #68358 (Closed): Cleanups for PageRepositoryhttp://forge.typo3.org/issues/683582015-07-18T19:50:49ZSebastian Michaelsenmichaelsen@t3seo.de
<p>I want to do some cleanups in PageRepository before finishing <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Enable working with SysFolders in CONTENT (Closed)" href="http://forge.typo3.org/issues/20933">#20933</a></p> TYPO3 Core - Task #68329 (Closed): Use ::class where possible in fluid unit testshttp://forge.typo3.org/issues/683292015-07-18T10:36:04ZSebastian Michaelsenmichaelsen@t3seo.deTYPO3 Core - Task #68326 (Closed): Use "an" instead of "a" in labels and comments where appropriatehttp://forge.typo3.org/issues/683262015-07-18T02:18:17ZSebastian Michaelsenmichaelsen@t3seo.de
<p>In english you have to use "an" before any spoken vowel.</p> TYPO3 Core - Task #63327 (Closed): Use class imports in Cache Frontend classeshttp://forge.typo3.org/issues/633272014-11-25T21:37:39ZSebastian Michaelsenmichaelsen@t3seo.deTYPO3 Core - Task #63326 (Closed): Avoid using $GLOBALS['TYPO3_DB'] in DataHandlerhttp://forge.typo3.org/issues/633262014-11-25T16:38:46ZSebastian Michaelsenmichaelsen@t3seo.de
<p>Instead of $GLOBALS['TYPO3_DB'] a type hinted property $this->databaseConnection should be used to gain autocompletion and better IDE inspection in this class.</p>
<p>Concerns: This might be a breaking change. $this->databaseConnection is set on DataHandler->start(). If some code relies on setting/modifying $GLOBALS['TYPO3_DB'] <strong>after</strong> DataHandler->start() and <strong>before</strong> other methods of DataHandler are invoked it might break. Please decide if this is too much of a risk.</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 - 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 - 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>