http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692013-03-17T21:13:04ZTYPO3 ForgeTYPO3 Core - Bug #22519: Page moved in custom workspace doesn't get moved when published using LIVE workspacehttp://forge.typo3.org/issues/22519?journal_id=1549402013-03-17T21:13:04ZOliver Haderoliver.hader@typo3.org
<ul><li><strong>Target version</strong> deleted (<del><i>0</i></del>)</li><li><strong>Parent task</strong> set to <i>#46389</i></li></ul> TYPO3 Core - Bug #22519: Page moved in custom workspace doesn't get moved when published using LIVE workspacehttp://forge.typo3.org/issues/22519?journal_id=2448162015-01-15T12:53:53ZMathias Schreibermathias.schreiber@typo3.com
<ul><li><strong>Category</strong> set to <i>Workspaces</i></li><li><strong>Is Regression</strong> set to <i>No</i></li></ul> TYPO3 Core - Bug #22519: Page moved in custom workspace doesn't get moved when published using LIVE workspacehttp://forge.typo3.org/issues/22519?journal_id=2462692015-01-23T11:33:38ZMathias Schreibermathias.schreiber@typo3.com
<ul><li><strong>Target version</strong> set to <i>7.5</i></li></ul> TYPO3 Core - Bug #22519: Page moved in custom workspace doesn't get moved when published using LIVE workspacehttp://forge.typo3.org/issues/22519?journal_id=2767242015-09-22T12:53:36ZRiccardo De Contardierredeco@gmail.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul><p>I close this because I can't reproduce it in both 6.2.15 and 7.5-dev (latest dev)</p>
<p>My test:</p>
<p>I enter TYPO3 as an editor which is both owner and member of the custom workspace.<br />1) live workspace > create a page<br />2) switch to custom workspace<br />3) move the page with drag & drop<br />4) switch to live workspace<br />5) workspace module > you have to select the tab "All workspaces" to see the moved page<br />6) promote the page to publish</p>
<p>result: the page is moved</p>
<p>If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.</p>