TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692013-03-20T13:18:21ZTYPO3 Forge
Redmine 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 #44965 (Closed): Cleanups for CSS Styled Contenthttp://forge.typo3.org/issues/449652013-01-30T13:53:48ZSebastian Michaelsenmichaelsen@t3seo.de
<ul>
<li>Remove "@todo Define visibility" annotations from the render_* methods. They are called from TS, they need to be public.</li>
<li>Remove unused variables from the CssStyledContentController</li>
<li>Don't pass the constants borderColor and rowSpace to tt_content.image any more, they are not used there.</li>
</ul> 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 #44537 (Closed): BackendUtility::displayWarningMessages uses wrong returnUrlhttp://forge.typo3.org/issues/445372013-01-15T14:26:18ZSebastian Michaelsenmichaelsen@t3seo.de
Steps to reproduce:
<ul>
<li>create a user with the following credentials: admin/password (you're encouraged not to do so on a live system ;) )</li>
<li>open the "About Modules" module, which shows a warning about the admin user.</li>
<li>click the link to edit the admin user</li>
<li>close or save/close the form</li>
<li>404</li>
</ul> TYPO3 Core - Task #44527 (Closed): Cleanup EXT:lang FormEngineBasedCheckboxGroupViewHelperhttp://forge.typo3.org/issues/445272013-01-15T11:03:24ZSebastian Michaelsenmichaelsen@t3seo.de
<ul>
<li>namespaces in type annotations have to start with a backslash \</li>
<li>remove unused variable $items in render method</li>
</ul> TYPO3 Core - Task #44526 (Closed): Use property injection in TYPO3\CMS\Lang\Controller\LnaguageCo...http://forge.typo3.org/issues/445262013-01-15T10:01:58ZSebastian Michaelsenmichaelsen@t3seo.de
<p>The LanguageController has 4 inject* Methods which a pretty vanilla and can be replaced by property injection.</p> TYPO3 Core - Task #44506 (Closed): Remove references to old-style Login News (TYPO3_CONF_VARS)http://forge.typo3.org/issues/445062013-01-14T12:12:48ZSebastian Michaelsenmichaelsen@t3seo.de
<p>Adding Login News via $GLOBALS['TYPO3_CONF_VARS']['BE']['loginNews'] is not longer supported but there are still references to it in the code that should be removed.</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 - Bug #35762 (Closed): Edit Link in Backend Live Search doesn't workhttp://forge.typo3.org/issues/357622012-04-07T09:32:07ZSebastian Michaelsenmichaelsen@t3seo.de
<p>Reproduce:</p>
<p>- Start a search in the backend with the live search in the upper right corner.<br />- Click on one of the search results<br />- The edit view will open but will close immediately and jump back to where you came from</p>
<p>Can anyone confirm this? I can reproduce this on 2 independent TYPO3 (4.6.7) installations.</p>
<p>I could not find the error on the code or a possible solution yet.</p> TYPO3 Core - Task #34559 (Closed): Fix wrong cObject name in comment (CLEAR_REGISTER => RESTORE_R...http://forge.typo3.org/issues/345592012-03-06T14:01:28ZSebastian Michaelsenmichaelsen@t3seo.de
<p>In the comment explaining tslib_fe->registerStack there's a reference to CLEAR_REGISTER (doesn't exist). It should be RESTORE_REGISTER.</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 #28050 (Closed): t3lib_div::devLog - PHPDoc Comment does not match method signaturehttp://forge.typo3.org/issues/280502011-07-09T20:12:04ZSebastian Michaelsenmichaelsen@t3seo.de
<p>This is the signature of t3lib_div::devLog<br /><pre>
/**
* Logs message to the development log.
* This should be implemented around the source code, both frontend and backend, logging everything from the flow through an application, messages, results from comparisons to fatal errors.
* The result is meant to make sense to developers during development or debugging of a site.
* The idea is that this function is only a wrapper for external extensions which can set a hook which will be allowed to handle the logging of the information to any format they might wish and with any kind of filter they would like.
* If you want to implement the devLog in your applications, simply add lines like:
* if (TYPO3_DLOG) t3lib_div::devLog('[write message in english here]', 'extension key');
*
* @param string Message (in english).
* @param string Extension key (from which extension you are calling the log)
* @param integer Severity: 0 is info, 1 is notice, 2 is warning, 3 is fatal error, -1 is "OK" message
* @param array Additional data you want to pass to the logger.
* @return void
*/
public static function devLog($msg, $extKey, $severity = 0, $dataVar = FALSE) {
}
</pre></p>
<p>Notice that the last Parameter is declared as array, but defaults to FALSE. This leads to warning notices in IDEs like PHPStorm when you use devLog.</p>