TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692012-07-19T12:59:20ZTYPO3 Forge
Redmine TYPO3 Core - Feature #39081 (Closed): Disable Upload form in TCA form globalyhttp://forge.typo3.org/issues/390812012-07-19T12:59:20ZDominique Feyerdfeyer@ttree.ch
<p>Currently to disable to form upload in TCA form we must use the disable_controls key in the config array. On some TYPO3 installation it's part of the project guidline, that the user must upload files to fileadmin, before using them.</p>
<p>Disabling upload control, for each field is error prone. So a global User TSConfig can be a good idea</p>
<pre>
options.disableUploadControlInTcaForm = 1
</pre> TYPO3 Core - Task #39060 (Closed): Better use of sanitizeLocalUrl in db listhttp://forge.typo3.org/issues/390602012-07-18T15:49:33ZDominique Feyerdfeyer@ttree.ch
<p>db list use sanitizeLocalUrl, at line 192 (4.7), like this:</p>
<pre>
if (t3lib_div::sanitizeLocalUrl(t3lib_div::_GP('returnUrl'))) {
$location = t3lib_div::sanitizeLocalUrl(t3lib_div::_GP('returnUrl'));
t3lib_utility_Http::redirect($location);
}
</pre>
<p>A no brainer improvement is possible ;)</p> TYPO3 Core - Feature #39051 (Closed): Add support for page module, to automatic redirect to list ...http://forge.typo3.org/issues/390512012-07-18T11:39:38ZDominique Feyerdfeyer@ttree.ch
<p>When the user select a sysfolder in the page module, currently the BE just display a link to the list module.</p>
<p>With a new option flag, the backend can redirect to the list module automaticaly, with a proper flashmessage in the list module to explain the user, why they have been redirected.</p> TYPO3 Core - Feature #39046 (Closed): TCA tree must support custom widthhttp://forge.typo3.org/issues/390462012-07-18T01:21:13ZDominique Feyerdfeyer@ttree.ch
<p>Currently it's not possible to change the default width of the TCA form tree.</p> TYPO3 Core - Bug #39035 (Closed): TCA tree fail to load with IRREhttp://forge.typo3.org/issues/390352012-07-17T17:16:16ZDominique Feyerdfeyer@ttree.ch
<p>The TCA tree element fail to load inside IRRE, in some condition (when the record is not loaded/opened)</p> TYPO3 Core - Bug #34886 (Closed): t3lib_cache_backend_FileBackend don't support 0 has liftimehttp://forge.typo3.org/issues/348862012-03-15T16:01:02ZDominique Feyerdfeyer@ttree.ch
<p>In the DB backend 0 has liftime mean "unlimited" lifetime for the cache entry, but in the file backend it's give a always invalid cache entry.</p>
<p>Patch is coming</p> TYPO3 Core - Bug #32600 (Closed): Add clear l10n cache when the user clear all cachehttp://forge.typo3.org/issues/326002011-12-15T15:46:14ZDominique Feyerdfeyer@ttree.ch
<p>Currently the l10n parser cache can only be cleared manually, by adding this in locallang.php:</p>
<p>$GLOBALS['TYPO3_CONF_VARS']['SYS']['lang']['cache']['clear_menu'] = TRUE;</p>
<p>This patch change the default behavior. By default the l10n cache is cleared on "clear all cache", if the clear l10n menu item is enabled, it's not cleared on clear all cache.</p> TYPO3 Core - Bug #32578 (Closed): Update links to documentation in language labelshttp://forge.typo3.org/issues/325782011-12-15T01:16:59ZDominique Feyerdfeyer@ttree.ch
<p>In file lang/locallang_csh_corebe.xlf there is the label "_menu_modules.seeAlso". It contains a link to typo3.org, which is wrong.</p>
<p>The correct link is:<br /><a class="external" href="http://docs.typo3.org/typo3cms/GettingStartedTutorial/GeneralPrinciples/Index.html">http://docs.typo3.org/typo3cms/GettingStartedTutorial/GeneralPrinciples/Index.html</a></p> TYPO3 Core - Bug #30917 (Closed): Remove english projecthttp://forge.typo3.org/issues/309172011-10-14T10:22:38ZDominique Feyerdfeyer@ttree.ch
<p>English is the default language in TYPO3, so we don't need english project in Pootle. We need to rename "en" projects to "templates"</p> TYPO3 Core - Task #30916 (Closed): Transform the current en->en XLIFF file to template filehttp://forge.typo3.org/issues/309162011-10-14T10:21:34ZDominique Feyerdfeyer@ttree.ch
<p>We have a design problem actually, the english XLIFF is actualy a "en" to "en" translation file. We need to change this. English file must just be a template (as this is the default language). So we need to remove the target element from this file.</p> TYPO3 Core - Bug #28086 (Closed): Disable clear lang cache by defaulthttp://forge.typo3.org/issues/280862011-07-11T11:21:55ZDominique Feyerdfeyer@ttree.ch
<p>By default the clear lang cache must not be enabled.</p>
<p>You can enable it if needed with this configuration, in localconf.php:</p>
<p>$GLOBALS['TYPO3_CONF_VARS']['SYS']['lang']['cache']['clear_menu'] = TRUE;</p> TYPO3 Core - Bug #27972 (Closed): LLXML Parser does not support localized label in the main LLXMLhttp://forge.typo3.org/issues/279722011-07-08T10:00:36ZDominique Feyerdfeyer@ttree.ch
<p>Many extension use the main LLXML file to provide default language and<br />others languages (fr, de, ...). The parser must support that.</p>
<p>This patch add this support. The priority is always given to the<br />language pack found in typo3conf/l10n. If a language pack is found<br />the localized label in the main LLXML file are not parsed.</p> TYPO3 Core - Task #27416 (Closed): Fix localization handling to support XLIFFhttp://forge.typo3.org/issues/274162011-06-13T23:57:51ZDominique Feyerdfeyer@ttree.ch
<p>Due to the change in localization handling within Core, Extbase must be updated.</p>
<p>See <a class="issue tracker-2 status-5 priority-4 priority-default closed parent" title="Feature: Adding XLIFF support as the default format for translation (Closed)" href="http://forge.typo3.org/issues/25397">#25397</a></p> TYPO3 Core - Feature #25397 (Closed): Adding XLIFF support as the default format for translationhttp://forge.typo3.org/issues/253972011-03-25T18:43:04ZDominique Feyerdfeyer@ttree.ch
<p>The goal of the project is to extend TYPO3 translation format support with XLIFF format.</p>
<p>This move is motivated by the lack of good tools to translate TYPO3. Translation team need advanced feature to manage their workload and improve TYPO3 translation quality. Actually we are impressed by the features of Pootle (use by LibreOffice, Mozilla, Gnome, ...) and plan to use it as a replacement of llxmltranslate.</p>
<p>We are actually working in the TYPO3 core, on github. The current job is to move the existing feature to dedicated class (parsing llxml, llphp, ...) and adding a sort of factory to switch between the correct parser.<br /><a class="external" href="https://github.com/dfeyer/git.typo3.org">https://github.com/dfeyer/git.typo3.org</a></p>
<p>You can check our test Pootle server here:<br /><a class="external" href="https://pootle.reelpeek.net/pootle/">https://pootle.reelpeek.net/pootle/</a></p>
<p>And a quick and dirty tools to convert core llxml to XLIFF:<br /><a class="external" href="https://github.com/dfeyer/llxml2xliff">https://github.com/dfeyer/llxml2xliff</a></p>
<p>(issue imported from #M18040)</p> TYPO3 Core - Feature #25046 (Closed): Allow the usage of t3lib_befunc::getProcessedValue() in the...http://forge.typo3.org/issues/250462011-02-15T16:34:25ZDominique Feyerdfeyer@ttree.ch
<p>The separation between BE and FE is sometime a big issue in some projet. I supply a little patch to allow the use of t3lib_befunc::getProcessedValue() in a frontend extension. The idea is not to port all the BE API to the FE, but a coding a copy of getProcessedValue in FE it's not a good option.</p>
<p>The proposed patch simply add a proxy method t3lib_befunc::sL to switch between $LANG->sL and $TSFE->sL depending on TYPO3_MODE</p>
<p>(issue imported from #M17601)</p>