TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692010-11-29T19:15:18ZTYPO3 Forge
Redmine 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 - Bug #11142 (Closed): The 'All' tab throws Exception 'No such workspace defined'http://forge.typo3.org/issues/111422010-11-29T19:09:09ZOliver Haderoliver.hader@typo3.org
<p>Select the 'All' tab and get an Exception 'No such workspace defined' thrown in tx_Workspaces_Service_Workspaces::getWorkspaceTitle<br />The precondition is that there are records which belong to a workspace that does not exist anymore.</p> TYPO3 Core - Task #10201 (Closed): Set up test environment for team membershttp://forge.typo3.org/issues/102012010-10-11T18:29:49ZOliver Haderoliver.hader@typo3.org
<p>Set up a test environment for team members.<br />A TYPO3 introduction package will be used to visualize the work. The sources are fetched automatically via cron job from GitHub.</p>
<p>Future URL: <a class="external" href="http://workspaces.typo3projects.org/">http://workspaces.typo3projects.org/</a></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 #9755 (Closed): Module: Implement modal window for "send to stage"http://forge.typo3.org/issues/97552010-09-16T12:05:11ZOliver Haderoliver.hader@typo3.org
<p>Implement a modal window in ExtJs (take existing concept for e.g. relogin windows or donate window) that allows one to select the next stage.<br />The data will be prerendered and transferred by plain HTML and substituted in DOM there.</p> 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> 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 #9751 (Closed): Module: Extend the structure to be available in new workspac...http://forge.typo3.org/issues/97512010-09-16T11:43:22ZOliver Haderoliver.hader@typo3.org
Fields to be defined in the structure that is available in JavaScript:
<ul>
<li>uid</li>
<li>workspace id</li>
<li>current stage</li>
<li>next stage</li>
<li>label of workspace version</li>
<li>label of live version</li>
<li>percentage of changes</li>
<li>rootline of workspace version (parent page could be changed)</li>
<li>rootline of live version</li>
<li>date of creation in workspace</li>
<li>date of last change in workspace</li>
<li>record icon (concerning the current state like hidden, time-controlled, etc.)</li>
</ul> 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 - Feature #2567 (Closed): Recycler: Change layout and interface to fit HCI suggestionshttp://forge.typo3.org/issues/25672009-02-04T21:46:43ZOliver Haderoliver.hader@typo3.org
Change layout and interface to fit HCI suggestions
<ul>
<li>concerning usability</li>
<li>concerning styling and colors</li>
</ul> TYPO3 Core - Feature #1835 (Closed): Recycler: Integrate recursive recoveringhttp://forge.typo3.org/issues/18352008-10-26T22:26:02ZOliver Haderoliver.hader@typo3.org
Imagine the following structure of deleted pages:
<ul>
<li>"First Level" (id: 1, deleted: 1)
<ul>
<li>"Second Level" (id: 2, deleted: 1)
<ul>
<li>"Third Level" (id: 3, deleted: 1)</li>
</ul></li>
</ul></li>
</ul>
<p>If the "Third Level" (id: 3) shall be recovered, it would be required that all deleted ancestors get recovered as well.</p>
On a per-user basis it shall be possible to define the following:
<ol>
<li>User is allowed to execute recursive recovering data structures (in the example, if page with id 3 gets recovered, also the ids 2 and 1 get recovered automatically)</li>
<li>User is not allowed to execute recursive recovering - thus, the record (e.g. page with id 3) isn't displayed with the possibility to be recovered in the recycler</li>
</ol>
<p>"Per-user basis" means User TSconfig and User setup module. Additionally there must be a configurable system default to that behaviour.</p> TYPO3 Core - Feature #1834 (Closed): Recycler: Integrate Lost+Found possibiliteshttp://forge.typo3.org/issues/18342008-10-26T22:15:18ZOliver Haderoliver.hader@typo3.org
Imagine a record is still available in the database and not marked as deleted (deleted=0). However the accordant parent element was deleted (removed completely or marked as deleted). These parent elements could be:
<ul>
<li>a page (direct parent or any other page ancestor) that was deleted</li>
<li>a default language record that was deleted (translated records, e.g. spanish, are not marked as deleted)</li>
</ul>
<p>All these records with no correct reference to an existing resource should be displayed as "Lost+Found" with the possibilites to delete them as well or to move the to another page.</p>