TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692017-04-03T18:39:24ZTYPO3 Forge
Redmine 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 - Bug #73243 (Closed): Stage buttons shown in frontend without user being repsonsiblehttp://forge.typo3.org/issues/732432016-02-11T15:50:44ZOliver Haderoliver.hader@typo3.org
<p>The workspace preview in the frontend shows the buttons to the previous and next stage if the user is not responsible for the current stage. Clicking the button does not forward the records to the names stage however - this is caught by DataHandlerHook in EXT:version.</p> TYPO3 Core - Bug #72225 (Closed): Workspace page previews collide with generated preview linkshttp://forge.typo3.org/issues/722252015-12-14T22:53:45ZOliver Haderoliver.hader@typo3.org
<p>Workspace page previews collide with that configuration that might have been set by using a preview link containing a ADMCMD_prev command. The keyword "IGNORE" is introduced to actually ignore these configurations when viewing a page from the workspace module.</p> TYPO3 Core - Bug #71161 (Closed): Workspace placeholder is not process with eval-functionhttp://forge.typo3.org/issues/711612015-10-30T13:28:28ZOliver Haderoliver.hader@typo3.org
<p>The workspace move-placeholder is not processed with the accordant eval-function. This leads to scenario that a placeholder is not persisted at all and produces orphaned or invalid data sets.</p> TYPO3 Core - Task #11162 (Closed): Suggest to Core and other extensions to increase the type of t...http://forge.typo3.org/issues/111622010-11-30T12:40:17ZOliver Haderoliver.hader@typo3.org
<p>Currently the field t3ver_stage which is defined by each module/extension that supports workspaces is defined as TINYINT and thus supports up to 255 stages. This was way enough until now - however since we have custom stages right now and each workspace can also have stages, it might happen that 255 is not enough anymore.</p>
<p>Thus, we should consider to give the suggestion to the Core and Extension Developers to use INT as storage type for the t3ver_stage field.</p> TYPO3 Core - Task #11153 (Closed): Determine whether Tx_Workspaces_Service_Stages::encodeStageUid...http://forge.typo3.org/issues/111532010-11-30T10:45:09ZOliver Haderoliver.hader@typo3.org
<p>Determine whether the following wrappers in Tx_Workspaces_Service_Stages are still required and remove them if not.</p>
<p>public function resolveStageUid($ver_stage) {<br /> return $ver_stage;<br /> //return $ver_stage - $this->raiseStageIdAmount;<br />}</p>
<p>public function encodeStageUid($stage_uid) {<br /> return $stage_uid;<br /> //return $stage_uid + $this->raiseStageIdAmount;<br />}</p> TYPO3 Core - Bug #11143 (Closed): Editing workspaces record shows PHP warninghttp://forge.typo3.org/issues/111432010-11-29T19:15:18ZOliver Haderoliver.hader@typo3.org
<p>PHP Warning<br />PHP Warning: parse_url(/typo3/alt_doc.php?returnUrl=http://myhost.com/typo3/mod.php?M=web_WorkspacesWorkspaces&workspace=2&tx_workspaces_web_workspacesworkspaces%5Baction%5D=index&tx_workspaces_web_workspacesworkspaces%5Bcontroller%5D=Review&id=0&edit[pages]<sup><a href="#fn212">212</a></sup>=edit) [function.parse-url]: Unable to parse URL in typo3/alt_doc.php line 216</p>
<p>-> returnUrl shall be URL encoded</p> TYPO3 Core - Feature #9820 (Closed): Module: Show legend below new grid componenthttp://forge.typo3.org/issues/98202010-09-18T17:56:11ZOliver Haderoliver.hader@typo3.org
<p>Module: Show legend below new grid component</p> TYPO3 Core - Feature #9759 (Closed): Module: Improve styling of the whole new grid viewhttp://forge.typo3.org/issues/97592010-09-16T12:16:07ZOliver Haderoliver.hader@typo3.org
<p>Improve styling of the whole new grid view</p> TYPO3 Core - Feature #9758 (Closed): Module: Implement handler on the PHP side for the accordant ...http://forge.typo3.org/issues/97582010-09-16T12:10:30ZOliver Haderoliver.hader@typo3.org
<p>Implement handler on the PHP side for the accordant actions in the grid view in a new controller (Classes/Controller/).</p> TYPO3 Core - Feature #9753 (Closed): Module: Extend the ExtJS grid view and visualize the data de...http://forge.typo3.org/issues/97532010-09-16T11:58:56ZOliver Haderoliver.hader@typo3.org
<p>The data that is delivered must be visualized in the ExtJS grid view.</p> TYPO3 Core - Feature #9752 (Closed): Module: Implement foldout part of differences in grid viewhttp://forge.typo3.org/issues/97522010-09-16T11:55:45ZOliver Haderoliver.hader@typo3.org
<p>Implement the functionality to render the differences of workspace versions in the ExtJS grid view.<br />The accordant data shall be requested by AJAX, an plain HTML response is expected here.</p> TYPO3 Core - Feature #9750 (Closed): Module: Take over wslib from versions extensionshttp://forge.typo3.org/issues/97502010-09-16T11:36:10ZOliver Haderoliver.hader@typo3.org
<p>Copy the required methods in the old wslib of the versions extension to the new workspaces manager.</p> TYPO3 Core - Bug #20759 (Closed): Changing the workspace by the workspace selector produces JavaS...http://forge.typo3.org/issues/207592009-07-15T17:19:14ZOliver Haderoliver.hader@typo3.org
<p>On changing the workspace from e.g. live to draft by using the workspace selector, JavaScript errors appear. Firefox can handle them without any problem, however Internet Explorer has some severe problems with it.</p>
<p>Solution:<br />When the workspace got changed the selector puts a location.href to the top of the backend.php's JavaScript. It's preferred to use a real HTTP redirect instead of the JavaScript hack.</p>
<p>(issue imported from #M11541)</p>