TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692016-02-25T10:41:24ZTYPO3 Forge
Redmine TYPO3 Core - Feature #73665 (New): Backend page tree: show localized page titlehttp://forge.typo3.org/issues/736652016-02-25T10:41:24ZSonja Schubertsonja.scholz@typo3.org
<p>Hey guys,</p>
<p>I want to suggest a new feature for the backend page tree. It would be nice to have two new options in pageTSconfig available:</p>
<p>options.pageTree.showLocalizedTitle = 2<br />options.pageTree.showLocalizedTitleDefaultLabel = [Default]:</p>
<p>With this new options an administrator can activate the feature to show the page title in backend page tree localized in the language 2 if available. This would be comfortable for editors from China or Russia which wants to see the page tree in their language localized also. If the certain page is not localized in language 2 the title from default language is shown. Here it is possible to add a label before if configured, to not confuse the editor. I added a diff patch, so you can take a look.</p>
<p>What do you think? Could this feature be added?</p>
<p>Kind regards,</p>
<p>Sonja</p> TYPO3 Core - Feature #32547 (Accepted): BCC for notification mail - configurable by stagehttp://forge.typo3.org/issues/325472011-12-14T15:52:22ZSonja Schubertsonja.scholz@typo3.org
<p>It would be nice to have a configuration field hidden_notification / BCC for every stage, where it is possible to add several email addresses.</p>
<p>On every stage change these fields are checked and the containing email addresses will also get a notification email. The be_user won't notice this, as this is not shown anywhere in backend.</p>
<p>I attached the modified t3x of the workspaces extension with a tested solution. I know that it is not nice to just attach the t3x and do not create patches. I am very sorry but I have no time this week to create these patches, but I will do this later.</p>
<p>Nevertheless some feedback if you like this feature in general would be nice.</p>
<p>Greets,</p>
<p>Sonja</p> TYPO3 Core - Feature #32545 (Accepted): Show only recipients which are responsible for this page/...http://forge.typo3.org/issues/325452011-12-14T15:43:12ZSonja Schubertsonja.scholz@typo3.org
<p>If you have a TYPO3 extension with one workspace but a lot of seperate websites, you have the following problem.</p>
<p>As soon as a user sends a change to the next stage, it will get all responsible users for this stage as suggested recipients for the notification mail. In such a big TYPO3 installation this may be a lot of users.</p>
<p>Now it would be nice if workspaces extension would check the responsible users and only suggest these users which are allowed to see this changed element/page/mount. We developed a proof-of-concept solution, which is not nice and core-like developed but works. Maybe it is a basis to discuss and develop a clean/nice solution.</p>
<p>Further we developed a extEMConf option stageChangeHideMatch where it is possible to insert a preg_match which usernames should not be shown as suggested recipients in the stage change popup.</p>
<p>I attached the modified t3x of the workspaces extension with a tested solution. I know that it is not nice to just attach the t3x and do not create patches. I am very sorry but I have no time this week to create these patches, but I will do this later.</p>
<p>Nevertheless some feedback if you like these features in general would be nice.</p> TYPO3 Core - Feature #32544 (Accepted): 4 eyes principe for publishing elementshttp://forge.typo3.org/issues/325442011-12-14T15:34:15ZSonja Schubertsonja.scholz@typo3.org
<p>For one of our customers with a big TYPO3 we needed a feature called 4-eyes principe. Some use cases:</p>
<ol>
<li>User A edits something in workspace.</li>
<li>User A sends the change to next stage</li>
<li>User A directly publish his change to live -> This is wrong, because maybe he had a mistake and noone else checked the change</li>
</ol>
<p>Correct would be:</p>
<ol>
<li>User A edits something in workspace</li>
<li>User A sends the change to next stage</li>
<li>User B checks the change and publishs it</li>
</ol>
<p>Also possible and correct:</p>
<ol>
<li>User A edits something in workspace</li>
<li>User A sends the change to next stage</li>
<li>User B checks it and changes something in the element</li>
<li>User B tries to publish the element and will get an error, because he edited the element at the latter</li>
<li>User A can check the change from User A and publish the change</li>
</ol>
<p>We developed this feature configurable, so it is possible to activate 4-eyes princip in extEMConf, otherwise everything works like before. In my opinion it would also be nice to have this enable-checkbox in workspace config instead of extEMconf. But this needs to be discussed by the workspace team.</p>
<p>I attached the modified t3x of the workspaces extension with a tested solution. I know that it is not nice to just attach the t3x and do not create patches. I am very sorry but I have no time this week to create these patches, but I will do this later.</p>
<p>Nevertheless some feedback if you like this feature in general would be nice.</p>
<p>Greets,</p>
<p>Sonja</p> TYPO3 Core - Feature #32543 (Closed): Some improvements for notification mail - new marker, list ...http://forge.typo3.org/issues/325432011-12-14T15:17:50ZSonja Schubertsonja.scholz@typo3.org
<p>It would be nice to have some improvements for the workspace notification mails sent by version extension.</p>
<ul>
<li>Nice list of elements in email if multiple elements were sent to next stage in one run</li>
<li>new marker ELEMENT_NUMBER so numerable the list of elements</li>
<li>new pageTsConfig option cropPathTitlesAfter to crop titles in email after number of chars</li>
</ul>
<p>I attached the modified t3x of the version extension with a tested solution. I know that it is not nice to just attach the t3x and do not create patches. I am very sorry but I have no time this week to create these patches, but I will do this later.</p>
<p>Nevertheless some feedback if you like these features in general would be nice.</p> TYPO3 Core - Bug #29780 (Closed): BE Design: Very long page titles break do not look nicehttp://forge.typo3.org/issues/297802011-09-14T15:10:15ZSonja Schubertsonja.scholz@typo3.org
<p>Module Page -> Choose page -> Edit content element on a page with very very long page title.</p>
<p>The form of the content element is displayed as ever, but the page path in the top right corner is wraped in two lines.</p>
<p>Would be nice to get very long page titles croped in the top right corner.</p> TYPO3 Core - Bug #29779 (Closed): Sometimes editor gets an permission error in workspace modulehttp://forge.typo3.org/issues/297792011-09-14T15:01:46ZSonja Schubertsonja.scholz@typo3.org
<p>Sometimes, an editor gets an permission error when trying to delete a workspace change via workspace module.</p>
<p>Error message is "No permission", the deletion is performed nevertheless which is OK because the editor itself creates the workspace change and is definitely allowed to do this. Only the error message is annoying.</p>
<p>Unfortunately I can not reproduce the error message every time, so i can not give more information at the moment. Maybe someone else has the same problem and more information?</p> TYPO3 Core - Bug #29595 (Closed): Update of a DB record via extbase fails on MSSQLhttp://forge.typo3.org/issues/295952011-09-09T13:16:21ZSonja Schubertsonja.scholz@typo3.org
<p>I have an extbase extension with model and repository. When I try to update an entry via extbase repositiory update() function it fails as soon as there are special umlauts in the entry.</p>
<p>When I overwrite the update() function in my repository and update the entry via GLOBAL_DB->execUPDATEquery it works. The field/column with the umlauts is of type varchar.</p>
<p>In my opinion either extbase repsitory or at the end DBAL does not respect/convert umlauts in the update.</p>
<p>By the way: When the update fails, a new entry is created. The add() function seems not to have the problem with umlauts...</p> TYPO3 Core - Feature #27682 (Closed): Recycler - Workspace Support including deleted pages in wor...http://forge.typo3.org/issues/276822011-06-24T14:38:37ZSonja Schubertsonja.scholz@typo3.org
<p>It would be a nice feature if the recycler module would also work in worspace mode. Additionally it would be nice to get the following working:</p>
<p>- User switches to workspace mode<br />- User creates a completely new element<br />- User deletes the element again so it's deleted=1 for place holder and version element in DB<br />- User goes to recycler module and restores the version element again. The two elements are changed in background to deleted=0 again and visible in workspace mode</p>
<p>Greets,</p>
<p>Sonja</p> TYPO3 Core - Feature #27097 (Closed): Preview: Options should be configurable via page/userTSconfighttp://forge.typo3.org/issues/270972011-05-27T18:39:06ZSonja Schubertsonja.scholz@typo3.org
<p>In Workspace preview there are several views possible at the moment: Slider, Vertical, Horizontal</p>
<p>There should be a new option "Only Workspace" which shows only the workspace in a frame.</p>
<p>Further all options should be configurable va page/userTSconfig.</p> TYPO3 Core - Bug #27051 (Closed): BE user is not able to expand page in pagetree if he have only ...http://forge.typo3.org/issues/270512011-05-26T14:52:20ZSonja Schubertsonja.scholz@typo3.org
<p>The BE user is not able to expand the top page in pagetree if he have only exactly one mountpoint.</p>
<p>This is caused by the following condition in t3lib/tree/pagetree/class.t3lib_tree_pagetree_dataprovider.php</p>
<p>line 287 in 4.5.2 core<br />if (count($mountPoints) <= 1) {<br /> $subNode->setExpanded(TRUE);<br /> $subNode->setCls('typo3-pagetree-node-notExpandable');<br />}</p>
<p>As soon as I change the condition to only < it works..</p>
<p>Sorry have no git at the moment, otherwise you would have posted a patch.</p>
<p>Kind regards,<br />Sonja</p> TYPO3 Core - Bug #25960 (Closed): Some DB fields needs to be varchar to support MSSQLhttp://forge.typo3.org/issues/259602011-04-14T11:58:07ZSonja Schubertsonja.scholz@typo3.org
<p>There are some fields in the sys_workspace table, which are of type text at the moment. This is a problem for MSSQL, as MSSQL is not able to compare type text fields in a query like "adminusers = '5'".</p>
<p>Solution is to change the types of these three fields (adminusers, members, reviewers) to varchar(4000). Tested in a MSSQL database and a MySQL database, works for both.</p>
<p>I will attach a patch soon.</p> TYPO3 Core - Bug #25768 (Closed): Grid View: It is not possible to move a content element to anot...http://forge.typo3.org/issues/257682011-04-05T15:13:03ZSonja Schubertsonja.scholz@typo3.org
<p>When someone uses the page/grid view it is not possible to move a content element with its all language overlay elements to another column of the grid, as there is no button for that like "cut" and then "paste into".</p>
<p>It is possible to change the sorting in the own column of the element, but that is not enough to change the column.</p>
<p>Temporary, the user has to edit the content element and then change the "column" their, which is not a good solution for the normal user.</p> TYPO3 Core - Bug #25484 (Closed): RTE Remove format: German fieldset legend does not wrap in IEhttp://forge.typo3.org/issues/254842011-03-31T11:25:36ZSonja Schubertsonja.scholz@typo3.org
<p>It's only a very small bug, but it would be nice, if the popup would be more wide as soon as the label is longer, so the label is not cropped.</p> TYPO3 Core - Bug #25165 (Closed): IE8 Browser crashes as soon as content element is saved/closedhttp://forge.typo3.org/issues/251652011-02-24T16:10:47ZSonja Schubertsonja.scholz@typo3.org
<p>As soon as I edit a normal text with image content element and press the save button the browser crashes and the browser windows with the website needs to be closed. Please have a look at the screenshots With Firefox there's no problem. Sometimes the error doesn't occur on pressing the save/close but the close button. The error also occurs on saving the tt_address element form.</p>
<p>typo3 4.5.0<br />https certificate for BE login<br />IE8<br />(issue imported from #M17751)</p>