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 - Feature #102644 (New): Make it easier to restrict uploadable file types / extensions...http://forge.typo3.org/issues/1026442023-12-09T22:07:09ZSybille Peterssypets@gmx.de
<p>I want to prevent <strong>additional</strong> unwanted files from being uploaded, such as .exe, .zip, .iso etc. (this should be configurable). Right now, I can only do it AFAIK by changing the regex in fileDenyPattern.</p>
<a name="My-feature-reqeust"></a>
<h2 >My feature reqeust<a href="#My-feature-reqeust" class="wiki-anchor">¶</a></h2>
<ul>
<li>add a "safe" configuration, so you can add <strong>additional</strong> file extensions, without having to change fileDenyPattern. This does not even have to be a regex or be added to fileDenyPattern, it could be a comma separated list of file extensions, which is used in FileNameValidator</li>
<li>make it possible to use "explicit allow" instead of "explicit deny" here. This should probably not be the default yet, but could be in the future.</li>
</ul>
<a name="Background"></a>
<h2 >Background<a href="#Background" class="wiki-anchor">¶</a></h2>
<p>Currently, there is a setting which is a bit hidden: $GLOBALS['TYPO3_CONF_VARS']['BE']['fileDenyPattern'], is used in FileNameValidator.</p>
<p>It is hidden, because it is not in the Default configuration and not visible when editing "Global configuration" in the BE.</p>
<p>I assume, that is for security reasons, that you don't accidentally mess up the regular expression, making the system less secure. In particular, it should not be possible to upload .php files, .htaccess files etc.</p>
<p>But, this also makes it difficult, in case you want to be <em>more restrictive</em> (!). You have to first find the hidden option and then edit the regex, hoping you don't break anything.</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 - Feature #101077 (New): Improve administrative handling of "Anonymize IP Adresses"http://forge.typo3.org/issues/1010772023-06-15T05:24:09ZSybille Peterssypets@gmx.de
<ul>
<li>currently it is only possible to select 1 table in the task (but more can be configured in ext_localconf.php)</li>
<li>the task is a scheduler task which means you have to create a scheduler task first, you can't just run it from the console (which means extra work and you can't (easily) store the configuration in a Git repo)</li>
</ul>
<a name="Sugestions"></a>
<h2 >Sugestions<a href="#Sugestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>make a Symfony command out of it</li>
<li>make it possible to run it with "all configured tables" which would use all tables in $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['scheduler']['tasks'][self::class]['options']</li>
</ul>
<p>In the "Table garbage collection" task there is a checkbox "Clean all available tables"</p>
<a name="Side-note"></a>
<h2 >Side note<a href="#Side-note" class="wiki-anchor">¶</a></h2>
<p>It is unclear to me whether all current scheduler tasks will be migrated to Symfony commands in the future.</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 - Feature #99384 (New): Dynamic refresh instead of save and reload in backend forms wi...http://forge.typo3.org/issues/993842022-12-16T07:37:00ZSybille Peterssypets@gmx.de
<p>In TCA it is possible to make form fields disappear based on the conditions of other fields (displayCond).</p>
<p>For this to work, you have to add a "reload" to the field it depends on so that the form will be saved and reloaded.</p>
<a name="problems"></a>
<h3 >problems<a href="#problems" class="wiki-anchor">¶</a></h3>
<ul>
<li>the dialog asking if one should save and reload is annoying when one is still filling out the fields</li>
<li>in some cases it is unnecessarily displayed (e.g. if some fields are displayed depending on what is seletected in a list and not all changes in the list need the reload)</li>
<li>the field is saved even though the editor is not done</li>
<li>feels clunky and not editor friendly</li>
</ul>
<p><img src="http://forge.typo3.org/attachments/download/37638/dialog_refresh_save_cancel.png" alt="" loading="lazy" /></p>
<a name="Preferred-change"></a>
<h3 >Preferred change<a href="#Preferred-change" class="wiki-anchor">¶</a></h3>
<p>Suggested alternative would be to do this behaviour in JavaScript in the core so the form is dynamically displayed.</p>
<a name="Alternatives-as-developer"></a>
<h3 >Alternatives as developer<a href="#Alternatives-as-developer" class="wiki-anchor">¶</a></h3>
<p>1. use displayCond and reload for the fields which should be displayed conditionally. Which means a dialog will appear on every change asking if we should continue, even for the selections where it is not relevant<br />2. Just show all the fields which clutters the user interface with unused options.<br />3. Write the code to display fields conditionally in JavaScript yourself which is extra work and makes the extensions difficult to maintain. For example if you change the field type you might have to adapt the JavaScript code. <br />4. Other solutions???</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 - Task #94325 (New): Naming conventions for extensions for extending Page TSconfighttp://forge.typo3.org/issues/943252021-06-12T10:30:10ZSybille Peterssypets@gmx.de
<p>What namespace should extensions use for naming the TSconfig settings (e.g. "tx_myext", "mod.tx_myext", "user.tx_myext" ...).</p>
<p>Should core and extension settings be separated?</p>
<p>How the namespace is also affects how they are displayed in "Info > Page TSconfig" (the order and if they can be selected in the select field"</p>
<p>Also, ideally the core settings should be unified in using uppercase / lowercase in the top-level "objects", currently we have a mix of all uppercase and all lowercase. There may be some deeper meaning or reason I am not aware of, but from what I wrote in <a class="issue tracker-1 status-3 priority-4 priority-default closed child" title="Bug: Info => Page TSconfig: Sort order (Resolved)" href="http://forge.typo3.org/issues/94321">#94321</a>:</p>
<blockquote>
For basic coredev installation it looks like this:
<ul>
<li>TCEFORM</li>
<li>TCEMAIN</li>
<li>mod<br />... I think it would be better to (long term) unify the naming so that the top-level items are all lowercase.<br />In TypoScript, by convention the type of the "objects" are uppercase (e.g. PAGE) and the "objects" themselves are lowercase. So I think TCEFORM, TCEMAIN etc. should be changed to lowercase. (This sometimes mixing of type and "object" and inconsistent usage of terms is something which was not just noticed and pointed out by me, we already make some changes in the "TypoScript Reference" to address this).</li>
</ul>
</blockquote>
<a name="Requirements"></a>
<h2 >Requirements<a href="#Requirements" class="wiki-anchor">¶</a></h2>
<p>1. Make it possible to easily find the settings in the filter options in "Info > Page TSconfig". <br />2. All extension TSconfig should be grouped together, not found in various places<br />3. They should be grouped logically<br />4. use an intuitive convention that is easy to remember</p>
<p>The difficulty is finding a good namespace. In mod, you have the namespaces per module, e.g mod.web_info, but you might rather want to group by extension key or group by third party extensions in general.</p>
<a name="Examples-for-existing-TSconfig"></a>
<h2 >Examples for existing TSconfig:<a href="#Examples-for-existing-TSconfig" class="wiki-anchor">¶</a></h2>
<p>Examples for extension TSconfig and how they are displayed.</p>
<ul>
<li>news: tx_news: only appears in "all" (this is what news uses)</li>
<li>linkvalidator: mod.linkvalidator: appears in "all" and in "mod" </li>
<li>direct_mail: mod.web_modules.dmail : appears in "Module: Web>Modules"</li>
</ul> TYPO3 Core - Feature #94278 (New): Make it possible to extend the creation of the translation but...http://forge.typo3.org/issues/942782021-06-04T10:46:35ZSybille Peterssypets@gmx.de
<p><strong>Update</strong> : Issue title and text was updated: <em>PageLayoutView</em> is no longer used in 11 and only used in 9 or 10 if feature toggle <em>fluidBasedPageModule</em> is not set.</p>
<p>Now, the functionality can be found in</p>
<ul>
<li>EXT:backend/Classes/View/BackendLayout/Grid/LanguageColumn.php</li>
<li>EXT:backend/Resources/Private/Partials/PageLayout/LanguageColumns.html</li>
</ul>
<hr />
<p>In any case, it would be nice to be able to extend the creation of the language button.</p>
<a name="Requirements"></a>
<h2 >Requirements<a href="#Requirements" class="wiki-anchor">¶</a></h2>
<p>Besides the "copy" and "translate" button and description, it should be possible to add additional buttons and they should be made configurable.</p>
<p>e.g. configure</p>
<pre>
# already existing core page TSconfig
mod.web_layout.localization.enableTranslate
mod.web_layout.localization.enableCopy
# NEW
mod.web_layout.localization.enableDeeplTranslate
...
</pre>
<a name="What-is-missing"></a>
<h2 >What is missing<a href="#What-is-missing" class="wiki-anchor">¶</a></h2>
<ul>
<li>it is possible to override LanuageColumn.html, but there you would need access to the additional TSconfig.</li>
</ul>
<a name="Possible-Application"></a>
<h2 >Possible Application<a href="#Possible-Application" class="wiki-anchor">¶</a></h2>
<p>Currently the translation deepltranslate / wv_deepltranslate extends the translation mode buttons. But they are not made configurable. TYPO3 already has functionality to configure the buttons via TSConfig (enableTranslate, enableCopy).</p>
<p>Currently, wv_translate always shows all the extra buttons which means 2 buttons for Google Translate and 2 buttons for DeepL translate.</p>
<p>But it is not possible to make this configurable currently - the buttons are always displayed.</p>
<p>More information is here: <a class="external" href="https://github.com/web-vision/wv_deepltranslate/issues/8#issuecomment-854608662">https://github.com/web-vision/wv_deepltranslate/issues/8#issuecomment-854608662</a></p>
<p><img src="http://forge.typo3.org/attachments/download/36113/deepl.png" alt="" loading="lazy" /></p> TYPO3 Core - Feature #93799 (New): Enhance public API for some basic page operations (pages, page...http://forge.typo3.org/issues/937992021-03-22T15:35:16ZSybille Peterssypets@gmx.de
<p>Recently, I had been wanting to add some basic functionality to an extension and every time it wasn't something I had done before or was already documented, I ended up browsing through the core, finding the functionality, but only in internal classes and ended up copy-pasting or writing my own code from scratch (even though the functionality exists in the core).</p>
<p>Also, it is not so easy to figure some things out. I find e.g. the command controllers, upgrade wizards, etc. very well documented, but for some things you are on your own and end up browsing or stepping through the core (which is ok, but sometimes you need to understand the internal workings which is not always intuitive).</p>
<p>Currently, we have several internal classes, which supply general functionality which might be useful for extensions.</p>
<p>Examples:</p>
<ul>
<li>get all mount points (for current user). Something similar exists in TreeController::getAllEntryPointPageTrees or getAllowedMountPoints()</li>
<li>does current user have permission to page x?</li>
<li>get all (sub)pages of a page, exists in linkvalidator: PagesRepository::getAllSubpagesForPage() and also doesRootLineContainHiddenPages() - might make sense to move this to a more central place</li>
<li>get all doktypes (that are in use): TreeController::getDokTypes</li>
<li>TreeController:getDomainNameForPage</li>
<li>TreeController:isDragMoveAllowed</li>
</ul>
<p>In fact, a few of the functions in TreeController look like they might be resuable. Some things already exist in BackendUtility class.</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 - Feature #92193 (New): Make console commands (directly) visible in list of scheduler ...http://forge.typo3.org/issues/921932020-09-04T09:55:26ZSybille Peterssypets@gmx.de
<p>When you create a new task in the scheduler, you can see a list of available tasks in Class.</p>
<p><img src="http://forge.typo3.org/attachments/download/35430/scheduler1.png" alt="" loading="lazy" /></p>
<p>Here, you have to select "Execute console commands" to see a list of the console commands.</p>
<p>This makes the usability a bit clunky, because you do not have a full list of what is available. You have to choose "console command" and only then do you see the console commands (or not).</p>
<p>Extension authors may want to make their schedulable tasks available as console commands because this adds more flexibility (as they can be called on the console or via cron directly). However, having the commands then be a bit hidden is a downside of this.</p>
<a name="Possible-solution"></a>
<h2 >Possible solution<a href="#Possible-solution" class="wiki-anchor">¶</a></h2>
<ul>
<li>add the console commands to the list of scheduler tasks to be visible like any other scheduler task.</li>
</ul> TYPO3 Core - Feature #91303 (New): Make it possible to configure fieldControls for TCA / Flexform...http://forge.typo3.org/issues/913032020-05-05T09:39:36ZSybille Peterssypets@gmx.de
<p>For a "select" type there are several renderTypes.</p>
<p>For the <a href="https://docs.typo3.org/m/typo3/reference-tca/master/en-us/ColumnsConfig/Type/Select.html#properties-rendertype-selectmultiplesidebyside" class="external">renderType=selectMultipleSideBySide</a>, you can add additional fieldControls, for the <a href="https://docs.typo3.org/m/typo3/reference-tca/master/en-us/ColumnsConfig/Type/Select.html#properties-rendertype-selectcheckbox" class="external">renderType=selectCheckBox</a> you cannot. (The fieldControl is missing in the documentation and also it does not get displayed if you try it in a FlexForm, for the selectMultipleSideBySide is does work however). You also cannot modify the default fieldControl (as far as I know).</p>
<p>The renderType=selectCheckBox already has a default fieldControl "ResetSelection", maybe this is the reason, it is not possible.</p>
<p>I currently have a usecase where it would be very useful to add additional fieldControls for this type (in a Flexform).</p>
<p>I think it might also be useful to be able to add fieldControls for other types.</p>