TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692020-09-22T16:53:41ZTYPO3 Forge
Redmine TYPO3 Core - Bug #92372 (Needs Feedback): Duplicates when copying a page having moved elements in...http://forge.typo3.org/issues/923722020-09-22T16:53:41ZOliver Haderoliver.hader@typo3.org
<a name="Steps"></a>
<h2 >Steps<a href="#Steps" class="wiki-anchor">¶</a></h2>
<ul>
<li>in live
<ul>
<li>having a page</li>
<li>having three content elements A, B, C on that page</li>
<li>having page localization of that page</li>
<li>having all three content elements localized (in connected mode)</li>
</ul>
</li>
<li>in workspace
<ul>
<li>move content element A after B</li>
<li>copy that page as new sibling on same level</li>
</ul></li>
</ul>
<a name="Bugs"></a>
<h2 >Bugs<a href="#Bugs" class="wiki-anchor">¶</a></h2>
<ul>
<li>localized version of moved record (having move-placeholders in workspace) are duplicated
<ul>
<li>→ localized version of element A is show twice in backend</li>
<li>→ in the frontend there is just one record rendered, no duplicates</li>
</ul>
</li>
<li>copied content elements in that page are not reflecting the proper order
<ul>
<li>→ should be B, A, C</li>
<li>→ actually is A, B, C since order was taken from live workspace, move-placeholders were ignored when copying the page</li>
</ul></li>
</ul>
<p>Tests at <a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/8457e82596fe232b7699fdd660dd18be8bb7c800/typo3/sysext/workspaces/Tests/Functional/DataHandling/Regular/Modify/DataSet/changeContentSortingAndCopyDraftPage.csv#L36">https://github.com/TYPO3/TYPO3.CMS/blob/8457e82596fe232b7699fdd660dd18be8bb7c800/typo3/sysext/workspaces/Tests/Functional/DataHandling/Regular/Modify/DataSet/changeContentSortingAndCopyDraftPage.csv#L36</a> (starting in line 36 with uids 335+) unfortunately contain this misbehaviour...</p> TYPO3 Core - Bug #89138 (Closed): Correctly retrieve workspace versionshttp://forge.typo3.org/issues/891382019-09-10T23:54:34ZOliver Haderoliver.hader@typo3.org
<ul>
<li>Clipboard now correctly resolves record localizations of a workspace</li>
<li>PageLayoutController new correctly determines sub-pages that are new in a particular workspace</li>
<li>SlugHelper & TypoScriptTemplateModuleController can be simplified by using WorkspaceRestriction directly</li>
<li>common function test scenario tree (based on YAML) is introduced for ext:backend in order to be used as structure for other tests</li>
<li>required testing framework changes support version and language variants and combination much better now</li>
</ul> TYPO3 Core - Bug #87995 (Closed): Cannot preview workspace changes in frontendhttp://forge.typo3.org/issues/879952019-03-25T10:54:48ZOliver Haderoliver.hader@typo3.org
<p>When previewing workspace changes in the frontend using split view (/typo3/index.php?route=%2Fworkspace%2Fpreview-control%2F&token=...&id=...) an exception is thrown.</p>
<pre>
#1518472189 TYPO3\CMS\Core\Error\Http\PageNotFoundException
Request parameters could not be validated (&cHash comparison failed)
</pre> TYPO3 Core - Bug #80995 (Closed): Content of hidden page not shown in workspace previewhttp://forge.typo3.org/issues/809952017-04-25T01:12:48ZOliver Haderoliver.hader@typo3.org
<p>New pages in a workspace are created as hidden per default. If either the hidden page or enabled version (the new-placeholder still stays hidden) shall be previewed in the frontend, no content elements are shown.</p>
<p>Parts of previous TYPO3 CMS 7 behavior of PageRepository has been extracted to distinct query restriction interceptors. However, back then not any enable restrictions were not applied if workspaces version preview was active.</p> TYPO3 Core - Bug #79048 (Closed): Cannot interact with versions on all workspaces tabhttp://forge.typo3.org/issues/790482016-12-20T13:13:33ZOliver Haderoliver.hader@typo3.org
<p>Interacting with workspace versions using the "all workspaces" tab in the workspace module is not possible. The process tries to use the current workspace, which is in this case the virtual workspace with ID -98 - which of course does not exist.</p> TYPO3 Core - Feature #72466 (Closed): Enhance workspace notification templateshttp://forge.typo3.org/issues/724662015-12-29T18:02:18ZOliver Haderoliver.hader@typo3.org
<ul>
<li>HTML messages</li>
<li>many (nested) records</li>
<li>provide additional technical information using HTML tags</li>
<li>enable customization of rendering and get rid of marker-based parts</li>
</ul>
A proof-of-concept example (already some years old):
<ul>
<li><a class="external" href="https://github.com/ohader/irre_workspaces/tree/master/Resources/Private/Templates/Notification">https://github.com/ohader/irre_workspaces/tree/master/Resources/Private/Templates/Notification</a></li>
<li><a class="external" href="https://github.com/ohader/irre_workspaces/blob/master/Classes/Service/Action/ChangeStageService.php">https://github.com/ohader/irre_workspaces/blob/master/Classes/Service/Action/ChangeStageService.php</a></li>
</ul> TYPO3 Core - Task #71990 (Closed): Add possibility to purge workspaces move placeholderhttp://forge.typo3.org/issues/719902015-11-30T17:50:22ZOliver Haderoliver.hader@typo3.org
<p>During resolving references in a workspace context overlays and delete-placeholder are considered and it's possible to define whether they are kept or substituted. This mechanism is missing for move-placeholders as well.</p> TYPO3 Core - Feature #65720 (New): Add workspace element filter settingshttp://forge.typo3.org/issues/657202015-03-13T14:55:48ZOliver Haderoliver.hader@typo3.org
<p>The workspace configuration is extended by an element filter setting that allows to define record visibility in the workspace module per stage. This way, it can be defined, that either workspace owner, members or editors/creators of a particular record are allowed to see elements in the module - depending on the setting for the element's workspace stage.</p> TYPO3 Core - Bug #58441 (Closed): Displaced button in workspace preview toolbarhttp://forge.typo3.org/issues/584412014-05-03T10:46:51ZOliver Haderoliver.hader@typo3.org
<p>The workspace preview in the TYPO3 frontend shows a toolbar at the top for several workspace related actions.<br />However, the whole toolbar and its buttons have visual bugs and look displaced if the screen is resized.</p>
See attached screenshots
<ul>
<li>wsPreview_1.png</li>
<li>wsPreview_2.png</li>
</ul> TYPO3 Core - Story #58284 (Closed): Bug fixes & Behaviourhttp://forge.typo3.org/issues/582842014-04-28T10:49:41ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Story #54854 (Closed): As an editor I want to use a more intuitive workspace modulehttp://forge.typo3.org/issues/548542014-01-08T22:17:28ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Story #54853 (Closed): As a user I want to correctly create, modify, preview and pub...http://forge.typo3.org/issues/548532014-01-08T22:14:58ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Feature #50223 (Closed): Enable all workspaces tab in workspace modulehttp://forge.typo3.org/issues/502232013-07-20T14:30:44ZOliver Haderoliver.hader@typo3.org
<p>The "all workspaces" tab currently is only available for admin users. However, there's no need to disallow regular editors to use this feature as well - access will be granted to workspaces that have been defined for each particular user or group.</p>
<p>Besides that, actions from the "all workspaces" view need to be handled in a special way since there is no correct BE_USER->workspace value assigned in that case and working with records require the correct workspaces scope to deal with the correct t3ver_wsid values.</p> TYPO3 Core - Bug #27976 (Closed): A cache with identifier "workspaces_cache" does not existhttp://forge.typo3.org/issues/279762011-07-08T10:41:58ZOliver Haderoliver.hader@typo3.org
<p>The following exception is thrown on e.g. creating a new localized version of a page in the live workspace:</p>
<pre>#1203699034: A cache with identifier "workspaces_cache" does not exist. (More information)
t3lib_cache_exception_NoSuchCache thrown in file
/Users/olly/Development/typo3/master/t3lib/cache/class.t3lib_cache_manager.php in line 132.</pre> TYPO3 Core - Bug #11163 (Closed): Actions performed on tabs are not executed on the correct works...http://forge.typo3.org/issues/111632010-11-30T14:00:43ZOliver Haderoliver.hader@typo3.org
<p>Actions performed on tabs are not executed on the correct workspace</p>