TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692022-12-19T13:15:42ZTYPO3 Forge
Redmine TYPO3 Core - Bug #99394 (Resolved): Update documentation for NewRecordViewHelperhttp://forge.typo3.org/issues/993942022-12-19T13:15:42ZGuido Schmechel
<p>Not all examples were adapted when copy/pasting from EditRecordViewHelper.</p>
<p>Documentation: <a class="external" href="https://docs.typo3.org/other/typo3/view-helper-reference/main/en-us/typo3/backend/latest/Link/NewRecord.html">https://docs.typo3.org/other/typo3/view-helper-reference/main/en-us/typo3/backend/latest/Link/NewRecord.html</a><br />File: typo3/sysext/backend/Classes/ViewHelpers/Link/NewRecordViewHelper.php</p> TYPO3 Core - Bug #99383 (Resolved): Filemount display in BE group modal too narrowhttp://forge.typo3.org/issues/993832022-12-15T22:53:56ZGuido Schmechel
<ul>
<li>Edit a backend user</li>
<li>Jump to "Mount and workspaces" tab</li>
<li>Select a group and edit a group<br />=> A small popup opens</li>
</ul>
<p>If I now want to change a filemount inside this popup, the modal for filemounts opens, which is not displayed cleanly in width.</p> TYPO3 Core - Bug #99344 (Closed): Use correct flag of zimbabwehttp://forge.typo3.org/issues/993442022-12-12T10:21:31ZGuido Schmechel
<p><a class="external" href="https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Resources/Public/Icons/Flags/ZW.png">https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Resources/Public/Icons/Flags/ZW.png</a></p>
<p>The flag of Andorra is currently being used incorrectly: <a class="external" href="https://en.wikipedia.org/wiki/Flag_of_Andorra">https://en.wikipedia.org/wiki/Flag_of_Andorra</a></p>
<p>=> <a class="external" href="https://en.wikipedia.org/wiki/Flag_of_Zimbabwe">https://en.wikipedia.org/wiki/Flag_of_Zimbabwe</a></p> TYPO3 Core - Bug #95391 (Closed): MFA label is not translatedhttp://forge.typo3.org/issues/953912021-09-28T19:51:10ZGuido Schmechel
<p>Context: admin user - NO MFA. Setup Time Based Password => <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/71132">https://review.typo3.org/c/Packages/TYPO3.CMS/+/71132</a></p>
<p>Loggedin successfully and i got a flash message:</p>
<p>"MFA setup successful" <br />"You have successfully activated MFA provider LLL:EXT:core/Resources/Private/Language/locallang_mfa_provider.xlf:totp.title. This provider was also automatically set as your default provider. You can change this at any time in your user settings."</p> TYPO3 Core - Bug #94048 (Closed): LanguagePackCommand isn't schedulablehttp://forge.typo3.org/issues/940482021-05-03T21:28:58ZGuido Schmechel
<p>Regerssion from <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/67635">https://review.typo3.org/c/Packages/TYPO3.CMS/+/67635</a>. Only for master (v11)</p> TYPO3 Core - Bug #89328 (Closed): Auto redirect does not respect language hosthttp://forge.typo3.org/issues/893282019-10-01T21:35:04ZGuido Schmechel
<p>Source host doesnt use language detection: <a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/redirects/Classes/Service/SlugService.php#L171">https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/redirects/Classes/Service/SlugService.php#L171</a></p>
<p>Should be similar to: <a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/redirects/Classes/Service/SlugService.php#L157">https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/redirects/Classes/Service/SlugService.php#L157</a></p> TYPO3 Core - Bug #89327 (Closed): Auto redirect: Could not resolve target pagehttp://forge.typo3.org/issues/893272019-10-01T21:10:55ZGuido Schmechel
<p><strong>Scenario:</strong><br />I change a slug in the page properties. Example: "test1" (source) to "test2" (target). The redirect has been added.</p>
<p><strong>Problem:</strong><br />If i call "https://example.com/test1" i got this message "The page did not exist or was inaccessible. Reason: The requested page does not exist" The target has been added as value "/test2" and not as "t3://page?uid=3"</p>
<p><strong>Error message in target field</strong><br />"not implemented type unknown"</p>
<p><strong>Possible solution</strong><br />Maybe its a better way to use the page id?<br />Code: <a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/redirects/Classes/Service/SlugService.php#L155">https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/redirects/Classes/Service/SlugService.php#L155</a></p> TYPO3 Core - Bug #88939 (Closed): Custom CacheAction cannot send success state and custom flash m...http://forge.typo3.org/issues/889392019-08-08T17:44:30ZGuido Schmechel
<p>Content:<br />Add a cacheAction via $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['additionalBackendItems']['cacheActions']. Everything is fine and the cache icon is displayed in the topbar. Sending a JsonResponse via interface:</p>
<pre><code class="php syntaxhl" data-language="php"> <span class="cd">/**
* @param ServerRequestInterface $request
* @return ResponseInterface
*/</span>
<span class="k">public</span> <span class="k">function</span> <span class="n">flush</span><span class="p">(</span><span class="kt">ServerRequestInterface</span> <span class="nv">$request</span><span class="p">):</span> <span class="kt">ResponseInterface</span>
<span class="p">{</span>
<span class="k">return</span> <span class="k">new</span> <span class="nc">JsonResponse</span><span class="p">([</span><span class="s1">'success'</span> <span class="o">=></span> <span class="kc">true</span><span class="p">]);</span>
<span class="p">}</span>
</code></pre>
<p>We get a red FlashMessage with the hardcoded "An error occurred while clearing the cache. It is likely not all caches were cleared as expected." text.</p>
<p>The message is thrown from <a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/master/Build/Sources/TypeScript/backend/Resources/Public/TypeScript/Toolbar/ClearCacheMenu.ts#L72">https://github.com/TYPO3/TYPO3.CMS/blob/master/Build/Sources/TypeScript/backend/Resources/Public/TypeScript/Toolbar/ClearCacheMenu.ts#L72</a> because we have a response. It does not matter what is inside, as you can see.</p>
<p>Solution:<br />We need a proper solution for this typescript case. Luckily we have a similar solution here: <a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/master/Build/Sources/TypeScript/recordlist/Resources/Public/TypeScript/ClearCache.ts#L67">https://github.com/TYPO3/TYPO3.CMS/blob/master/Build/Sources/TypeScript/recordlist/Resources/Public/TypeScript/ClearCache.ts#L67</a></p> TYPO3 Core - Bug #87821 (Closed): Form Framework has problems with Windows Line Endingshttp://forge.typo3.org/issues/878212019-03-02T11:24:08ZGuido Schmechel
<p>Form Framework stops the output of forms when using Windows Line Endings, e.g. due to a faulty upload. The editor gets no indication and the error is hard to find as an integrator.</p>
<p>To prevent this, chr (13) can be removed from the metadata:<br /><a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/form/Classes/Mvc/Persistence/FormPersistenceManager.php#L687">https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/form/Classes/Mvc/Persistence/FormPersistenceManager.php#L687</a></p>
<p>How can you test it?<br />Just build an simple form yaml config and change the line ending via editor (e.g. PHP Storm) from "LF" to "CRLF"</p> TYPO3 Core - Bug #87683 (Closed): TitleTagProvider always get the cached entryhttp://forge.typo3.org/issues/876832019-02-10T22:10:25ZGuido Schmechel
<p>Given scenario:<br />I have a searchresult page (e.g. UID 42). The post requests variables are used for generating title tag and meta description. There is a custom TitleTagProvider which deliver a custom title, e.g. "Hello world 123" or if another search is correct "Hello world 456"</p>
<p>Btw: The searchresultAction is uncached.</p>
<p>Output:<br />Case 1: "Hello world 123" <br />Case 2: "Hello world 123"</p>
<p>Expected Result:<br />Case 1: "Hello world 123" <br />Case 2: "Hello world 456"</p>
<p>Problem:<br />TYPO3 saves title Tag, also custom Provider, in typo3/sysext/core/Classes/PageTitle/PageTitleProviderManager.php $cacheIdentifier. It never looks for the content of the titleTag. <br /><pre><code class="php syntaxhl" data-language="php"><span class="nv">$cacheIdentifier</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-></span><span class="nf">getTypoScriptFrontendController</span><span class="p">()</span><span class="o">-></span><span class="n">newHash</span> <span class="mf">.</span> <span class="s1">'-titleTag-'</span> <span class="mf">.</span> <span class="nv">$provider</span><span class="p">;</span>
</code></pre></p>
<p>Possible solution:<br />Integrate (hashed?) titleTag content in the cacheIdentifier.</p>
<p><a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/core/Classes/PageTitle/PageTitleProviderManager.php#L69">https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/core/Classes/PageTitle/PageTitleProviderManager.php#L69</a></p>
<p>Same problem exists for the MetaTags.</p> TYPO3 Core - Bug #87500 (Closed): Site Configuration with an empty static route is possiblehttp://forge.typo3.org/issues/875002019-01-20T20:54:19ZGuido Schmechel
<p><strong>Error</strong></p>
<p>The problem occurs when opening the sitemap.</p>
<pre><code class="php syntaxhl" data-language="php"><span class="p">(</span><span class="mi">1</span><span class="o">/</span><span class="mi">1</span><span class="p">)</span> <span class="nc">TypeError</span>
<span class="nc">Argument</span> <span class="mi">1</span> <span class="n">passed</span> <span class="n">to</span> <span class="nc">TYPO3\CMS\Core\LinkHandling\LinkService</span><span class="o">::</span><span class="nf">resolve</span><span class="p">()</span> <span class="n">must</span> <span class="n">be</span> <span class="n">of</span> <span class="n">the</span> <span class="n">type</span> <span class="n">string</span><span class="p">,</span> <span class="kc">null</span> <span class="n">given</span><span class="p">,</span> <span class="n">called</span> <span class="n">in</span> <span class="nc">\public\typo3\sysext\frontend\Classes\Middleware\StaticRouteResolver</span><span class="mf">.</span><span class="n">php</span> <span class="n">on</span> <span class="n">line</span> <span class="mi">133</span>
</code></pre>
<p><strong>Steps to reproduce</strong></p>
<ul>
<li>Add an Static Route in Site Configuration</li>
<li>Change "Route Type" to "Page, File" </li>
<li>Backend is reloaded</li>
<li>Click "Close" to abort the adding of a route</li>
</ul>
<p>As it stands, the mandatory field check is not performed by clicking on "Close".</p> TYPO3 Core - Bug #87337 (Closed): ExtbasePluginEnhancer does not use a custom controller configur...http://forge.typo3.org/issues/873372019-01-05T19:25:17ZGuido Schmechel
<p><strong>Context</strong><br />I have a standard extbase plugin. Actions are list, detail and city.</p>
<p><strong>Problem</strong><br />If defaultController and _controller do not match from a route, the URL will not build up cleanly. In my case, he always uses "list" to generate the URL.</p>
<p><strong>Solution</strong><br />When verifying each configuration in the ExtbasePluginEnhancer, the controller will not overwrite the current configuration. Only the default controller is used.</p>
<pre><code class="php syntaxhl" data-language="php"><span class="k">if</span> <span class="p">(</span><span class="o">!</span><span class="k">empty</span><span class="p">(</span><span class="nv">$configuration</span><span class="p">[</span><span class="s1">'_controller'</span><span class="p">]))</span> <span class="p">{</span>
<span class="nv">$this</span><span class="o">-></span><span class="nf">applyControllerActionValues</span><span class="p">(</span>
<span class="nv">$configuration</span><span class="p">[</span><span class="s1">'_controller'</span><span class="p">],</span>
<span class="nv">$originalParameters</span><span class="p">[</span><span class="nv">$this</span><span class="o">-></span><span class="n">namespace</span><span class="p">]</span>
<span class="p">);</span>
<span class="p">}</span>
</code></pre>
<p><strong>Route Enhancer config</strong></p>
<pre><code class="php syntaxhl" data-language="php"><span class="n">routeEnhancers</span><span class="o">:</span>
<span class="nc">DetailPoi</span><span class="o">:</span>
<span class="n">type</span><span class="o">:</span> <span class="nc">Extbase</span>
<span class="n">extension</span><span class="o">:</span> <span class="nc">AyacooPoi</span>
<span class="n">plugin</span><span class="o">:</span> <span class="nc">Poi</span>
<span class="n">routes</span><span class="o">:</span>
<span class="o">-</span> <span class="p">{</span> <span class="n">routePath</span><span class="o">:</span> <span class="s1">'restaurant/{slug}'</span><span class="p">,</span> <span class="n">_controller</span><span class="o">:</span> <span class="s1">'Poi::detail'</span><span class="p">,</span> <span class="n">_arguments</span><span class="o">:</span> <span class="p">{</span><span class="s1">'slug'</span> <span class="o">:</span> <span class="s1">'poi'</span><span class="p">}</span> <span class="p">}</span>
<span class="o">-</span> <span class="p">{</span> <span class="n">routePath</span><span class="o">:</span> <span class="s1">'stadt/{cityTitle}'</span><span class="p">,</span> <span class="n">_controller</span><span class="o">:</span> <span class="s1">'Poi::city'</span><span class="p">,</span> <span class="n">_arguments</span><span class="o">:</span> <span class="p">{</span><span class="s1">'cityTitle'</span> <span class="o">:</span> <span class="s1">'city'</span><span class="p">}</span> <span class="p">}</span>
<span class="n">defaultController</span><span class="o">:</span> <span class="s1">'Poi::list'</span>
<span class="n">requirements</span><span class="o">:</span>
<span class="n">poi</span><span class="o">:</span> <span class="s1">'\d+'</span>
<span class="n">city</span><span class="o">:</span> <span class="s1">'\d+'</span>
<span class="n">aspects</span><span class="o">:</span>
<span class="n">slug</span><span class="o">:</span>
<span class="n">type</span><span class="o">:</span> <span class="nc">PersistedAliasMapper</span>
<span class="n">tableName</span><span class="o">:</span> <span class="s1">'tx_ayacoopoi_domain_model_poi'</span>
<span class="n">routeFieldName</span><span class="o">:</span> <span class="s1">'slug'</span>
<span class="n">cityTitle</span><span class="o">:</span>
<span class="n">type</span><span class="o">:</span> <span class="nc">PersistedAliasMapper</span>
<span class="n">tableName</span><span class="o">:</span> <span class="s1">'tx_ayacoopoi_domain_model_poi'</span>
<span class="n">routeFieldName</span><span class="o">:</span> <span class="s1">'city'</span>
</code></pre> TYPO3 Core - Bug #87333 (Closed): Slug fieldSeparator default value collides with symfony strict ...http://forge.typo3.org/issues/873332019-01-05T09:40:59ZGuido Schmechel
<p><strong>Context</strong></p>
<p>I combine two fields via TCA Slug ['city', 'street']. TYPO3 builds the slug correctly to e.g. "cologne/streetname". This is also displayed in the backend in the slug field.</p>
<pre><code class="php syntaxhl" data-language="php"> <span class="s1">'slug'</span> <span class="o">=></span> <span class="p">[</span>
<span class="s1">'exclude'</span> <span class="o">=></span> <span class="kc">true</span><span class="p">,</span>
<span class="s1">'label'</span> <span class="o">=></span> <span class="s1">'URL Segment'</span><span class="p">,</span>
<span class="s1">'config'</span> <span class="o">=></span> <span class="p">[</span>
<span class="s1">'type'</span> <span class="o">=></span> <span class="s1">'slug'</span><span class="p">,</span>
<span class="s1">'generatorOptions'</span> <span class="o">=></span> <span class="p">[</span>
<span class="s1">'fields'</span> <span class="o">=></span> <span class="p">[</span><span class="s1">'city'</span><span class="p">,</span> <span class="s1">'street'</span><span class="p">],</span>
<span class="s1">'replacements'</span> <span class="o">=></span> <span class="p">[</span>
<span class="s1">'/'</span> <span class="o">=></span> <span class="s1">''</span><span class="p">,</span>
<span class="s1">'&'</span> <span class="o">=></span> <span class="s1">''</span>
<span class="p">],</span>
<span class="p">],</span>
<span class="s1">'fallbackCharacter'</span> <span class="o">=></span> <span class="s1">'-'</span><span class="p">,</span>
<span class="s1">'eval'</span> <span class="o">=></span> <span class="s1">'uniqueInPid'</span><span class="p">,</span>
<span class="p">],</span>
<span class="p">],</span>
</code></pre>
<p><strong>Problem</strong></p>
<p>If i call a list action which call this slug via f:link.page I get this error message:</p>
<pre>
Parameter "tx_ayacoopoi_poi__poi" for route "tx_ayacoopoi_poi_0" must match "[^/]++" ("cologne/streetname" given) to generate a corresponding URL.
</pre>
<p>I have not defined a field separator in the TCA config and so a slash is used by the code => <a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/core/Classes/DataHandling/SlugHelper.php#L185">https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/core/Classes/DataHandling/SlugHelper.php#L185</a></p>
<p>Symfony routing is in strict mode and so the slash isn't allowed.</p>
<p><strong>Route Enhancer</strong></p>
<pre><code class="yaml syntaxhl" data-language="yaml"><span class="na">routeEnhancers</span><span class="pi">:</span>
<span class="na">DetailPoi</span><span class="pi">:</span>
<span class="na">type</span><span class="pi">:</span> <span class="s">Extbase</span>
<span class="na">extension</span><span class="pi">:</span> <span class="s">AyacooPoi</span>
<span class="na">plugin</span><span class="pi">:</span> <span class="s">Poi</span>
<span class="na">routes</span><span class="pi">:</span>
<span class="pi">-</span> <span class="pi">{</span> <span class="nv">routePath</span><span class="pi">:</span> <span class="s1">'</span><span class="s">{slug}'</span><span class="pi">,</span> <span class="nv">_controller</span><span class="pi">:</span> <span class="s1">'</span><span class="s">Poi::detail'</span><span class="pi">,</span> <span class="nv">_arguments</span><span class="pi">:</span> <span class="pi">{</span><span class="s1">'</span><span class="s">slug'</span> <span class="pi">:</span> <span class="s1">'</span><span class="s">poi'</span><span class="pi">}</span> <span class="pi">}</span>
<span class="na">defaultController</span><span class="pi">:</span> <span class="s1">'</span><span class="s">Poi::detail'</span>
<span class="na">aspects</span><span class="pi">:</span>
<span class="na">slug</span><span class="pi">:</span>
<span class="na">type</span><span class="pi">:</span> <span class="s">PersistedAliasMapper</span>
<span class="na">tableName</span><span class="pi">:</span> <span class="s1">'</span><span class="s">tx_ayacoopoi_domain_model_poi'</span>
<span class="na">routeFieldName</span><span class="pi">:</span> <span class="s1">'</span><span class="s">slug'</span>
<span class="na">routeValuePrefix</span><span class="pi">:</span> <span class="s1">'</span><span class="s">/'</span>
</code></pre> TYPO3 Core - Bug #86277 (Closed): Editlock blocks edit button also for adminhttp://forge.typo3.org/issues/862772018-09-16T19:38:48ZGuido Schmechel
<p>Affected version<br />9.5-dev</p>
Steps to reproduce:
<ul>
<li>Edit page properties</li>
<li>Set editlock to true</li>
<li>Save</li>
</ul>
<p>Now the edit button is hidden because of the editlock property.</p> TYPO3 Core - Bug #84838 (Rejected): Empty AdditionalConfiguration.php breaks install toolhttp://forge.typo3.org/issues/848382018-04-22T19:09:18ZGuido Schmechel
<p>If you add an "empty" AdditionalConfiguration.php with only one line, "<?php" the install tool isn't callable.</p>
<p>/install.php?install[controller]=layout&install[context]=backend&install[action]=executeSilentConfigurationUpdate&_=1524415847672 add this one line to the JsonResponse. Backend response "Something went wrong. Please use Check for broken extensions to see if a loaded extension breaks this part of the install tool and unload it." in the view.</p>