TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692013-03-24T02:56:06ZTYPO3 Forge
Redmine TYPO3 Core - Feature #46617 (Closed): Provide flushing cache by table and record tagshttp://forge.typo3.org/issues/466172013-03-24T02:56:06ZNicole Cordestypo3@cordes.co
<p>As suggested in the wiki it is helpful to tag caches with a combination of table and record uid to get the cache deleted when the specific record was edited. But rather that each extension provides its own implementation it would be better to store this simple function into the core.</p> TYPO3 Core - Bug #43043 (Closed): Remove empty brackets when configuration type is emptyhttp://forge.typo3.org/issues/430432012-11-17T01:27:37ZNicole Cordestypo3@cordes.co
<p>When applying patch <a class="external" href="http://forge.typo3.org/issues/43042">http://forge.typo3.org/issues/43042</a> for unknown configuration types empty brackets are shown behind the input field. These could be dropped.</p> TYPO3 Core - Bug #43042 (Closed): Default behaviour for configuration is droppedhttp://forge.typo3.org/issues/430422012-11-17T01:09:46ZNicole Cordestypo3@cordes.co
<p>In TYPO3 4.7 (and below) the default field of a configuration was a text field. With a wrong configuration type in ext_conf_template.txt now the field isn't rendered any more. There should be any fallback like it used to.</p>
<p>Affected extension for example current master of PhpUnit extensions (I'll investigate in this) but IMHO the default shouldn't be dropped without any notice.</p> TYPO3 Core - Bug #43041 (Closed): Extension Manager doesn't care about Configuration sortinghttp://forge.typo3.org/issues/430412012-11-17T00:41:10ZNicole Cordestypo3@cordes.co
<p>When showing the configuration of an extension actually the Extension Manager doesn't care about the given sorting.</p>
<p>E.g. configuration:</p>
<ol>
<li>cat=basic/enable/10; type=boolean; label=First configuration option<br />firstOption = 1</li>
</ol>
<ol>
<li>cat=basic/enable/20; type=int; label=Second option<br />secondOption = 999</li>
</ol>
<p>The sorting is the other way around because configuration is just merged.</p> TYPO3 Core - Bug #42655 (Closed): Missing pid field in ext_tables_static+adt.sqlhttp://forge.typo3.org/issues/426552012-11-02T22:20:39ZNicole Cordestypo3@cordes.co
<p>In the ext_tables.sql there is a pid field which is left in the ext_tables_static+adt.sql file. This causes unnecessary ALTER queries in database comparison.</p> TYPO3 Core - Task #42613 (Closed): Cleanup update wizard configurationhttp://forge.typo3.org/issues/426132012-11-02T02:15:10ZNicole Cordestypo3@cordes.co
<p>There are still some old tx_ classes in the update wizard configuration which should be replaced with their namespaced versions. Then those classes which were introduced with 6.0 could be deleted from the class mapping list.</p> TYPO3 Core - Bug #42574 (Closed): Updating introduction package failshttp://forge.typo3.org/issues/425742012-10-31T22:36:15ZNicole Cordestypo3@cordes.co
<p>Updating the current introduction package fails due to hardcoded t3lib_div call in localconf.php. This class was removed and new name is \TYPO3\CMS\Core\Utility\GeneralUtility</p>
<pre>
$TYPO3_CONF_VARS['FE']['pageNotFound_handling'] = t3lib_div::getIndpEnv('TYPO3_SITE_URL').'index.php?id=16';
</pre>
<p>We need to set class_alias in bootstrap where the GeneralUtility class gets loaded.</p> TYPO3 Core - Task #42237 (Closed): Add information about ThreadStackSize to install toolhttp://forge.typo3.org/issues/422372012-10-21T00:46:18ZNicole Cordestypo3@cordes.co
<p>There is an information about the ThreadStackSize on Windows systems in the Install.txt.</p>
<p>This information should be displayed in the Basic Configuration of the Install Tool as well.</p> TYPO3 Core - Bug #42235 (Closed): Add information about ThreadStackSize to report statushttp://forge.typo3.org/issues/422352012-10-20T23:51:40ZNicole Cordestypo3@cordes.co
<p>There is an information about the ThreadStackSize on Windows systems in the Install.txt</p>
<p>This information should be displayed in report status as well</p> TYPO3 Core - Bug #41223 (Closed): Deleted processed files are not re-renderedhttp://forge.typo3.org/issues/412232012-09-21T23:43:29ZNicole Cordestypo3@cordes.co
<p>The rendering process (e.g. for images) are saved in an own table "sys_file_processedfile". Everytime a file is going to be processed the data is taken from the table without checking if the file still exists. This breaks for example preview images in backend module.</p> TYPO3 Core - Bug #41204 (Closed): Preview images not rendered in Web > Page view on Windows systemshttp://forge.typo3.org/issues/412042012-09-21T21:24:42ZNicole Cordestypo3@cordes.co
<p>In Web > Page view the preview images are not rendered on Windows systems. Is is due to failing functions in class TYPO3\CMS\Core\Utility\PathUtility. Basically it's an issue with forward and backward slashes. In the class the constance DIRECTORY_SEPARATOR is used which is on Windows systems a backward slash. Normally paths in TYPO3 are converted to use forward slashes and here is the existing problem.</p> TYPO3 Core - Bug #41182 (Closed): Driver cannot be savedhttp://forge.typo3.org/issues/411822012-09-21T16:45:49ZNicole Cordestypo3@cordes.co
<p>Because of a false call on setLocalConfigurationValuesByPathValuePairs the driver config cannot be set. The function</p> TYPO3 Core - Bug #41158 (Closed): Error messages are not shown in 123 installation processhttp://forge.typo3.org/issues/411582012-09-21T12:03:13ZNicole Cordestypo3@cordes.co
<p>Because of a missing ERRORMESSAGES subpart in the 123 install template, error messages collected while processing are not shown in the frontend.</p> TYPO3 Core - Task #41151 (Closed): Improve error message for failling database creationhttp://forge.typo3.org/issues/411512012-09-21T10:56:03ZNicole Cordestypo3@cordes.co
<p>Due to compatibility (maybe?) the create database command can't use quotes for new database names. Therefore (at least for MySQL databases) the characters to use is limited to 0-9, a-z, A-Z, $, _</p>
<p>This should be mentioned when creating the database fails.</p> TYPO3 Core - Bug #40843 (Closed): Fatal error is thrown when more drivers are registeredhttp://forge.typo3.org/issues/408432012-09-12T00:11:49ZNicole Cordestypo3@cordes.co
<p>When multiple drivers are loaded due to extension manager processes the ext_localconf.php's are loaded twice. This leads to exception #1314979451. Instead of checking only the short name of a driver the DriveRegistry should check the class name as well.</p>