TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-11-20T08:46:44ZTYPO3 Forge
Redmine TYPO3 Core - Task #96041 (Closed): Toolbar items: Register via compiler passhttp://forge.typo3.org/issues/960412021-11-20T08:46:44ZDaniel Windloff
<p>The registration of the toolbar items are set in the ext_localconf.php file. It only links to provider classes, that have to implement the ToolbarItemInterface. Therefore the registration could be simplified by tagging via that interface.</p> TYPO3 Core - Task #88724 (Closed): Usage of localizationRedirecthttp://forge.typo3.org/issues/887242019-07-11T14:49:28ZDaniel Windloff
<p>The method "localizationRedirect" in PageLayoutView, DatabaseRecordList and EditDocumentController is almost the same.</p>
<p>The usage should be streamlined and two of them should be removed.</p> TYPO3 Core - Task #81429 (Closed): Streamline preview iconshttp://forge.typo3.org/issues/814292017-06-02T16:46:50ZDaniel Windloff
Usage:
<ul>
<li><strong>actions-view-page</strong><br />Preview a single page record </li>
<li><strong>actions-view</strong><br />Preview a single record (except pages)</li>
<li><strong>actions-document-view</strong><br />Preview multiple records</li>
</ul> TYPO3 Core - Task #81428 (Closed): Streamline icons for "new" actionshttp://forge.typo3.org/issues/814282017-06-02T16:38:30ZDaniel Windloff
Suggested usage:
<ul>
<li><strong>actions-add-placeholder</strong><br />Link to wizards / controller (e.g. NewRecordController) where the selection between several kinds of new records can be made </li>
<li><strong>actions-add</strong><br />*Link to one new record (EditDocumentController) for all records except pages</li>
<li><strong>actions-page-new</strong><br />Link to one new page record</li>
<li><strong>actions-document-new</strong><br />Link to create multiple new records (EditDocumentController)</li>
</ul> TYPO3 Core - Task #81422 (Closed): Use actions-remove to remove items from listhttp://forge.typo3.org/issues/814222017-06-02T15:10:59ZDaniel Windloff
Replaced icons:
<ul>
<li>icon-actions-selection-delete</li>
<li>icon-actions-close</li>
</ul>
<p>Use actions-remove for remove items from list actions, that do not change db entries.</p> TYPO3 Core - Task #81238 (New): Streamline severity and message of delete modalhttp://forge.typo3.org/issues/812382017-05-17T08:55:42ZDaniel Windloff
<a name="Story"></a>
<h2 >Story:<a href="#Story" class="wiki-anchor">¶</a></h2>
<p>As an user I would like to know if a record or a file is moved to trash or deleted from database or file system.</p>
<a name="Reference-behavior"></a>
<h2 >Reference behavior:<a href="#Reference-behavior" class="wiki-anchor">¶</a></h2>
Delete a tt_content record:
<ul>
<li>modal serverity warning (yellow).</li>
</ul>
Switch to the recycler module and delete the record there:
<ul>
<li>modal severity danger (red).</li>
</ul>
So as an user I expect the following relation:
<ul>
<li>warning → moved to trash</li>
<li>danger → delete</li>
</ul>
<a name="Overview"></a>
<h2 >Overview:<a href="#Overview" class="wiki-anchor">¶</a></h2>
<table>
<tr>
<th>case </th>
<th>expected behavior </th>
<th>current behavior </th>
<th>example</th>
</tr>
<tr>
<td>TCA record with ctrl – delete and deleted = 0 </td>
<td> warning </td>
<td> warning </td>
<td> tt_content</td>
</tr>
<tr>
<td>TCA record with ctrl – delete and deleted = 1 </td>
<td> danger </td>
<td> danger </td>
<td> tt_content</td>
</tr>
<tr>
<td>TCA record without ctrl – delete </td>
<td> danger </td>
<td> warning </td>
<td> sys_domain</td>
</tr>
<tr>
<td>Record without TCA </td>
<td> danger </td>
<td> warning </td>
<td> scheduler task</td>
</tr>
<tr>
<td>File with recycler available and not in recycler </td>
<td> warning </td>
<td> warning </td>
<td> file</td>
</tr>
<tr>
<td>File in recycler </td>
<td> danger </td>
<td> warning </td>
<td> file</td>
</tr>
<tr>
<td>File without recycler </td>
<td> danger </td>
<td> warning </td>
<td> file</td>
</tr>
</table> TYPO3 Core - Task #78864 (Closed): Streamline ElementInformation templatehttp://forge.typo3.org/issues/788642016-12-02T13:12:08ZDaniel Windloff
<ul>
<li>Change "Show" button to btn-default</li>
<li>Use infobox for missing files</li>
<li>Streamline button order and groups</li>
</ul> TYPO3 Core - Task #78753 (Closed): Streamline button order in list module / multi selection modehttp://forge.typo3.org/issues/787532016-11-20T08:04:06ZDaniel Windloff
<p>In order to be consistent, chage the button order to edit, delete, copy and mark all.</p> TYPO3 Core - Task #78424 (Closed): Streamline checkbox styling in TranslationStatusControllerhttp://forge.typo3.org/issues/784242016-10-25T14:26:28ZDaniel Windloff
<p>In order to be consistent, change the checkbox styling in TranslationStatusController.</p> TYPO3 Core - Task #78383 (Closed): TCA: Streamline field order and position for recurring fieldshttp://forge.typo3.org/issues/783832016-10-23T13:16:18ZDaniel Windloff
<a name="User-story"></a>
<h2 >User story<a href="#User-story" class="wiki-anchor">¶</a></h2>
<p>When I edit a record, I would like to have the same options on similar places. So I have a chance to have a valid expectation where to find the option.</p>
<a name="Description-of-the-issue"></a>
<h2 >Description of the issue<a href="#Description-of-the-issue" class="wiki-anchor">¶</a></h2>
<p>In T3 there are some recurring field definitions shared by a lot of records (core records and extension records). These fields are mostly defined in TCA[‘crtl’]- e.g. disabled, descriptionColumn. These fields should have a standard position and order.</p>
<a name="Example-Field-enablecolumnsdisabled"></a>
<h2 >Example Field enablecolumns.disabled<a href="#Example-Field-enablecolumnsdisabled" class="wiki-anchor">¶</a></h2>
<table>
<tr>
<th>Record </th>
<th>Tab </th>
<th>Field position </th>
</tr>
<tr>
<td>Page </td>
<td> Access </td>
<td> Visibility – Page - Disable</td>
</tr>
<tr>
<td>Backendusergroup </td>
<td> General </td>
<td> Disable</td>
</tr>
<tr>
<td>Backenduser </td>
<td> General </td>
<td> Disable</td>
</tr>
<tr>
<td>Webseite language </td>
<td> Access </td>
<td> Disable</td>
</tr>
<tr>
<td>Action </td>
<td> Access </td>
<td> Deactivated</td>
</tr>
<tr>
<td>System News </td>
<td> General </td>
<td> Disable</td>
</tr>
<tr>
<td>Scheduler task group </td>
<td> --- </td>
<td> Disable</td>
</tr>
<tr>
<td>Template </td>
<td> General </td>
<td> Disable</td>
</tr>
<tr>
<td>Content element</td>
<td> Access </td>
<td> Visibility – Content Element - Disable</td>
</tr>
<tr>
<td>Website User </td>
<td> General </td>
<td> Disable</td>
</tr>
<tr>
<td>Backend layout </td>
<td> Access </td>
<td> Disable:</td>
</tr>
<tr>
<td>Domain </td>
<td> --- </td>
<td> Disable</td>
</tr>
<tr>
<td>Alternative Page Language </td>
<td> Access </td>
<td> Visiblity – Page - Disable</td>
</tr>
<tr>
<td>Category </td>
<td> General </td>
<td> Hide (next to Language in palette)</td>
</tr>
<tr>
<td>Record Collection </td>
<td> General </td>
<td> Hide (next to Language in palette)</td>
</tr>
<tr>
<td>Abbreviation </td>
<td> --- </td>
<td> Hide</td>
</tr>
</table>
<a name="Suggested-solution"></a>
<h2 >Suggested solution<a href="#Suggested-solution" class="wiki-anchor">¶</a></h2>
<p>Streamline the field order and position for all core records. Add missing fields where necessary. Document the order and position to encourage extension authors to change the field order accordingly.</p>
<a name="Suggested-field-order-and-position"></a>
<h2 >Suggested field order and position<a href="#Suggested-field-order-and-position" class="wiki-anchor">¶</a></h2>
<p>Legend: / means palette</p>
<p><strong>Tab: General (must be the first tab)</strong></p>
<ul>
<li>type / (main sub selection e.g. colPos)</li>
<li>label / (label specific options)</li>
<li>label_alt (in case these fields are related to the label)</li>
</ul>
<p><strong>Other tabs defined by the specific record</strong></p>
<p><strong>Tab: Language</strong></p>
<ul>
<li>language_field / transOrigPointerField</li>
<li>other language or translation related options</li>
</ul>
<p><strong>Tab: Access</strong></p>
<ul>
<li>disabled / (hide in menu)</li>
<li>starttime / endtime</li>
<li>fe_group / fe_admin_lock</li>
<li>adminlock</li>
<li>other access related options</li>
</ul>
<p><strong>Tab: Categories</strong></p>
<ul>
<li>categories (not to select parent categories; only to categorize a record)</li>
</ul>
<p><strong>Tab: Notes</strong></p>
<ul>
<li>descriptionColumn</li>
</ul> TYPO3 Core - Task #78199 (Closed): Streamline button order/grouphttp://forge.typo3.org/issues/781992016-10-08T18:37:23ZDaniel Windloff
In order to be consistent, streamline the button order. <br /><strong>Group 1:</strong>
<ul>
<li>preview</li>
<li>edit</li>
<li>hide</li>
<li>delete</li>
</ul>
<strong>Group 2:</strong>
<ul>
<li>info</li>
<li>sorting</li>
</ul>
<strong>Group 3:</strong>
<ul>
<li>misc</li>
</ul> TYPO3 Core - Task #78174 (Closed): Streamline order and styling of icons in InlineRecordContainerhttp://forge.typo3.org/issues/781742016-10-07T14:02:10ZDaniel Windloff
<p>In order to be consistent, change the button order and styling (according to the list module).</p> TYPO3 Core - Bug #77588 (Closed): SQL Error / Check linkshttp://forge.typo3.org/issues/775882016-08-22T19:36:54ZDaniel Windloff
<p>It is possible to get a sql-error in EXT:linkvalidator (info module).</p>
Steps to reproduce:
<ul>
<li>Create an empty, hidden page</li>
<li>Go to the linkvalidator</li>
<li>Run check links (select all link types; check level: This page)</li>
<li>Get exception Doctrine\DBAL\Exception\SyntaxErrorException (master)</li>
</ul>
<p>Reason:<br />LinkAnalyzer::getLinkStatistics doesn’t check against an empty $pidList and could generate an invalid sql-query.</p>
<p>Tested in master(8)/7.6/6.2.</p> TYPO3 Core - Feature #77581 (New): List module: Add preview button for recordshttp://forge.typo3.org/issues/775812016-08-22T14:59:42ZDaniel Windloff
<p>In <a class="issue tracker-4 status-5 priority-3 priority-lowest closed child" title="Task: Add generic preview URL generator API (Closed)" href="http://forge.typo3.org/issues/66370">#66370</a> the configuration for the preview url of records was introduced.<br />At the moment the configuration is used by the EditDocumentController to generate the preview url for "Save and view".<br />It would be nice to use the same configuration to generate preview buttons in the recordlist (list module).</p> TYPO3 Core - Feature #77580 (New): List module: Make the selection of single record mode, multi-s...http://forge.typo3.org/issues/775802016-08-22T14:35:45ZDaniel Windloff
<p>To make the features of the list module (EXT:recordlist) easy to find, add the main (currently implicit) selections to the module menu. <br />Remove the “activated clipboard” dependency from the selection mode.</p>
<p>Example 1:<br />The user wants to edit or remove multiple records.</p>
<p>Current situation:<br />The user has to scroll down, active the clipboard, scroll down and click to the multi selection mode (e.g. Clipboard 1). <br />The action itself (edit, remove) has no relation to clipboard features (move, copy, paste).</p>
<p>Proposed behaviour:<br />Select the single record mode or the multi-selection mode via module menu (in case of a deactivated clipboard). Select the clipboard via module menu in case of an activated clipboard.</p>
<p>Example 2:<br />The user wants to select an additional column (download a csv…).</p>
<p>Current situation:<br />Scroll to the table of the record type and click to the table title. If there are many record types and records, the link will be hard to find.</p>
<p>Proposed behaviour:<br />Select record type in the module menu.</p>