TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692014-06-06T22:27:52ZTYPO3 Forge
Redmine TYPO3 Core - Bug #59397 (Closed): Extbase FrontendUser does not work with the TCA caching feature...http://forge.typo3.org/issues/593972014-06-06T22:27:52ZJost Baronjost.baron@gmx.de
<p>I use the following code to add a field to the <code>fe_users</code> table:</p>
<code class="php syntaxhl" data-language="php"> <span class="nv">$newColumns</span> <span class="o">=</span> <span class="k">array</span><span class="p">(</span>
<span class="s1">'ratings'</span> <span class="o">=></span> <span class="k">array</span><span class="p">(</span>
<span class="s1">'label'</span> <span class="o">=></span> <span class="nv">$lll</span> <span class="mf">.</span> <span class="s1">'somelabel'</span><span class="p">,</span>
<span class="s1">'config'</span> <span class="o">=></span> <span class="k">array</span><span class="p">(</span>
<span class="s1">'readOnly'</span> <span class="o">=></span> <span class="s1">'1'</span><span class="p">,</span>
<span class="s1">'type'</span> <span class="o">=></span> <span class="s1">'select'</span><span class="p">,</span>
<span class="s1">'foreign_table'</span> <span class="o">=></span> <span class="s1">'mytable'</span><span class="p">,</span>
<span class="s1">'foreign_field'</span> <span class="o">=></span> <span class="s1">'somefield'</span><span class="p">,</span>
<span class="s1">'maxitems'</span> <span class="o">=></span> <span class="s1">'1000000'</span><span class="p">,</span>
<span class="s1">'minitems'</span> <span class="o">=></span> <span class="s1">'0'</span><span class="p">,</span>
<span class="s1">'autoSizeMax'</span> <span class="o">=></span> <span class="s1">'20'</span><span class="p">,</span>
<span class="p">),</span>
<span class="p">),</span>
<span class="p">);</span>
<span class="nc">ExtensionManagementUtility</span><span class="o">::</span><span class="nf">addTCAcolumns</span><span class="p">(</span><span class="s1">'fe_users'</span><span class="p">,</span> <span class="nv">$newColumns</span><span class="p">);</span>
<span class="c1">// Add types to the TCA</span>
<span class="nv">$recordType</span> <span class="o">=</span> <span class="s1">'MyRecordType'</span><span class="p">;</span>
<span class="nv">$GLOBALS</span><span class="p">[</span><span class="s1">'TCA'</span><span class="p">][</span><span class="s1">'fe_users'</span><span class="p">][</span><span class="s1">'types'</span><span class="p">][</span><span class="nv">$recordType</span><span class="p">]</span> <span class="o">=</span> <span class="nv">$GLOBALS</span><span class="p">[</span><span class="s1">'TCA'</span><span class="p">][</span><span class="s1">'fe_users'</span><span class="p">][</span><span class="s1">'types'</span><span class="p">][</span><span class="s1">'0'</span><span class="p">];</span>
<span class="nv">$GLOBALS</span><span class="p">[</span><span class="s1">'TCA'</span><span class="p">][</span><span class="s1">'fe_users'</span><span class="p">][</span><span class="s1">'columns'</span><span class="p">][</span><span class="s1">'tx_extbase_type'</span><span class="p">][</span><span class="s1">'config'</span><span class="p">][</span><span class="s1">'items'</span><span class="p">][]</span> <span class="o">=</span> <span class="k">array</span><span class="p">(</span>
<span class="nv">$lll</span> <span class="mf">.</span> <span class="s1">'anotherlabel'</span><span class="p">,</span>
<span class="nv">$recordType</span>
<span class="p">);</span>
<span class="nc">ExtensionManagementUtility</span><span class="o">::</span><span class="nf">addToAllTCAtypes</span><span class="p">(</span><span class="s1">'fe_users'</span><span class="p">,</span> <span class="s1">'ratings'</span><span class="p">,</span> <span class="nv">$recordType</span><span class="p">,</span> <span class="s1">'after:tx_extbase_type'</span><span class="p">);</span>
</code>
<p>This does work if used in <code>ext_tables.php</code>, but not if used in <code>Configuration/TCA/Overrides</code>. In the latter case, it seems that the <code>ext_tables.php</code> from Extbase is executed later and overwrites my changes (especially the <code>types</code> part).</p>
<p>Regards Jost</p> TYPO3 Core - Feature #58332 (Closed): Updating from 4.5 to 6.2 removes some be_group permissionshttp://forge.typo3.org/issues/583322014-04-29T15:43:31ZJost Baronjost.baron@gmx.de
<p>On updates from 4.5 to 6.2, the permissions for be_groups changed. In this case, the right to access the exclude fields 'imageorient' and 'imagecols' in tt_content have been removed/not added.</p>
<p>Each update was done version by version, going through respective latest releases of 4.5, 4.6, 4.7, 6.0 and 6.1. I cannot say in exactly which update the problem occurred, but I have experienced it in multiple cases.</p>
<p>When looking at old database dumps from before the update, I couldn't find permissions for the fields in the database (in table 'be_groups', field 'non_exclude_fields'), although they were editable for restricted accounts.</p> TYPO3 Core - Bug #58260 (Closed): Installtool-Check "checkMaximumFileUploadSize" doesn't look at ...http://forge.typo3.org/issues/582602014-04-27T15:45:48ZJost Baronjost.baron@gmx.de
<p>If the php-setting <code>upload_max_filesize</code> is less than 10MB (10 * 1024 * 1024), the following message appears:</p>
<pre>
PHP Maximum upload filesize too small
upload_max_filesize=8M
By default TYPO3 supports uploading, copying and moving files of sizes up to 10MB (you can alter
the TYPO3 defaults with the config option TYPO3_CONF_VARS[BE][maxFileSize]). Your current PHP
value is below this, so right now, PHP determines the limits for uploaded filesizes and not TYPO3. It is
recommended that the value of upload_max_filesize is at least equal to the value of
TYPO3_CONF_VARS[BE][maxFileSize]
</pre>
<p>This message suggests that the maxFileSize is relevant here, but in fact it does not influence if the message appears, only the <code>upload_max_filesize</code> is relevant.</p>
<p>Solution: Either modify the message, or change the check.</p> 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 #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 - 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>