TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-02-06T10:22:55ZTYPO3 Forge
Redmine TYPO3 Core - Bug #103059 (New): Not possible to see references if no access to content where file...http://forge.typo3.org/issues/1030592024-02-06T10:22:55ZSybille Peterssypets@gmx.de
<p>In the file list you can see the number of references for files which are referenced from content which you do not have access to, and you can also click on the link, but the references will not be displayed.</p>
<p>I would expect it to be possible to see the references (read-only) and also be able to see which pages the references are on (ideally by having a "view page" button).</p>
<p>Otherwise you cannot delete files and you can't find out (as normal editor) where they are still being referenced from.</p>
<p>This means, these cases can only be resolved by admin users or by users with access to both the files and the content.</p>
<a name="Example"></a>
<h2 >Example<a href="#Example" class="wiki-anchor">¶</a></h2>
<p>user A<br />- access to pages /a/<br />- access to files fileadmin/a</p>
<p>user B<br />- access to pages /b/<br />- access to files fileadmin/b</p>
<p>Content in /a/ links to file /b/test.png. Now, user b cannot see references for test.png and cannot delete test.png.</p> TYPO3 Core - Bug #101411 (New): Message that there are references which point to this record is n...http://forge.typo3.org/issues/1014112023-07-22T12:42:30ZSybille Peterssypets@gmx.de
<p>Usually, we get an alert, sometime like this:</p>
<blockquote>
<p>Are you sure you want to delete the record 'textmedia1 [tt_content:54]'? There are 1 reference(s) to this record!</p>
</blockquote>
<p>or</p>
<blockquote>
<p>Are you sure you want to delete 'textmedia with shortcuts to this ce'? (There are 1 reference(s) to this record!)</p>
</blockquote>
<p>when trying to delete a record (e.g. [textmedia]) which has references pointing to it (e.g. "Insert Records" [shortcut]").</p>
<p>But sometimes we get a generic message which does not point out there are references, such as:</p>
<blockquote>
<p>Are you sure you want to delete this record?</p>
</blockquote>
<p>It looks like the behaviour improved between v11 => v13 but is not fully resolved.</p>
<p>(language label: labels.referencesToRecord)</p>
<a name="Problems-Inconsistencies"></a>
<h2 >Problems / Inconsistencies<a href="#Problems-Inconsistencies" class="wiki-anchor">¶</a></h2>
<p>in <strong>v13</strong></p>
<ul>
<li>list module: if using checkboxes to select several records then deleting, we get:</li>
</ul>
<blockquote>
<p>Delete marked<br />Are you sure you want to delete all marked records from the table 'Page Content'?<br />Close Delete</p>
</blockquote>
<p>(no hint that there are references)</p>
<ul>
<li>(minor): in FormEngine the "Delete record" button does not have an "(!)", in the other cases it does</li>
</ul>
<p>in <strong>v11</strong> , sames as v13, but also</p>
<ul>
<li>in page layout: using inline delete button, we get generic message (not warning about references):</li>
</ul>
<blockquote>
<p>Delete this record?<br />Delete this record?<br />Cancel | OK</p>
</blockquote>
<ul>
<li>some more minor inconsistencies in how the delete button is named etc.</li>
</ul>
<a name="Screenshots"></a>
<h2 >Screenshots<a href="#Screenshots" class="wiki-anchor">¶</a></h2>
<p><img src="http://forge.typo3.org/attachments/download/37844/delete_record_with_references_generic_message.png" title="generic delete message" alt="generic delete message" loading="lazy" /></p>
<p><img src="http://forge.typo3.org/attachments/download/37845/delete_record_with_references_message_points_out_references.png" title="delete message which mentions references" alt="delete message which mentions references" loading="lazy" /></p>
<p>v13</p>
<p><img src="http://forge.typo3.org/attachments/download/37846/v13_delete_record_with_references_in_list_module_bulk_removal_no_mention_of_references.png" title="v13 bulk removal in list module (references not mentioned)" alt="v13 bulk removal in list module (references not mentioned)" loading="lazy" /></p>
<a name="Full-report"></a>
<h2 >Full report<a href="#Full-report" class="wiki-anchor">¶</a></h2>
<p>see delete_record_with_references.txt</p> TYPO3 Core - Bug #100123 (New): Regular exceptions due to dependency injection (di) cachehttp://forge.typo3.org/issues/1001232023-03-09T06:20:09ZSybille Peterssypets@gmx.de
<p>I have regular error messages in the logs due to Dependency Injection cache /var/cache/code/di. This improved considerably, after switching from shared (NFS) to the VM storage, but has not disappeared.</p>
<p>This also results in error message when loading a page in frontend. When page is loaded again, it is ok. Since (page) cache is warmed up at night and after deployment, these errors are usually not noticed, but it does happen.</p>
<a name="Switching-to-non-NFS"></a>
<h2 >Switching to non-NFS:<a href="#Switching-to-non-NFS" class="wiki-anchor">¶</a></h2>
<p>- entire var/cache/code switched to local storage<br />- when deploying, system cache on all machines must be flushed (and opcache also, of course)<br />- cache is warmed up during deployment ("@php vendor/bin/typo3 cache:warmup")</p>
<p>The number of log messages with these errors are reduced. Last time I checked, I had roughly 60, all with nearly same timestamp (within 20 seconds).</p>
<a name="setup"></a>
<h2 >setup<a href="#setup" class="wiki-anchor">¶</a></h2>
<ul>
<li>TYPO3 11.5.24</li>
<li>dual machines behind load-balancer, however currently only one at a time utilized, other is fallback</li>
<li>uses the defaults for caching, except what is usually in the DB is in Redis and b13/distributed-locking is used for shared locking. var/cache/di is switched to local storage</li>
</ul>
<a name="Logs"></a>
<h2 >Logs<a href="#Logs" class="wiki-anchor">¶</a></h2>
<p><strong>ssl_access.log</strong><br />1)<br />"Call to a member function resolvePackagePath" <br /><pre>
Thu Mar 02 05:26:22 2023] [error] [pid 18699] mod_proxy_fcgi.c(851): [client 54.36.148.228:29271] AH01071: Got error 'PHP message:
PHP Fatal error: Uncaught Error: Call to a member function resolvePackagePath()
on null in
/var/www/mysite/releases/1/public/typo3/sysext/core/Classes/Utility/ExtensionManagementUtility.php:135
</pre></p>
<p><strong>TYPO3 log</strong> (logfile if default LogWriter is used, usually in var/log or typo3temp/var/log)</p>
<p>2)</p>
<p>"The temporary cache file .*cache/code/di/.*could not be written" <br /><pre>
Thu, 02 Mar 2023 23:36:22 +0100 [CRITICAL] request="825e1a685dff9" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler":
Core: Exception handler (WEB: BE): TYPO3\CMS\Core\Cache\Exception, code #1334756737,
file /var/www/www.uni-oldenburg.de/releases/115/htdocs/typo3/sysext/core/Classes/Cache/Backend/SimpleFileBackend.php, line 232:
The temporary cache file "/var/www/www.uni-oldenburg.de/releases/115/var/cache/code/di/640124e6f2270786869194.temp" could not be written. - {"mode":"WEB","application_mode":"BE","exception_class":"TYPO3\\CMS\\Core\\Cache\\Exception","exception_code":1334756737,"file":"/var/www/www.uni-oldenburg.de/releases/115/htdocs/typo3/sysext/core/Classes/Cache/Backend/SimpleFileBackend.php","line":232,"message":"The temporary cache file \"/var/www/www.uni-oldenburg.de/releases/115/var/cache/code/di/640124e6f2270786869194.temp\" could not be written.","request_url":"https://mysite/","exception":null}
</pre></p>
<p>3)<br />"Class 'DependencyInjectionContainer_[0-9a-f]*' not found" <br /><pre>
Fri, 03 Mar 2023 00:11:29 +0100 [CRITICAL] request="91d0aa2d1ff6e" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB: BE): Error, code #0, file /var/www/www.uni-oldenburg.de/releases/115/htdocs/typo3/sysext/core/Classes/DependencyInjection/ContainerBuilder.php, line 98: Class 'DependencyInjectionContainer_dfe57bd75f64f6fcd823c25279efdcb969473f70' not found - {"mode":"WEB","application_mode":"BE","exception_class":"Error","exception_code":0,"file":"/var/www/www.uni-oldenburg.de/releases/115/htdocs/typo3/sysext/core/Classes/DependencyInjection/ContainerBuilder.php","line":98,"message":"Class 'DependencyInjectionContainer_dfe57bd75f64f6fcd823c25279efdcb969473f70' not found","request_url":"https://mysite/","exception":null}
</pre></p> TYPO3 Core - Bug #99469 (New): Record selector behaves differently for pages depending on where y...http://forge.typo3.org/issues/994692023-01-05T14:07:42ZSybille Peterssypets@gmx.de
<p>The Records Selector may return different results for pages, depending on where you click (either left column or right column). Apparently either a page id is returned or a "pages_ID". In the situation described below, the page ID then resolves to a tt_content id ("tt_content_ID").</p>
<p>This was originally reported for gridelements and can be reproduced with the latest EA version, see <a class="external" href="https://github.com/CodersCare/gridelements_EA/issues/510">https://github.com/CodersCare/gridelements_EA/issues/510</a></p>
<p>I have create a minimal example where this is also reproducible: <a class="external" href="https://github.com/sypets/sypets_example_shortcut_records_pages">https://github.com/sypets/sypets_example_shortcut_records_pages</a></p>
<a name="What-is-affected"></a>
<h2 >What is affected<a href="#What-is-affected" class="wiki-anchor">¶</a></h2>
<p>If the configuration for the tt_content.records field (or something else?) has been changed to accept pages as well:</p>
<pre><code class="php syntaxhl" data-language="php"><span class="nv">$GLOBALS</span><span class="p">[</span><span class="s1">'TCA'</span><span class="p">][</span><span class="s1">'tt_content'</span><span class="p">][</span><span class="s1">'columns'</span><span class="p">][</span><span class="s1">'records'</span><span class="p">][</span><span class="s1">'config'</span><span class="p">][</span><span class="s1">'allowed'</span><span class="p">]</span> <span class="mf">.</span><span class="o">=</span> <span class="s1">',pages'</span><span class="p">;</span>
</code></pre>
<a name="Reproduce"></a>
<h2 >Reproduce:<a href="#Reproduce" class="wiki-anchor">¶</a></h2>
<p>either with gridelements or my example extension:</p>
<p>1. Create a content element with type "shortcut" <br />2. In the form, for records, <strong>click on "Page"</strong> (not "Page Content" !)<br />3. In the "Record selector" select a page <strong>in the left column</strong> (not in the right column) by clicking on the link symbol on the right.</p>
<p>What is now written to records is something like this:</p>
<pre>
select uid,records from tt_content where uid=454;
+-----+----------------+
| uid | records |
+-----+----------------+
| 454 | tt_content_491 |
+-----+----------------+
</pre>
<p>In case no corresponding tt_content element exists for the page id, nothing is written to the field.</p>
<a name="Cross-checking"></a>
<h2 >Cross checking<a href="#Cross-checking" class="wiki-anchor">¶</a></h2>
<p>Weirdly enough, doing the same thing with pages.shortcut is not a problem, but here there are not several table types which can be used, it is always pages.</p>
<a name="Screenshots"></a>
<h2 >Screenshots<a href="#Screenshots" class="wiki-anchor">¶</a></h2>
<p>Screenshots for testing with gridelments:</p>
<p><img src="http://forge.typo3.org/attachments/download/37289/record_selector_link.png" alt="" loading="lazy" /></p>
<p><img src="http://forge.typo3.org/attachments/download/37288/gridelements_shortcut_record_selector4.png" title="Record selector" alt="Record selector" loading="lazy" /></p>
<p><img src="http://forge.typo3.org/attachments/download/37287/gridelements_shortcut_animated.gif" title="Animated gif" alt="Animated gif" loading="lazy" /></p> TYPO3 Core - Bug #99162 (New): Entire cache flushed if TypoScript template is modified and saved ...http://forge.typo3.org/issues/991622022-11-22T14:18:32ZSybille Peterssypets@gmx.de
<p>If a root or extension TypoScript template is modified and saved, the entire page cache is flushed. Apparently even pages in other site (in multi-site installation) and redirects cache is flushed. Even if just a constant is changed.</p>
<a name="Affected-versions"></a>
<h2 >Affected versions<a href="#Affected-versions" class="wiki-anchor">¶</a></h2>
<p>Not a new issue, was this way since v11 at least, reproducible in v13</p>
<a name="Possible-solutions"></a>
<h2 >Possible solutions<a href="#Possible-solutions" class="wiki-anchor">¶</a></h2>
<p>1. change the behaviour if possible (e.g. flush only cache entries affected by the change, e.g. on subpages)<br />2. Make it possible to override this behaviour</p>
<a name="Usecases"></a>
<h2 >Usecases<a href="#Usecases" class="wiki-anchor">¶</a></h2>
<p>We use a sitepackage to manage TypoScript, but sometimes specific changes need to be made for just one page, e.g. for powermail configuration. It is not possible to do this without flushing entire cache, which has a negative impact on performance</p> TYPO3 Core - Bug #97486 (New): Consider file mounts when renaming or deleting directorieshttp://forge.typo3.org/issues/974862022-04-27T12:20:38ZSybille Peterssypets@gmx.de
<ul>
<li>Directories which have filemounts pointing to them (or to a child page) should not be able to be deleted </li>
<li>If the directory is renamed, the directory in the file mounts (and file mounts with child directories) should be renamed as well</li>
</ul>
<p>Given the following situation:</p>
<ul>
<li>Complex access system of groups / filemounts with filemounts within<br />filemounts</li>
</ul>
<p>e.g.</p>
<pre>
- fileadmin
-> dir1
-> dir1.1
</pre>
<p>- group1 - uses filemount for dir1<br />- group1.1 - uses filemount for dir1.1</p>
<p>Now users in group1 (and admin) could rename the directory dir1.1 (or<br />delete it if no files with references in it). If that happens, the user in group 1.1 can no longer access the files.</p>
<p>Users in group1 may not be aware of the subgroups.</p>
<p>There is no warning, when doing this.</p>
<a name="My-suggestion"></a>
<h2 >My suggestion:<a href="#My-suggestion" class="wiki-anchor">¶</a></h2>
<ul>
<li>it should not be possible by users to delete directories with filemounts (and also with filemounts attached to subdirectories)</li>
<li>directories with filemounts should be marked in filelist so they are<br />visible as "system folder" (and ideally visible as directory with a filemount for admins)</li>
<li>If it is allowed for the directories with filemounts pointing to them (or to child directories) are allowed to be renamed, the file mounts records (sys_file_mount) should be updated as well.</li>
</ul>
<a name="TYPO3-versions"></a>
<h2 >TYPO3 versions<a href="#TYPO3-versions" class="wiki-anchor">¶</a></h2>
<p>I reproduced this in v10, superficially confirmed in latest master v12.</p>
<a name="sys_filemounts"></a>
<h2 >sys_filemounts<a href="#sys_filemounts" class="wiki-anchor">¶</a></h2>
<p>- base (int), is storage<br />- path (varchar), is relative path in storage (not uid)</p>
<p>Thus, sys_filemounts uses the path, not the uid(s) of dirs / Folders (and AFAIK there is no management of folders by uid anyway).</p>
<p>See also note in Folder class:</p>
<pre>
/** The identifier of this folder to identify it on the storage.
* On some drivers, this is the path to the folder, but drivers could also just
* provide any other unique identifier for this folder on the specific storage.
*
* @var string
*/
protected $identifier;
</pre> TYPO3 Core - Bug #97152 (New): Usability problem in listing of references: content (including act...http://forge.typo3.org/issues/971522022-03-09T13:50:03ZSybille Peterssypets@gmx.de
<p>In the list of reference (opened via the file list) you must scroll down to see the edit action buttons if the visible content is too wide.</p>
<p>There is a horizontal scrollbar on the bottom, so there is a way to reach the clipped off content.</p>
<p>This is only a bother, if there are lots of entries and you don't see the scrollbar and you either have to scroll down and back up (or you are not aware there is a scrollbar and not aware there is more content).</p>
<a name="Reproduce"></a>
<h2 >Reproduce<a href="#Reproduce" class="wiki-anchor">¶</a></h2>
<p>Intention: we want to see a list of references for a file and make changes in a (related) content element.</p>
<ol>
<li>Use latest main branch with styleguide</li>
<li>Let styleguide create content</li>
<li>In file list click on fileadmin/styleguide and choose a file, e.g. bus_lane.jpg and click on the "Ref" link (right column)</li>
<li>When scrolling down we see the "References to this item"</li>
</ol>
<p>The content is clipped, we do not see the action buttons. We must scroll down to do that to get to the horizontal scrollbar.</p>
<p>The problem exists due to the following. Some of these are a question of general BE UI concept.</p>
<p>- It is not possible to resize the dialog (this is generally so, so it complies to general BE UI concept)<br />- In some other dialogs in the BE, in addition to the action icons on the far right, you can also click on a link in the columns. This is the case in the redirects module, for example. You can edit by clicking on source_path column. I do not find this intuitive, but in cases like these it would be helpful<br />- The clipping of tables can be prevented by setting a fixed size (e.g. done in linkvalidator list). But in most other cases, it is not done, so you do get the scrollbar.<br />- The action buttons are on the far right and in combination with above can be clipped easily. This complies to general BE UI concept (also mentioned in styleguide extension).</p>
<a name="Example-1-Listing-of-references"></a>
<h2 >Example 1: Listing of references<a href="#Example-1-Listing-of-references" class="wiki-anchor">¶</a></h2>
<p><img src="http://forge.typo3.org/attachments/download/36780/ref1.png" alt="" loading="lazy" /></p>
<p>After scrolling down:</p>
<p><img src="http://forge.typo3.org/attachments/download/36779/ref2.png" alt="" loading="lazy" /></p>
<a name="Example-2-redirects-module"></a>
<h2 >Example 2: redirects module<a href="#Example-2-redirects-module" class="wiki-anchor">¶</a></h2>
<p><img src="http://forge.typo3.org/attachments/download/36778/redirects.png" alt="" loading="lazy" /></p>
<p>Here, there is also a horizontal scrollbar and content is cut off, but you can edit by clicking on the link in "Source path" column (not really intuitive because no visible indication what the link does).</p> TYPO3 Core - Bug #93912 (New): Avoid horizontal scrollbar for redirects modulehttp://forge.typo3.org/issues/939122021-04-13T08:48:19ZSybille Peterssypets@gmx.de
<p>If some URL targets are long, a horizontal scrollbar is displayed. This makes the action button invisible and you have to scroll down.</p>
<p>I think this is not very good from a usability point of view - it actually hides the action buttons.</p>
<p>We had the same problem in the linkvalidator list and switched to a fixed layout (where each column has a fixed width).</p>
<p>Another (better?) alternative would be to shorten both source and targets paths if they exceed a certain length.</p>
<a name="System"></a>
<h2 >System<a href="#System" class="wiki-anchor">¶</a></h2>
<ul>
<li>master (11-dev)</li>
<li>10.4.14</li>
</ul>
<p><img src="http://forge.typo3.org/attachments/download/36001/redirects1.png" alt="" loading="lazy" /></p>
<p><img src="http://forge.typo3.org/attachments/download/36002/redirects2.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #93540 (New): It is not clear which options extendToSubpages in page properties ...http://forge.typo3.org/issues/935402021-02-18T07:36:22ZSybille Peterssypets@gmx.de
<a name="Problems"></a>
<h2 >Problems<a href="#Problems" class="wiki-anchor">¶</a></h2>
<p>1. Not intuitive to see which fields are affected by extendToSubpages</p>
<p>extendToSubpages applies to property <strong>hidden</strong> (among others).</p>
<p>It does not apply to <strong>nav_hide</strong> .</p>
<p>The way the options are grouped currently is misleading. It does not make it clear, what extendToSubpages apply to. One could assume it applys to all the options in the section (which would not include hidden) or all option in the row (which might include start and stop, depending on how the page is resized) or in the "Access" tab.</p>
<p>I would suggest to apply extendToSubpages to all options in the "Access" tab (including nav_hide) and remove the separator.</p>
<p>Alternatively, move nav_hide to the "Behaviour" tab.</p>
<p>Or group the options differently.</p>
<a name="Desired-change"></a>
<h2 >Desired change<a href="#Desired-change" class="wiki-anchor">¶</a></h2>
<p>1. rethink which options should be overriden with extendToSubpages (nav_hide yes?, others: ...)<br />2. change gui: Easy to see which fields are affected by extendToSubpages<br />3. on child pages: do not make settings available which will have no effect (because overriden by parent page), see comment by Stefan P: <a class="external" href="https://forge.typo3.org/issues/93540#note-10">https://forge.typo3.org/issues/93540#note-10</a><br />4. improve docs</p>
<p>see also questions and suggestions below in comments.</p>
<p>current state:</p>
<p><img src="http://forge.typo3.org/attachments/download/35859/extendToSubpages.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #92972 (New): Softref parsers should take syntax format of field into accounthttp://forge.typo3.org/issues/929722020-12-02T11:08:42ZSybille Peterssypets@gmx.de
<a name="Suggestion"></a>
<h2 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h2>
<ul>
<li>make it possible to always set "format" for TCA column type "text" and "input" </li>
<li>use the format in the softref parsers</li>
</ul>
<a name="Explanation"></a>
<h2 >Explanation<a href="#Explanation" class="wiki-anchor">¶</a></h2>
<p>Currently, AFAIK, the softref parser does not evaluate what format the field has. Possible formats can be HTML (e.g. tt_content.bodytext), plain text, TypoScript (e.g. sys_template.config, sys_template.constants), comma separated list.</p>
<p>The <a href="https://docs.typo3.org/m/typo3/reference-tca/master/en-us/ColumnsConfig/Type/textT3editor.html#format" class="external">format</a> can already (partly) be set in TCA, but only if type is 'text' and 'renderType' is 't3editor', for example as 'typoscript' for sys_template.config.</p>
<p>Since t3editor is used only for typoscript it does not really seem to make sense that the format can be set for this renderType but not for renderType default.</p>
<blockquote>
<p>renderType='t3editor': System extension “t3editor” provides an enhanced textarea for TypoScript input</p>
</blockquote>
<blockquote>
<p>format: The value specifies the language t3editor should handle. Allowed values: css, html, javascript, php, typoscript, xml</p>
</blockquote>
<p>For tt_content.bodytext neither renderType nor format are set.</p>
<p>If this is handled consistently, you would not have to pass 'linklist' to the softref parser, but read this from format as well (e.g. for findRef_typolink()).</p>
<p>By being able to handle the formatting consistently in all softref parsers, it might be possible to simplify things and also avoid inconsistencies.</p>
<a name="Examples"></a>
<h1 >Examples:<a href="#Examples" class="wiki-anchor">¶</a></h1>
<p>Currently, URLs <strong>in comments</strong> in sys_template config or constants are added to the reference index, e.g.</p>
<pre>
sys_template.config:
# https://example.org
</pre>
<p>When saved, this record is created:</p>
<pre>
+----------------------------------+--------------+--------+--------+-------------+-------------+------------+---------+---------+-----------+-----------+---------+---------------------+
| hash | tablename | recuid | field | flexpointer | softref_key | softref_id | sorting | deleted | workspace | ref_table | ref_uid | ref_string |
+----------------------------------+--------------+--------+--------+-------------+-------------+------------+---------+---------+-----------+-----------+---------+---------------------+
| a7ad94098b4c8ea1293af92fcd8be9b5 | sys_template | 2 | config | | url | 2 | -1 | 0 | 0 | _STRING | 0 | https://example.org |
+----------------------------------+--------------+--------+--------+-------------+-------------+------------+---------+---------+-----------+-----------+---------+---------------------+
</pre>
<p>If TypoScript were parsed correctly, this should not happen.</p>
<p>(Not sure why URLs in TypoScript are added to reference index in the first place and whether this has any benefit).</p> TYPO3 Core - Bug #92541 (New): Text of flash message is misleading for JavaScript errorshttp://forge.typo3.org/issues/925412020-10-12T11:53:07ZSybille Peterssypets@gmx.de
<p>Example: Page tree error message</p>
<pre><code class="text syntaxhl" data-language="text">Page tree error
Got unexpected response from the server. Please check logs for details.
</code></pre>
<p>When I get this type of error, the logs are usually empty. This is usually a JavaScript error displayed in browser console.</p>
<p>It would be great if error message which recommends to look in logs is only given if error has been logged.</p>
<p>Would be great if user got a different hint if there has been a JavaScript error.</p> TYPO3 Core - Bug #91331 (New): List module: Mass editing of content shows permission error messag...http://forge.typo3.org/issues/913312020-05-07T13:06:50ZSybille Peterssypets@gmx.de
<a name="System"></a>
<h2 >System<a href="#System" class="wiki-anchor">¶</a></h2>
<ul>
<li>TYPO3 9.5.16</li>
</ul>
<a name="Reproduce"></a>
<h2 >Reproduce<a href="#Reproduce" class="wiki-anchor">¶</a></h2>
<p>In my example, German is the default language, English is the translation. The BE user should have only write access to records in English and not to records in the default language.</p>
<ol>
<li>Create page with several content elements and translate it to the target language</li>
<li>Create BE group and user with permissions for only 1 language (not the default language)</li>
<li>As this user, go to <strong>list</strong> module</li>
<li>Click <strong>"Page content"</strong></li>
<li>Use clipboard mode "Normal" and prepare to edit all content. </li>
<li>click "Edit all shown fields of the listed records"</li>
</ol>
<p>Now "mass editing" of all content elements on the page will be invoked (both languages).</p>
<a name="Actual-result"></a>
<h2 >Actual result<a href="#Actual-result" class="wiki-anchor">¶</a></h2>
<p>For each content element in the original language, there is an error message:</p>
<pre><code class="text syntaxhl" data-language="text">Sorry, you didn't have proper permissions to perform this change.
ERROR: Language was not allowed.
</code></pre>
<p><img src="http://forge.typo3.org/attachments/download/35208/error.png" alt="" loading="lazy" /></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>It is correct that we cannot edit the records in the original language, but that should not be an error. The error messages are misleading.</p>
<p>Technically, the error messages are correct since <strong>all</strong> records are edited. But from the point of view of usability, this should by default not happen IMHO. By default, only the records the editor has permissions to should be edited.</p>
<p>In any case, it is currently (afaik) not possible to choose for which language to do the mass-editing. You can either mass-edit all. Or you have to use clipboard mode and tediously select every single record you want to edit.</p> TYPO3 Core - Bug #90658 (New): The current value for "Global Configuration" that is displayed is ...http://forge.typo3.org/issues/906582020-03-06T11:42:11ZSybille Peterssypets@gmx.de
<a name="Reproduce"></a>
<h2 >Reproduce<a href="#Reproduce" class="wiki-anchor">¶</a></h2>
<p>Example: "Global Configuration" cookieSameSite: "strict" is shown even if "strict" has just been set to something else and saved</p>
<ol>
<li>Set [BE][cookieSameSite] to something other than strict in BE, e.g. "lax" or "none" </li>
<li>Save ("Write configuration" below)</li>
<li>"[BE][cookieSameSite] = strict" is still displayed in the header (the darkgrey section) for the option even though the new setting is shown in the select.</li>
</ol>
<p><img src="http://forge.typo3.org/attachments/download/34924/cookieSameSite.png" alt="" loading="lazy" /></p>
<p>After you reopen the "Installation-Wide" Options, the value is displayed correctly.</p> TYPO3 Core - Bug #88810 (New): Naming of admin vs. system maintainer privilege levels and modules...http://forge.typo3.org/issues/888102019-07-21T14:28:33ZSybille Peterssypets@gmx.de
<p>I find it confusing, that <strong>"admin"</strong> has access to <strong>SYSTEM</strong> module while <strong>system maintainer</strong> has additional access to <strong>ADMIN</strong> TOOLS (contrary to the admin).</p>
<p>Solution might be to switch the names for ADMIN TOOLS and SYSTEM module.</p>
<a name="admin-user"></a>
<h1 >admin user<a href="#admin-user" class="wiki-anchor">¶</a></h1>
<ul>
<li>is called admin in db: be_users.admin</li>
<li>is called admin in BE users form</li>
<li>has additional access to <strong>SYSTEM</strong> module (but not to ADMIN TOOLS)</li>
</ul>
<p><img src="http://forge.typo3.org/attachments/download/34424/admin.png" alt="" loading="lazy" /></p>
<a name="system-maintainer"></a>
<h2 >system maintainer<a href="#system-maintainer" class="wiki-anchor">¶</a></h2>
<ul>
<li>has additional access to "ADMIN TOOLS"</li>
</ul>
<p><img src="http://forge.typo3.org/attachments/download/34425/systemmaintainer.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #83970 (New): Localize / Synchronize buttons are missing for Text & media assetshttp://forge.typo3.org/issues/839702018-02-20T00:23:03ZSybille Peterssypets@gmx.de
<p>Tested with current master (9.2.0-dev).</p>
<p>If some "assets" are inserted into "Text & media" and translated (translate, not copy) and the elements in the original language are changed (order changed, new ones inserted etc.), I would expect the buttons "Localize all records" / "Synchronize with original language" to be displayed for the translation.</p>
<p>This does work with bootstrap carousel from bootstrap_package, but not with Text & Media.</p>
<p><img src="http://forge.typo3.org/attachments/download/33208/bootstrap.png" alt="" loading="lazy" /></p>
<p>May be missing TCA options 'showSynchronizationLink' and 'showAllLocalizationLink'?</p>