TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692018-11-30T17:47:27ZTYPO3 Forge
Redmine TYPO3 Core - Bug #87049 (Closed): Workspace Preview Info is rendered with pointer-events: nonehttp://forge.typo3.org/issues/870492018-11-30T17:47:27ZLorenz Ulrich
<p>The Workspace Preview information contains a link to leave the Preview mode:</p>
<p><img src="http://forge.typo3.org/attachments/download/33979/workspace-preview-info.jpg" alt="" loading="lazy" /></p>
<p>The container has the CSS style <code>pointer-events: none</code> which seemingly doesn't allow the link to be clicked.</p>
<p>I'm not sure why this is the case. I assume the motivation was not to block any essential parts of the sites during Workspace Preview.</p> TYPO3 Core - Bug #82750 (Closed): Workspace preview doesn't preview MM relations properlyhttp://forge.typo3.org/issues/827502017-10-12T19:07:39ZLorenz Ulrich
<p>If the workspace preview is used to preview a record of an Extbase extension having an m:n relation, the relation data isn't displayed properly in the stage preview.</p>
<p>The stage preview doesn't show a relation added to an item in a workspace while it is correctly saved in the database and also correctly applied if published.</p>
<p>So I assume the reason for the preview not working properly must be a bug in Extbase.</p>
<p>I created an extension to demonstrate the issue:</p>
<p><a class="external" href="https://github.com/visol/ext-group_mm_workspaces_test">https://github.com/visol/ext-group_mm_workspaces_test</a></p>
<p>The Workspace preview only works in this case if <a class="external" href="https://review.typo3.org/#/c/52791/">https://review.typo3.org/#/c/52791/</a> is applied.</p> TYPO3 Core - Bug #75484 (Rejected): Error in file list module when having a read-only filemount f...http://forge.typo3.org/issues/754842016-04-10T21:04:44ZLorenz Ulrich
<p>Test case:</p>
<ul>
<li>Assign a normal filemount, e.g. for 1:/test (Folder test in storage 1) to a user</li>
<li>Set a read-only filemount for the root path of storage 1: <code>options.folderTree.altElementBrowserMountPoints = 1:/</code></li>
</ul>
<p>This is the case in an environment where editors only can manipulate certain folders (e.g. of their departments), but should be able to read/use all file of the website.</p>
<p>Now, after switching to a non-admin user that has both filemounts assigned, a click to "test" in the File List module leads to an "endless" call that is terminated at max_execution_time.</p>
<p>This problem was introduced with <a class="external" href="https://review.typo3.org/#/c/39898">https://review.typo3.org/#/c/39898</a> in <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Prevent information disclosure in file list (Closed)" href="http://forge.typo3.org/issues/67245">#67245</a>. Before (or without) that change, this setup works/worked fine.</p> TYPO3 Core - Bug #72116 (Closed): Files without references still show a warning before deletinghttp://forge.typo3.org/issues/721162015-12-09T09:48:48ZLorenz Ulrich
<p>I have some files in the File module that have no references with is correctly shown in the list:</p>
<p><img src="http://forge.typo3.org/attachments/download/30274/file-reference-1.png" alt="" loading="lazy" /></p>
<p>When I look at the detail view of the file, I see a reference nevertheless - the reference from the sys_file_metadata record to this file:</p>
<p><img src="http://forge.typo3.org/attachments/download/30276/file-reference-2.png" alt="" loading="lazy" /></p>
<p>Now when I'm trying to delete this file, which is never used in content, I still get the warning that there is one reference:</p>
<p><img src="http://forge.typo3.org/attachments/download/30275/file-reference-3.png" alt="" loading="lazy" /></p>
<p>I assume that the problem is that the JavaScript dialog is based on the total number of references without considering that every file has a sys_file_metadata record.</p> TYPO3 Core - Bug #71973 (Closed): Sorting of file relations doesn't have any effect in a workspacehttp://forge.typo3.org/issues/719732015-11-30T10:56:49ZLorenz Ulrich
<p>Sorting file references, e.g. in a "file links" element, doesn't have any effect in a workspace. After saving, the sorting is just as it was before:</p>
<p><img src="workspaces-fal-sorting.mp4" alt="" /></p> TYPO3 Core - Bug #60254 (Closed): Non-admins cannot rename bookmarkshttp://forge.typo3.org/issues/602542014-07-10T22:10:16ZLorenz Ulrich
<p>A non-admin can add bookmarks to pages, but adding bookmarks to records fails. After the confirmation popup is clicked, nothing happens.</p> TYPO3 Core - Bug #56567 (Closed): Palette form fields have no left padding anymorehttp://forge.typo3.org/issues/565672014-03-05T10:50:13ZLorenz Ulrich
<p>In TCEforms, form fields inside a palette (e.g. header of tt_content) don't have a left padding anymore</p>
<p><img src="http://forge.typo3.org/attachments/download/26182/formfield-palette.png" alt="" loading="lazy" /></p>
<p>This is a regression of <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Upgrade normalize.css to version 3.0.0 (Closed)" href="http://forge.typo3.org/issues/55316">#55316</a>.</p> TYPO3 Core - Task #55416 (Closed): Accessing the root folder of a file mount is not possible for ...http://forge.typo3.org/issues/554162014-01-29T10:09:02ZLorenz Ulrich
<p>The change "[!!!][TASK] Driver API has too many crosscutting concerns" <a class="changeset" title="[!!!][TASK] Driver API has too many crosscutting concerns The Driver within the FileAbstractionL..." href="http://forge.typo3.org/projects/typo3cms-core/repository/1749/revisions/f83eddd5027b74d7f4d28a845521bff3b2dd603d">f83eddd5027b74d7f4d28a845521bff3b2dd603d</a> breaks filemounts for non-admins (or changes the configuration needed?). After this change, a non-admin cannot access the root folder of a filemount. Sub-folders of a filemount work.</p>
<p>The error message is: "You are not allowed to access the given folder."</p> TYPO3 Core - Bug #44386 (Rejected): tcaTree cannot handle records on pid 0 correctlyhttp://forge.typo3.org/issues/443862013-01-08T17:23:54ZLorenz Ulrich
<p>When using the tcaTree with nested records on pid 0, the parent handling does not work correctly.</p>
<p>The reproduce, you can e.g. allow the table sys_category on the root page by adding <code>'rootLevel' => -1</code> to its TCA configuration. Then go to some page (not root), add 3 cats:</p>
<pre><code>foo<br /> bar, set foo as parent<br /> bar 2, set foo as parent</code></pre>
<p>Then add a category to root level, open 'bar' or 'bar 2' again -> parent is not selected anymore.</p> TYPO3 Core - Bug #37967 (Closed): YouTube videos can't be played with Media CEhttp://forge.typo3.org/issues/379672012-06-12T18:37:16ZLorenz Ulrich
<p>Since the rework of the Media CE for TYPO3 4.7, YouTube videos cannot be played anymore using the Media CE. The path to the video file is resolved correctly, but obviously the "TYPO3 Media Player" cannot play YouTube videos.</p>
<p>I compared the handling of 4.6 and 4.7 to get one step further in this problem:</p>
<p>- TYPO3 4.6 has a flag "Use Player (Flash only)". When this is checked, TYPO3 tries to play a video with the Flash Player.</p>
<p>- This "TYPO3 Media Player" (contrib/flashmedia/swfplayer.swf) cannot play YouTube videos.</p>
<p>- Unchecking the Player checkbox in 4.6 sets the YouTube/v URL itself as player (typo3\sysext\cms\tslib\content\class.tslib_content_media.php, l. 188). The YouTube player is correctly rendered then.</p>
<p>- The option to deactive the player is missing in TYPO3 4.7. Therefore the YouTube player itself will never be rendered and YouTube videos cannot be played with the Media element in 4.7.</p>
<p>I just googled about using the FlowPlayer to play YouTube videos. But obiously this is only possible with a commercial plugin (<a class="external" href="http://flowplayer.electroteque.org/youtube">http://flowplayer.electroteque.org/youtube</a>). So basically my conclusion would be that we need to have back the SWF rendering with the YouTube SWF as player.</p>
<p>Side note: Vimeo videos seem to work...</p> TYPO3 Core - Bug #30554 (Closed): Reports module: Available services brokenhttp://forge.typo3.org/issues/305542011-10-04T18:20:45ZLorenz Ulrich
<p>Displaying the available services in the reports module is broken. This is a regression of removing the global declarations for TYPO4 4.6. In TYPO3 < 4.6 the global array <code>$T3_SERVICES</code> contained too much information:</p>
<p>$T3_SERVICES[$serviceType][$serviceKey] --> Information about a particular service<br />$T3_SERVICES[$serviceKey][$serviceKey] --> Same information</p>
<p>Because of this duplicate, the method t3lib_extMgm::findService could be "abused" to find out if a particular service was the service of highest priority of a type.</p>
<p>After the cleanup, the array <code>$GLOBALS['T3_SERVICES']</code> only contains the information it is supposed to:</p>
<p>$T3_SERVICES[$serviceType][$serviceKey] --> Information about a particular service</p>
<p>Therefore t3lib_extMgm::findService($serviceKey, '*') will no longer work. This can be easily solved by adding a method that checks, if a particular service is the service of highest priority for the given service type.</p> TYPO3 Core - Bug #27605 (Closed): Move element/add pages layout problemshttp://forge.typo3.org/issues/276052011-06-21T02:08:49ZLorenz Ulrich
<ul>
<li>Some margin between the page name and "Copy instead of move" would be nice</li>
<li>The page tree position has white space between the dotted lines (same in add pages)</li>
</ul>
<p><img src="http://forge.typo3.org/attachments/download/17830/moveelement.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #27603 (Closed): No margin between search box and sys noteshttp://forge.typo3.org/issues/276032011-06-21T02:03:43ZLorenz Ulrich
<p>See here:</p>
<p><img src="http://forge.typo3.org/attachments/download/17828/sysnotes.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #27589 (Closed): About Modules: Background of module nameshttp://forge.typo3.org/issues/275892011-06-21T01:21:34ZLorenz Ulrich
<p>See here:</p>
<p><img src="http://forge.typo3.org/attachments/download/17810/aboutmodules.png" alt="" loading="lazy" /></p>
<p>Wouldn't it look better to remove the white background of the main module names?</p> TYPO3 Core - Bug #27588 (Closed): Template Analyzer: More space between optionshttp://forge.typo3.org/issues/275882011-06-21T01:19:10ZLorenz Ulrich
<p>See screenshot:</p>
<p><img src="http://forge.typo3.org/attachments/download/17809/tempanalyzer.png" alt="" loading="lazy" /></p>