TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692013-01-30T13:53:48ZTYPO3 Forge
Redmine 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 #44963 (Closed): Create CSS Styled Content TypoScript configuration for v6.0http://forge.typo3.org/issues/449632013-01-30T13:10:17ZSebastian Michaelsenmichaelsen@t3seo.de
<p>For backwards compatibility we keep versions of the CSS Styled Content<br />TypoScript configuration files of previous versions selectable as rendering template.</p> TYPO3 Core - Bug #44781 (Closed): ConfigurationUtility->getCurrentConfiguration only delivers def...http://forge.typo3.org/issues/447812013-01-24T11:56:56ZSebastian Michaelsenmichaelsen@t3seo.de
<p>TYPO3\CMS\Extensionmanager\Utility\ConfigurationUtility has a nice handy function getCurrentConfiguration($extensionKey), which tries to load the default configuration and overlay it with the current configuration. But due to an error it will always output the default configuration.</p>
<p>Using GeneralUtility::array_merge_recursive_overrule $defaultConfig should be overlayed with $currentExtensionConfig. The problem is that the two arrays have different formats.</p>
<p>$defaultConfig contains the array with information parsed from the typoscript (style) comments, the default values are nested in these informations.<br />$currentExtensionConfig contains a pure key value store for the configuration.<br />Also see the attached screenshot to see how the two array don't fit together.</p>
<p>I don't really know how to solve this properly. I would love to have a Utility Function that just returns a key value array, but at the moment the function returns the more verbose array. We can't really change this anymore, since this is public API isn't it?</p>
<p>There are two spots in the core at the moment that use this method, that could be adjusted, but there might already be 3rd party implementations using it.</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 #44630 (Closed): StorageRepository doesn't respect 'deleted' flaghttp://forge.typo3.org/issues/446302013-01-18T11:40:59ZSebastian Michaelsenmichaelsen@t3seo.de
<p>The FAL's Storage Repository find* methods also load deleted file storages.</p>
Reproduce:
<ul>
<li>Create some "File Storage" records on the root page and delete some of them</li>
<li>Open the File module, it will show also deleted File Storages</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 - Bug #40672 (Closed): Including DatabaseUtility fails due to Null Characterhttp://forge.typo3.org/issues/406722012-09-06T13:41:28ZSebastian Michaelsenmichaelsen@t3seo.de
<p>(This one is strange and it took me a while to figure it out)</p>
<p>In typo3/sysext/extensionmanager/Classes/Utility/DatabaseUtility.php line 129, position 38 there seems to be a so called Null Character<sup><a href="#fn1">1</a></sup> which raises an error when the file is included. In my case the whole PHP process seems to be killed - the browser receives no response from the server. This way the EM and the Language module fail to load.</p>
<p>I found the problem via Command Line:</p>
<p>$ php -l DatabaseUtility.php <br />Bus error: 10</p>
<p>When I erase the Null character everything works fine.</p>
<p>Attention: I'm experiencing this on a Mac with Intel chip. This smells system dependant to me.</p>
<p>(I can't even provide a patch because git seems to handle DatabaseUtility.php as a binary file because of the Null character)</p>
<p>[1] <a class="external" href="http://en.wikipedia.org/wiki/Null_character">http://en.wikipedia.org/wiki/Null_character</a></p> TYPO3 Core - Bug #40665 (Closed): CSH Manual Popup brokenhttp://forge.typo3.org/issues/406652012-09-06T09:30:30ZSebastian Michaelsenmichaelsen@t3seo.de
<p>The popup that appears when you click a CSH helptext raises an exception.</p>
<p>Reproduce: Click on any helptext, e.g. the one appearing at the question mark in the top row of the list module.</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 #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>