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 - 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 #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 - Bug #77375 (Closed): MM references are not transformed to versioned entitieshttp://forge.typo3.org/issues/773752016-08-03T12:38:20ZOliver Haderoliver.hader@typo3.org
Scenario:
<ul>
<li>using a workspace</li>
<li>using a MM intermediate table for relations</li>
<li>having versioned entities on both sides of the relation to be defined</li>
<li>however, the live uids of the entities are submitted to the data handler</li>
</ul>
Problem:
<ul>
<li>MM relation is created with the live uids on one side</li>
</ul>
Solution:
<ul>
<li>convert submitted relation uids to accordant version uids in workspace context</li>
</ul> TYPO3 Core - Task #72395 (Closed): Mark out-dated workspaces parts as deprecatedhttp://forge.typo3.org/issues/723952015-12-22T16:58:43ZOliver Haderoliver.hader@typo3.org
<p>Several parts of the workspaces system extension are not used anymore by the core, but have not been marked as deprecated for TYPO3 CMS 7.</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 - 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 - Task #43210 (Closed): Resolving element dependencies does not work on deleted child ...http://forge.typo3.org/issues/432102012-11-21T22:00:14ZOliver Haderoliver.hader@typo3.org
<p>Imagine a structure of IRRE parent and child records - if one of those records are not deleted in a workspace, the parent pointer field (foreign_field) will still point to the live parent, not to the version parent. This results in a a wrong sys_refindex entry for that record which then again causes wrong dependency resolving on that deleted child record - it just has no parent record in that case.</p>
<p>I'm currently not sure where tx_version_tcemain or t3lib_TCEmain is causing this on deleting records...</p> TYPO3 Core - Feature #35246 (Closed): Make use of Extbase featureshttp://forge.typo3.org/issues/352462012-03-26T20:56:21ZOliver Haderoliver.hader@typo3.org
<p>The workspace module uses the Extbase dispatcher for backend modules, however, there are many places where domain models, repositories and proper services would make sense, e.g.:</p>
<ul>
<li>Domain_Model_Workspace (+ Repository)</li>
<li>Domain_Model_DatabaseRecord (could be live or version record) - lazy, just needs table and uid to be working</li>
<li>Domain_Model_CombinedRecord (the relationship of live and version record) - lazy, just needs table and uid to be working</li>
<li>Domain_Model_Stage (+ Repository)</li>
</ul> 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>