TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-11-03T14:20:44ZTYPO3 Forge
Redmine TYPO3 Core - Bug #102313 (Under Review): Allow change of metadata if file is deletedhttp://forge.typo3.org/issues/1023132023-11-03T14:20:44ZSimon SchaufelbergerTYPO3 Core - Bug #97845 (Closed): Add missing "throw" in deprecation resthttp://forge.typo3.org/issues/978452022-07-02T22:09:09ZSimon SchaufelbergerTYPO3 Core - Bug #94998 (Closed): Add missing autocomplete for TOTP fieldhttp://forge.typo3.org/issues/949982021-08-25T22:44:41ZSimon Schaufelberger
<p>While the authentication form has an autocomplete value of "one-time-code", it is missing in the setup template.</p> TYPO3 Core - Bug #93207 (Closed): Duplicate error message in AjaxDataHandler.tshttp://forge.typo3.org/issues/932072021-01-02T22:34:39ZSimon Schaufelberger
<p>I noticed that handleErrors is called twice in Build/Sources/TypeScript/backend/Resources/Public/TypeScript/AjaxDataHandler.ts.</p>
<p>Once in AjaxDataHandler->initialize and again in AjaxDataHandler->process.</p>
<p>One of both should be removed. I believe removing the one in initialize makes more sense as the one in process will also get called when deleting a record.</p>
<p>How to reproduce:</p>
<p>Put these lines in \TYPO3\CMS\Backend\Controller\SimpleDataHandlerController::processAjaxRequest after "$this->tce->printLogErrorMessages();" to force an error flash message:</p>
<pre><code class="php syntaxhl" data-language="php"> <span class="nv">$flashMessageService</span><span class="o">-></span><span class="nf">getMessageQueueByIdentifier</span><span class="p">()</span><span class="o">-></span><span class="nf">addMessage</span><span class="p">(</span><span class="nc">GeneralUtility</span><span class="o">::</span><span class="nf">makeInstance</span><span class="p">(</span>
<span class="nc">\TYPO3\CMS\Core\Messaging\FlashMessage</span><span class="o">::</span><span class="n">class</span><span class="p">,</span>
<span class="s1">'Duplicate error message!'</span><span class="p">,</span>
<span class="s1">'Duplicate error message title'</span><span class="p">,</span>
<span class="nc">\TYPO3\CMS\Core\Messaging\FlashMessage</span><span class="o">::</span><span class="no">ERROR</span>
<span class="p">));</span>
</code></pre> TYPO3 Core - Feature #66525 (Closed): IconUtility->skinImg source does not allow EXT prefixhttp://forge.typo3.org/issues/665252015-04-21T22:35:24ZSimon Schaufelberger
<p>pageTSConfig:</p>
<p>wizardItems.[group].elements.[name].icon is defined as image resource. It is possible to either set it via PHP like here: <a class="external" href="http://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/Examples/ContentElementWizard/Index.html">http://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/Examples/ContentElementWizard/Index.html</a> with ExtensionManagementUtility::extRelPath or make the path relative with ../../typo3conf/ext/myextension but using EXT:myextension is not working.</p>
<p>Example which <strong>should</strong> work:</p>
<pre>
mod.wizards {
newContentElement.wizardItems {
special {
elements {
worldmap {
icon = EXT:contentelements/Resources/Public/Images/worldmap.gif
...
}
}
show = *
}
}
}
</pre> TYPO3 Core - Bug #44732 (Closed): fallbackRendering is always called in tx_cssstyledcontent_pi1->...http://forge.typo3.org/issues/447322013-01-22T23:23:29ZSimon Schaufelberger
<p>fallbackRendering is always called in tx_cssstyledcontent_pi1->render_textpic which is not always defined and leads to an error message (seen in TimeTrack Log):<br /><pre>
Content Object "" does not exist
</pre></p> TYPO3 Core - Bug #41050 (Closed): core itself calls deprecated method deprecationLogForOldExtCach...http://forge.typo3.org/issues/410502012-09-18T20:36:13ZSimon Schaufelberger
<p>see:<br />typo3\sysext\cms\tslib\index_ts.php</p>
<p>line 65</p>
<p>... and fills the deprecation log which the core itself should NOT do.</p> TYPO3 Core - Feature #32964 (Rejected): Check for not existing static templates before removing themhttp://forge.typo3.org/issues/329642012-01-04T13:46:22ZSimon Schaufelberger
<p>Often times there is the problem that a team works together on a project and another person jumps in. Now he checks out the main repository but does not have all submodules. He changes the index typoscript template where all static templates from the extensions are included and since he does not have all of them locally, he removed some without any notice. Then the project is broken.</p>
<p>Before saving the typoscript template, there should be a check if the static templates in the list do really exist and if not, a flash message should be shown that a static template has been removed.</p>
<p>This does affect ALL TYPO3 versions of course and should be backported until 4.5!!!</p> TYPO3 Core - Bug #32960 (Closed): Filter for page alias does not work in pagetreehttp://forge.typo3.org/issues/329602012-01-04T11:01:07ZSimon Schaufelberger
<p>When i search/filter in the page tree for an alias, i don't get any results. Search only works with id and page title.</p> TYPO3 Core - Bug #30259 (Closed): List view not loading data on pid 0 after switch from page modulhttp://forge.typo3.org/issues/302592011-09-24T18:07:15ZSimon Schaufelberger
<p>After i logged into TYPO3, i am going to the page modul and select the pid 0 in the page tree. On the main frame i now see the message:<br />"Please click the page title in the page tree to the left to edit page content." <br />which is ok.<br />I now switch to the list modul and expect to see all the data on pid 0 but i see nothing (empty right frame).</p>
<p>This is only reproduceable if you switch from the page modul to the list modul. If you go straight to the list modul, i see the data on pid 0.</p>
<p>You can even go to the list modul (see the data), then to the page modul (see the message in the box) and back to the list modul and you will see nothing again.</p>
<p>This happens in latest trunk of TYPO3 4.6 as well in older versions, maybe even until TYPO3 4.3</p>
<p>In TYPO3 4.2 it was working.</p> TYPO3 Core - Feature #29168 (Closed): Enable constants in conditions in TypoScript templateshttp://forge.typo3.org/issues/291682011-08-22T18:05:59ZSimon Schaufelberger
<p>Right now, it is not possible to write something like this:</p>
<pre>
[PIDinRootline = LIT:{$tsconstant}]
# ...
[end]
</pre>
<p>Changing the check to:<br /><pre>
case 'PIDinRootline':
$value = $this->getVariable(trim($value));
$values = t3lib_div::trimExplode(',', $value, TRUE);
if (($key == 'PIDinRootline') || (!in_array($this->pageId, $values))) {
foreach ($values as $test) {
foreach ($this->rootline as $rl_dat) {
if ($rl_dat['uid'] == $test) {
return TRUE;
}
}
}
}
</pre><br />would solve that problem in t3lib/matchcondition/class.t3lib_matchcondition_frontend.php just for this case. of course this could be changed in other conditions as well.</p> TYPO3 Core - Bug #25962 (Closed): Versioning with context menu is visible if workspaces are enabledhttp://forge.typo3.org/issues/259622011-04-14T14:13:59ZSimon Schaufelberger
<p>I have versioning and workspaces installed. When installing workspaces, the versioning module in the left frame disappears but the entry in the context menu in the right corner when editing a page is still there. A bug?</p> TYPO3 Core - Bug #25309 (Closed): (old) Extensionmanager Popupwindow cannot be closed after insta...http://forge.typo3.org/issues/253092011-03-11T11:30:25ZSimon Schaufelberger
<p>i get the following js error when i install several extensions that are depending on each other:<br />parent.TYPO3.EM.Tools is undefined</p>
<p>Steps to reproduce: <br />- use old extension manager<br />- uninstall extbase and fluid if installed before.<br />- install fluid. fluid requires extbase to be installed. install extbase. another popup windows opens. after installing extbase, the window shoule be closeable via "Close window." but that is not possible.</p>
<p>(issue imported from #M17928)</p> TYPO3 Core - Feature #25284 (Closed): add braces to link in forgot password emailhttp://forge.typo3.org/issues/252842011-03-08T17:06:59ZSimon Schaufelberger
<p>currently it might happen tha the link is broken and looks like this:</p>
<p>+<ins>+http://mycoolserver.com/index.php?id=23&tx_felogin_pi1</ins>++[user]=3814&tx_felogin_pi1[forgothash]=1299642759%7Cd90fc0de484d6b64e788f381d7db7639</p>
<p>where only the part between +++ is linked.</p>
<p>according to<br /><a class="external" href="http://lists.typo3.org/pipermail/typo3-project-v4/2011-February/001767.html">http://lists.typo3.org/pipermail/typo3-project-v4/2011-February/001767.html</a><br />"simply put the URL inside "<>" and it will be properly recognized by all<br />email clients"</p>
<p>(issue imported from #M17897)</p> TYPO3 Core - Bug #21056 (Closed): Close Button is at the wrong place when editing a file in filelisthttp://forge.typo3.org/issues/210562009-09-15T10:31:08ZSimon Schaufelberger
<p>When editing a file via the file list browser, the close button is the third icon. everywhere else it is the first one except here. for consistency i would suggest to move it to the first position as well</p>
<p>(issue imported from #M11957)</p>