TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-03-19T12:48:29ZTYPO3 Forge
Redmine TYPO3 Core - Bug #103426 (Resolved): Add palette description for tables for listing and modificat...http://forge.typo3.org/issues/1034262024-03-19T12:48:29ZMarcin Sągolmarcin@soee.pl
<p>This is a followup to the <a class="external" href="https://forge.typo3.org/issues/103413">https://forge.typo3.org/issues/103413</a> issue.</p>
<p>Not all users know (even though it is mentioned in the documentation through: <a class="external" href="https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Backend/AccessControl/AccessControlOptions/Index.html">https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Backend/AccessControl/AccessControlOptions/Index.html</a>) that if the table is set for modification, it automatically receives the listing permissions.</p>
<p>This often leads to the situation when both lists have the same tables set while it could be done only for the one (tables for modification).</p>
<p>Maybe a short description for the palette with those lists could be a good idea here.</p> TYPO3 Core - Feature #103187 (Resolved): Add an option to create default backend groups while ins...http://forge.typo3.org/issues/1031872024-02-23T11:10:15ZMarcin Sągolmarcin@soee.pl
<p>As a part of our work for the ACL Improvements (through community budget ideas), we will extend the TYPO3 Installer with an option to allow user to create default backend Role groups like Editor and Advanced Editor.</p>
<p>This will be part of the GUI as well as there will be a dedicated command to handle those groups' creation from CLI.</p> TYPO3 Core - Task #102859 (Closed): Translation file contains unused labels related to workspaceshttp://forge.typo3.org/issues/1028592024-01-18T11:52:30ZMarcin Sągolmarcin@soee.pl
<p>There are 2 labels related to workspaces in the typo3/sysext/core/Resources/Private/Language/locallang_tca.xlf file that are not used anywhere and could/should be removed:</p>
<pre><code class="xml syntaxhl" data-language="xml"><span class="nt"><trans-unit</span> <span class="na">id=</span><span class="s">"workspace_perms_draft"</span> <span class="na">resname=</span><span class="s">"workspace_perms_draft"</span><span class="nt">></span>
<span class="nt"><source></span>Edit Draft (Offline)<span class="nt"></source></span>
<span class="nt"></trans-unit></span>
<span class="nt"><trans-unit</span> <span class="na">id=</span><span class="s">"workspace_perms_custom"</span> <span class="na">resname=</span><span class="s">"workspace_perms_custom"</span><span class="nt">></span>
<span class="nt"><source></span>Create new workspace projects<span class="nt"></source></span>
<span class="nt"></trans-unit></span>
</code></pre> TYPO3 Core - Task #102857 (Closed): The filemounts list in groupData contains not unique valueshttp://forge.typo3.org/issues/1028572024-01-18T09:42:23ZMarcin Sągolmarcin@soee.pl
<p>The <em>fetchGroupData()</em> function within the <em>\TYPO3\CMS\Core\Authentication\BackendUserAuthentication</em> class sets the value of the groupData property (an array of permissions for various access list groups).</p>
<p>The function processes combined permissions from both user and groups to ensure that there are unique values in each list, such as <em>modules</em>, <em>available_widgets</em>, etc.</p>
<p>However, there seems to be a missing check for unique values in the <em>filemounts</em> group.</p> TYPO3 Core - Feature #98110 (Closed): Add an option to sort tables list in DBCheck by name and us...http://forge.typo3.org/issues/981102022-08-09T20:20:34ZMarcin Sągolmarcin@soee.pl
<p>When we have a lot of tables configured in TCA and we often use DbCheck module to search for database records in those tables it is often hard to quickly find the table we are interestend with if we do not knot exact name etc.</p>
<p>It would be much easier to search this select list if we could sort items by table name.</p>
<p>Sometimes developers forget to add title for one or more tables in TCA and it results with an item withouot label on teh select list in DBCheck module.</p>
<p>So second usefull change would be to render table name not title when the title is missing in TCA.</p> TYPO3 Core - Bug #94896 (Closed): BD Check module uses outdated classes to render custom query co...http://forge.typo3.org/issues/948962021-08-15T19:02:08ZMarcin Sągolmarcin@soee.pl
<p>After migration to Boostrap 5 a lot of HTML templates uses outdated classes and structure.</p>
<p>One of this places is custom query builder section (Make Query) in DB Check Full Search module.</p>
<p>When we decide to build custom query all fields in form with custom constraints are rendered taking 100% width of the card container.<br />This make it less readable and less user friendly.</p> TYPO3 Core - Bug #91356 (Closed): Frontend users groups CSH text has typohttp://forge.typo3.org/issues/913562020-05-11T00:07:05ZMarcin Sągolmarcin@soee.pl
<p>There is a small typo in CSH text for frontend groups (<a class="external" href="https://github.com/TYPO3-CMS/frontend/blob/v10.4.1/Resources/Private/Language/locallang_csh_fe_groups.xlf#L66">https://github.com/TYPO3-CMS/frontend/blob/v10.4.1/Resources/Private/Language/locallang_csh_fe_groups.xlf#L66</a>):<br /><pre>
The access restriction in TYPO3 is assigned to these usergroups. When a page or other element is access restricted to a group, only Website users which are members or that group will be able to view the element on the website.
</pre><br />where part <em>members or that</em> should be <em>members of that</em>:<br /><pre>
The access restriction in TYPO3 is assigned to these usergroups. When a page or other element is access restricted to a group, only Website users which are members of that group will be able to view the element on the website.
</pre></p> TYPO3 Core - Task #91352 (Closed): Use Form content element name in Forms module descriptionhttp://forge.typo3.org/issues/913522020-05-09T12:44:50ZMarcin Sągolmarcin@soee.pl
<p>Backend module Forms uses this description (<a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/v10.4.1/typo3/sysext/form/Resources/Private/Language/locallang_module.xlf#L10">https://github.com/TYPO3/TYPO3.CMS/blob/v10.4.1/typo3/sysext/form/Resources/Private/Language/locallang_module.xlf#L10</a>):<br /><pre>
This module ships a flexible and user-friendly form editor. It allows you to build and create versatile forms for your frontend. Your forms can easily be added to any page by using the content element "Mail Form". Within this element, finishers can be overridden.
</pre><br />but since w have content element called Form that allows us to render predefined forms, we should use this name also in module description, so it would be:<br /><pre>
This module ships a flexible and user-friendly form editor. It allows you to build and create versatile forms for your frontend. Your forms can easily be added to any page by using the content element "Form". Within this element, finishers can be overridden.
</pre></p> TYPO3 Core - Task #91343 (Closed): Treat text of command exemple in the Scheduler as one sentence http://forge.typo3.org/issues/913432020-05-07T22:22:46ZMarcin Sągolmarcin@soee.pl
<p>The Scheduler provides a few command examples. First of them uses the following text (<a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/v10.4.1/typo3/sysext/scheduler/Resources/Private/Language/locallang.xlf#L481">https://github.com/TYPO3/TYPO3.CMS/blob/v10.4.1/typo3/sysext/scheduler/Resources/Private/Language/locallang.xlf#L481</a>):<br /><pre>
Every day-of-week from Monday through Friday. at 09:00 and 15:00
</pre></p>
<p>This dot is not needed and we should treat whole text as one sentence, so it should be:<br /><pre>
Every day-of-week from Monday through Friday at 09:00 and 15:00
</pre></p> TYPO3 Core - Bug #91314 (Closed): Typo in validation.identifierExists.message text message in the...http://forge.typo3.org/issues/913142020-05-05T22:58:07ZMarcin Sągolmarcin@soee.pl
<p>The <em>validation.identifierExists.message</em> text message used in typo3/sysext/backend/Classes/Controller/SiteConfigurationController.php controller (<a class="external" href="https://github.com/TYPO3-CMS/backend/blob/v10.4.1/Resources/Private/Language/locallang_siteconfiguration.xlf#L58">https://github.com/TYPO3-CMS/backend/blob/v10.4.1/Resources/Private/Language/locallang_siteconfiguration.xlf#L58</a>) has a small typo:<br /><pre>
Given site identifier "%1s" already exists and points to a different site. The existing identifier "%2s" for this site is kept.';
</pre><br />and it should be:<br /><pre>
Given site identifier "%1s" already exists and points to a different site. The existing identifier "%2s" for this site is kept.
</pre></p> TYPO3 Core - Task #91299 (Closed): Update file_rename.exists.description label translation in Fil...http://forge.typo3.org/issues/912992020-05-04T21:23:13ZMarcin Sągolmarcin@soee.pl
<p>As discussed on Slack, the <em>file_rename.exists.description</em> label from Filelist module (<a class="external" href="https://github.com/TYPO3-CMS/filelist/blob/master/Resources/Private/Language/locallang.xlf#L25">https://github.com/TYPO3-CMS/filelist/blob/master/Resources/Private/Language/locallang.xlf#L25</a>) could be modified by changing from:<br /><pre>
You want to rename the file "{0}" to "{1}", but such a file already exists. How do you want to proceed?
</pre><br />to:<br /><pre>
You want to rename the file "{0}" to "{1}", but the file "{1}" already exists. How do you want to proceed?
</pre></p> TYPO3 Core - Bug #91284 (Closed): Update clearcache.message.error label translation in recordlist...http://forge.typo3.org/issues/912842020-05-03T21:48:03ZMarcin Sągolmarcin@soee.pl
<p>Current translation for <em>clearcache.message.error</em> label in Recordlist module (<a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/recordlist/Resources/Private/Language/locallang.xlf#L16">https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/recordlist/Resources/Private/Language/locallang.xlf#L16</a>) could be improved a bit. <br />For example change from: <pre>Page cache could not cleared</pre> to: <pre>Page cache could not be cleared</pre></p> TYPO3 Core - Bug #61140 (Closed): Use CSS height property to define backend module typo3-docheade...http://forge.typo3.org/issues/611402014-08-22T12:51:13ZMarcin Sągolmarcin@soee.pl
<p>Atm. the height of typo3-docheader-buttons section in backend module layout is calculated based on line-height property. If we use some other CSS framework in our backend module (for example Twitter Bootstrap), the typo3-docheader-buttons changes height and does not match the corresponding section above pages tree.</p>
<p>The only problem here might be situation when inside typo3-docheader-buttons section someone put a lot of various icons, than on smaller screens with fixed height they might not be visible. I doubt though such situation will take place - never seen any module with large number of icons there.</p> TYPO3 Core - Bug #61004 (Closed): Extension manager - upload folders are not deleted when extensi...http://forge.typo3.org/issues/610042014-08-16T14:37:01ZMarcin Sągolmarcin@soee.pl
<p>Some extensions create own folders in uploads/ dir to store data (for example extension_builder creats one called 'tx_extensionbuilder'). When extension id deactivated and removed through Extension Builder this folders stays untouched. I think when extension is removed from server also related upload folders should be deleted.</p> TYPO3 Core - Bug #60256 (Closed): Argument 2 passed to mapRecordTypeToSpriteIconName() must be of...http://forge.typo3.org/issues/602562014-07-11T08:16:06ZMarcin Sągolmarcin@soee.pl
<p>After upgrade to 6.2.4 i can see some errors in Log module:</p>
<p><code>Core: Error handler (BE): PHP Catchable Fatal Error: Argument 2 passed to TYPO3\CMS\Backend\Utility\IconUtility::mapRecordTypeToSpriteIconName() must be of the type array, null given, called in /typo3_src-6.2.4/typo3/sysext/backend/Classes/Utility/IconUtility.php on line 841 and defined in /typo3_src-6.2.4/typo3/sysext/backend/Classes/Utility/IconUtility.php line 862 </code></p>
<p><code>Core: Error handler (BE): PHP Catchable Fatal Error: Argument 2 passed to TYPO3\CMS\Backend\Utility\IconUtility::mapRecordTypeToSpriteIconClass() must be of the type array, null given, called in /typo3_src-6.2.4/typo3/sysext/backend/Classes/Utility/IconUtility.php on line 723 and defined in /typo3_src-6.2.4/typo3/sysext/backend/Classes/Utility/IconUtility.php line 840 Zmiany w plikach: latitude,longitude. </code></p>
<p><code>Core: Error handler (BE): PHP Catchable Fatal Error: Argument 2 passed to TYPO3\CMS\Version\Hook\IconUtilityHook::overrideIconOverlay() must be of the type array, null given, called in /typo3_src-6.2.4/typo3/sysext/backend/Classes/Utility/IconUtility.php on line 1004 and defined in /typo3_src-6.2.4/typo3/sysext/version/Classes/Hook/IconUtilityHook.php line 32 </code></p>
<p><code>Core: Error handler (BE): PHP Catchable Fatal Error: Argument 2 passed to TYPO3\CMS\Backend\Utility\IconUtility::mapRecordOverlayToSpriteIconName() must be of the type array, null given, called in /typo3_src-6.2.4/typo3/sysext/backend/Classes/Utility/IconUtility.php on line 714 and defined in /typo3_src-6.2.4/typo3/sysext/backend/Classes/Utility/IconUtility.php line 947 Zmiany w plikach: latitude,longitude.</code></p>
<p><code>Core: Error handler (BE): PHP Catchable Fatal Error: Argument 2 passed to TYPO3\CMS\Backend\Utility\IconUtility::getSpriteIconForRecord() must be of the type array, null given, called in /typo3_src-6.2.4/typo3/sysext/core/Classes/Utility/File/ExtendedFileUtility.php on line 409 and defined in /typo3_src-6.2.4/typo3/sysext/backend/Classes/Utility/IconUtility.php line 710</code></p>