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 #84985 (Closed): Published workspace record show in page treehttp://forge.typo3.org/issues/849852018-05-12T17:27:42ZOliver Haderoliver.hader@typo3.org
<a name="Steps-to-reproduce"></a>
<h3 >Steps to reproduce<a href="#Steps-to-reproduce" class="wiki-anchor">¶</a></h3>
<ul>
<li>switch to some workspace</li>
<li>change title of page & save</li>
<li>publish workspace version to live</li>
<li>reload page tree</li>
</ul>
<a name="Result"></a>
<h3 >Result<a href="#Result" class="wiki-anchor">¶</a></h3>
<ul>
<li>page tree shows modified value</li>
<li>page tree shows previous old version</li>
</ul>
<a name="Background"></a>
<h3 >Background<a href="#Background" class="wiki-anchor">¶</a></h3>
<p>When publishing workspace records, the previous old version is still persisted with <code>pid=-1</code> and <code>t3ver_wsid=0</code> - that's correct. However, these records are not not filtered in the page tree.</p>
<a name="Pointer"></a>
<h3 >Pointer<a href="#Pointer" class="wiki-anchor">¶</a></h3>
<p>Flaws in resolving records in <code>PageTreeRepository::fetchAllPages</code> and maybe in <code>BackendWorkspaceRestriction</code> usage...</p> TYPO3 Core - Bug #81950 (Closed): Resolve disabled sys_workspace.unpublish_timehttp://forge.typo3.org/issues/819502017-07-24T15:15:03ZOliver Haderoliver.hader@typo3.org
<p>The property <code>sys_workspace.unpublish_time</code> was hidden during TYPO3 4.5 development from being displayed with a remark that the feature would not be working (see <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: "Un-Publish:" should be hidden (Closed)" href="http://forge.typo3.org/issues/12333">#12333</a>). However, in version 8.7 and 9-dev the TCA property is still available and still handled in <code>AutoPublishService</code> - however, there's not possibility in the regular backend to define that field.</p>
<p>The workspace auto-publishing process was thought to automatically push a (temporary) version to live at a given time (publish), as well as reverting that back at some other date (unpublish). The wording of "publishing" is misleading here, since it actually should be a "swapping" process which allows to switch the live and version state of some element at any time.</p>
<p>Thus, now we can either remove the <code>unpublish</code> behavior completely (from TCA and <code>AutoPublishService</code>) or "enable" this feature again (adding it to TCA types again) & providing better description and documentation.</p> 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 #80663 (Closed): Inline references are bound to versioned pagehttp://forge.typo3.org/issues/806632017-04-03T18:39:24ZOliver Haderoliver.hader@typo3.org
<p>When modifying inline child elements that belong to a page as parent record in a workspace, the pid values of these inline children are bound to the page version instead of the according counterpart (real record or placeholder) of the live workspace.</p> TYPO3 Core - Task #79339 (Closed): Streamline assignment of current workspace in DataHandlerhttp://forge.typo3.org/issues/793392017-01-16T16:26:50ZOliver Haderoliver.hader@typo3.org
<p>The processing of data structures in DataHandler and RelationHandler are bound to each other. DataHandler allows to be initialized with a custom BE_USER instance and thus with a custom workspace, different to the actual value of the real instance of $GLOBALS['BE_USER'].</p> TYPO3 Core - Feature #79105 (New): Extend workspace notification channelshttp://forge.typo3.org/issues/791052016-12-29T13:15:10ZOliver Haderoliver.hader@typo3.org
<p>Currently workspaces only supports sending out notifications via mail, however it would be great if this can be enhanced to push notifications to any other service, like e.g. Slack, IRC. This feature is about providing to possibility to have a custom API for attaching new notification services.</p> TYPO3 Core - Bug #70921 (Accepted): Really resolve meaning of FlexForm fields in version dependen...http://forge.typo3.org/issues/709212015-10-21T18:28:36ZOliver Haderoliver.hader@typo3.orgTYPO3 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 #61719 (Closed): Warnings on flushing whole workspace with localizationshttp://forge.typo3.org/issues/617192014-09-18T15:46:45ZOliver Haderoliver.hader@typo3.org
<p>Flushing a whole workspace in the workspace, which contains record localizations, shows warnings like this in the workspace module:<br /><cite>Attempt to reset workspace for record failed: No record</cite></p>
<p>The reason for that is simple, the record already has been flushed since it's a localization.</p>
<p>Thus, either the warning can be omitted by tracking already processed elements or record localizations need to be processed before the default record.</p> TYPO3 Core - Task #59120 (Accepted): Enhance workspace preview for new localized pageshttp://forge.typo3.org/issues/591202014-05-26T13:38:29ZOliver Haderoliver.hader@typo3.org
Scenario:
<ul>
<li>page available in default language</li>
<li>no translation available</li>
</ul>
Actions:
<ul>
<li>in workspace, page gets localized</li>
<li>preview of the new localized page</li>
</ul>
Experience:
<ul>
<li>preview module (with live/workspace slider) shows default and translated website</li>
</ul>
<p>There should be a warning that there is no localized pendant in live the workspace version can be compared to.</p> TYPO3 Core - Task #59116 (Accepted): Workspace module shows unmodified valueshttp://forge.typo3.org/issues/591162014-05-26T13:14:13ZOliver Haderoliver.hader@typo3.org
<p>The workspace module shows field values that have not been modified by a user. This can be reproduced by e.g. creating a new text with images element in a workspace, but without any image.</p>
This can be enhanced by using better defaults for records:
<ul>
<li>NULL vs. empty string for the "image" field for example</li>
<li>skipping empty and system values in the workspace module view</li>
</ul> TYPO3 Core - Feature #9754 (Rejected): Module: Implement Workspaces List tabhttp://forge.typo3.org/issues/97542010-09-16T12:01:32ZOliver Haderoliver.hader@typo3.org
<p>Implement Workspaces List tab</p>