TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692014-04-06T13:15:19ZTYPO3 Forge
Redmine TYPO3 Core - Feature #57685 (Closed): Sort PackageStates.php by extension keyhttp://forge.typo3.org/issues/576852014-04-06T13:15:19ZJost Baronjost.baron@gmx.de
<p>Hi!</p>
<p>It would be nice if the PackageStates.php would is sorted. Currently, the sorting changes every time the file is saved, making it very hard to properly track the changes using a version control system.</p>
<p>I know this comes from Flow, but I could not find their bugtracker to put it there.</p> TYPO3 Core - Bug #57200 (Closed): Update-Icon not shown for manually uploaded extensionshttp://forge.typo3.org/issues/572002014-03-23T12:03:10ZJost Baronjost.baron@gmx.de
<p>After uploading an extension manually, the extension manager does not show the option to update it, even if there is a newer version available in TER, and that version is compatible to the current environment. This happens on current master (2144d4c6e0f997f824e9dc41eb3eafb2b48a180d).</p>
<p>Steps to reproduce:</p>
<p>1. Install TYPO3 with current master<br />2. Download EXT:news in an older version: <a class="external" href="https://typo3.org/extensions/repository/download/news/2.2.1/t3x/">https://typo3.org/extensions/repository/download/news/2.2.1/t3x/</a> and install it using the upload form in the extension manager<br />3. Update the Extension list from TER, if not already done<br />4. The update icon is not there for EXT:news. It does not matter if the extension list is updated again or not.</p>
<p>This could be security-related, since hides available extension updates. This gets even more problematic with the release of 6.2, since many extensions are not officially compatible, but work with it. To install them, the manual upload functionality of the extension manager is the most easy way.</p> TYPO3 Core - Bug #56701 (Closed): Static template of css_styled_content can no longer be included...http://forge.typo3.org/issues/567012014-03-10T02:15:05ZJost Baronjost.baron@gmx.de
<p>If it is included using an <INCLUDE> directive, certain other TS (Plugin rendering definitions) is not included. The problematic commit is<br />3ce53655a3739dadd732556e1902e7686ef59260 (<a class="external" href="https://review.typo3.org/#/c/27587/">https://review.typo3.org/#/c/27587/</a>).</p>
<p>Steps to reproduce:</p>
<p>1. Create a new TYPO3 installation using the current master branch.<br />2. Install the development branch of EXT:flux (<a class="external" href="https://github.com/FluidTYPO3/flux">https://github.com/FluidTYPO3/flux</a>)<br />3. Install the development branch of EXT:fluidcontent (<a class="external" href="https://github.com/FluidTYPO3/fluidcontent">https://github.com/FluidTYPO3/fluidcontent</a>)</p>
<p>Create a new root page with the following root template:</p>
<p>Constants:<br /><pre><INCLUDE_TYPOSCRIPT: source="FILE:EXT:css_styled_content/static/constants.txt"></pre></p>
<p>Setup:<br /><pre><INCLUDE_TYPOSCRIPT: source="FILE:EXT:css_styled_content/static/setup.txt">
page = PAGE
page.10 < styles.content.get</pre></p>
<p>4. Check out commit 3ce53655a3739dadd732556e1902e7686ef59260 of the TYPO3 core and view the full Typoscript Template in the Analyzer. There is no object <code>tt_content.fluidcontent_content</code> being defined.<br />5. When using the previous commit 85d88e4f9d0efe4443bace89ce98c585255cacfd, <code>tt_content.fluidcontent_content</code> is defined correctly.</p> TYPO3 Core - Bug #56350 (Closed): Can't select text in the "all configuration" area of the new in...http://forge.typo3.org/issues/563502014-02-26T17:25:53ZJost Baronjost.baron@gmx.de
<p>When selecting text in one of the accordions using the mouse, it is only selected as long as the mouse button is pressed. As soon as it is released, the text gets deselected because the input field gets focus.</p>
<p>This is a problem because it is not what is expected, and because sometimes one might want to C&P text from there.</p>
<p>Used browser: FF 27.0.1</p> TYPO3 Core - Bug #56221 (Closed): Can't remove static templates from selection in template modulehttp://forge.typo3.org/issues/562212014-02-23T15:59:23ZJost Baronjost.baron@gmx.de
<p>After including a static template to a template using the template module, it cannot be removed afterwards. Clicking the "remove" button produces this JS error (in FF 27.0.1):</p>
<pre>
ReferenceError: formEl is not defined
var formObj = formEl.get();
FormEngine.js (line 178)
</pre>
<p>TYPO3-Version is current master (945911006229524d55cb48f1f7de0898be9a7b7f).</p> TYPO3 Core - Task #55820 (Closed): Improve speed of loading the extension list from TERhttp://forge.typo3.org/issues/558202014-02-09T19:30:05ZJost Baronjost.baron@gmx.de
<p>See subject, this issue is only for gerrit.</p> TYPO3 Core - Bug #54501 (Closed): Column names are not correctly displayed in the list modulehttp://forge.typo3.org/issues/545012013-12-18T22:45:55ZJost Baronjost.baron@gmx.de
<p>If there are multiple columns defined via a backend layout, and all these columns are filled on a page, the list module shows only the name of the first column. For the other columns only the column number is shown.</p>
<p>A screenshot is appended.</p> TYPO3 Core - Feature #53992 (Closed): Make it possible to change the backend layout for page type...http://forge.typo3.org/issues/539922013-11-26T22:00:27ZJost Baronjost.baron@gmx.de
<p>This would make sense since system folders can be used to store shared content elements.</p>
<p>Actually, this already possible by changing the page type to "Standard page", set the correct layout and then switch the page type back to "folder".</p> TYPO3 Core - Bug #53682 (Closed): Exception '$toolbarItem "shortcuts" must implement interface .....http://forge.typo3.org/issues/536822013-11-15T20:39:02ZJost Baronjost.baron@gmx.de
<p>The backend does not work with PHP 5.5.6 anymore. The exception thrown is this one:</p>
<p>$toolbarItem "shortcuts" must implement interface TYPO3\CMS\Backend\Toolbar\ToolbarItemHookInterface</p>
<p>To reproduce, create a new 6.2 installation using the wizard in the install tool, and run it on PHP 5.5.6.</p>
<p>This does not happen on PHP 5.5.5 or 5.4.22, I have not tested other versions. Ernesto Baschny pointed out that this problem occurred with PHP 5.3.3 too, maybe that info helps?</p>
<p><strong>Link to the PHP bug tracker:</strong> <a class="external" href="https://bugs.php.net/bug.php?id=66107">https://bugs.php.net/bug.php?id=66107</a></p>
<p>The following classes are affected:</p>
<ul>
<li>typo3/sysext/backend/Classes/Toolbar/ToolbarItemHookInterface </li>
<li>typo3/sysext/backend/Classes/Toolbar/ShortcutToolbarItem </li>
<li>typo3/sysext/backend/Classes/Toolbar/LiveSearchToolbarItem </li>
<li>typo3/sysext/backend/Classes/Toolbar/ClearCacheToolbarItem </li>
<li>typo3/sysext/backend/Classes/Form/Element/TreeElement.php</li>
<li>typo3/sysext/workspaces/Classes/ExtDirect/WorkspaceSelectorToolbarItem.php</li>
<li>typo3/sysext/opendocs/Classes/Controller/OpendocsController.php</li>
<li>typo3/sysext/sys_action/Classes/ActionToolbarMenu.php</li>
</ul>
<p>To solve the issue temporarily you need to modify the constructor of those classes by removing the reference operator (&) of all referenced class parameters.<br /><pre><code class="php syntaxhl" data-language="php"><span class="k">public</span> <span class="k">function</span> <span class="n">__construct</span><span class="p">(</span><span class="kt">SomeClassNameHere</span> <span class="o">&</span><span class="nv">$backendReference</span> <span class="o">=</span> <span class="kc">NULL</span><span class="p">)</span>
</code></pre></p>
<pre><code class="php syntaxhl" data-language="php"><span class="k">public</span> <span class="k">function</span> <span class="n">__construct</span><span class="p">(</span><span class="kt">SomeClassNameHere</span> <span class="nv">$backendReference</span> <span class="o">=</span> <span class="kc">NULL</span><span class="p">)</span>
</code></pre> TYPO3 Core - Feature #53369 (Rejected): Make it possible to define backend user rights via (TypoS...http://forge.typo3.org/issues/533692013-11-06T12:19:59ZJost Baronjost.baron@gmx.de
<p>It would be really helpful to be able to define user rights in files. This way they can be version controlled, moved from one project to the next one and ideally be split in multiple files (e.g. per extension). Extensions could even deliver some tested default configurations.</p>
<p>In TypoScript, the syntax could look like this, in userTS:</p>
<pre>
userRights {
allowModules {
web = 1
web.page = 1
web.list = 0
}
allowSelectTable {
tt_content = 1
backend_layouts = 0
}
allowUpdateTable {
[...]
}
allowPageTypes {
[...]
}
allowExcludeFields {
tt_content {
title = 1
text_color = 0
}
}
explicitAllowDeny {
header = 1
form = 0
}
# Only languages with ids 0, 2 and 3
restrictToLanguages = 0,2,3
}
</pre>
<p>I'm not sure how this should interact with the current database driven user permission system. I have two ideas:</p>
<ol>
<li>The permissions defined in TypoScript are overwritten by permissions from the database. Since there is no option "not specified" in the permission system, it would be necessary to introduce such a setting per permission in the backend (e.g. as an extra checkbox). Otherwise the permission definitions from TS would always be completely overwritten by the ones from the database. This approach is consistent with the settings priorization from plugin flexforms.</li>
<li>The permissions defined in TypoScript overwrite the permissions set in the backend. This would probably be simpler to implement, but it is inconsistent with the flexform handling.</li>
</ol> TYPO3 Core - Task #46853 (Closed): Move code for clearing text fields to jquery plugin for easy r...http://forge.typo3.org/issues/468532013-04-01T22:59:23ZJost Baronjost.baron@gmx.deTYPO3 Core - Bug #46573 (Closed): Time of last update from TER does not update after update from TERhttp://forge.typo3.org/issues/465732013-03-22T22:21:35ZJost Baronjost.baron@gmx.de
<p>Steps to reproduce:</p>
<p>1. Update extension list from TER in the extension manager<br />2. Update typo database using "update tx_extensionmanager_domain_model_repository set last_update = 1234567890;" <br />3. Verify that the extensionmanager shows a large number of days since the last update<br />4. Delete the file "typo3temp/1.extensions.xml.gz" to force an update from TER<br />5. Update extension list from TER in the extension manager - the same number of days as in 3. should be shown after the update. Doing another update fixes that.</p> TYPO3 Core - Task #46030 (Closed): Provide error messages when TER-update failshttp://forge.typo3.org/issues/460302013-03-04T22:37:20ZJost Baronjost.baron@gmx.de
<p>A nonstop spinning wheel in case of an error is not good. Show a flash message with info on the error instead.</p> TYPO3 Core - Task #46029 (Closed): Make "Update from TER"-Link more visiblehttp://forge.typo3.org/issues/460292013-03-04T21:57:22ZJost Baronjost.baron@gmx.de
<p>The "Update extension list"-Button in the new extension manager should be more recognizable. The text on the upper right is not recognizable as a thing that can be clicked on. I had to google to find it.</p>
<p>I have a patch ready and will submit it soon.</p> TYPO3 Core - Task #45499 (Closed): \TYPO3\CMS\Utility\StringUtility is not used in core - conside...http://forge.typo3.org/issues/454992013-02-15T04:26:57ZJost Baronjost.baron@gmx.de
<p>Hi.</p>
<p>If my patch for Issue <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: em should not export invisible folders (Closed)" href="http://forge.typo3.org/issues/45404">#45404</a> is accepted, the class \TYPO3\CMS\Utility\StringUtility will not be used in the core or any system extension anymore. Also it seems not that mature in its current state.</p>
<p>Please consider deprecation of that whole class (and its tests, of course).</p>