TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692018-11-11T18:24:11ZTYPO3 Forge
Redmine TYPO3 Core - Bug #86909 (Closed): tt_content examples in "Page" module does not respect CTypes ad...http://forge.typo3.org/issues/869092018-11-11T18:24:11ZSoren Mallingsoren@meteko.dk
<a name="Case"></a>
<h2 >Case<a href="#Case" class="wiki-anchor">¶</a></h2>
<p>I've added a number of items to the tt_content field CType directly via Page TSconfig.</p>
<p>When I add a content element which is added via TSconfig, the backend print "INVALID VALUE (webability_[contentname])". This is due to the $CType_labels property being used for rendering is not taking what is added via TSconfig in to concern.</p>
<a name="Proposed-solution"></a>
<h2 >Proposed solution<a href="#Proposed-solution" class="wiki-anchor">¶</a></h2>
<p>I suggest that we streamline this access of content types, so changes made via tsconfig or any other condition is taken into account and returns a single point of getting these values.</p>
<p>Perhaps a more API-wise solution. A "Content Element Registry" of a kind.</p>
<p>Comments are welcome, I will love to put time into it.</p>
<p>This is finding and suggestion based on the work of EXT:autosite where TSconfig is playing a big part in keeping each pagetree/site clean.</p> TYPO3 Core - Bug #79128 (Closed): "Record history" is shown, even if hidden with TSConfighttp://forge.typo3.org/issues/791282017-01-01T22:50:26ZSoren Mallingsoren@meteko.dk
<p>The tsconfig</p>
<pre>options.showHistory = 0</pre>
<p>is not respected in TYPO3\CMS\Backend\Controller\EditDocumentController in the getButtons() method in the making of the buttonbar.</p>
<p>Actually, a "Record History" buttons is being rendered twice but the TSconfig condition is only checked once.</p>
<p>In the first case, a condition only checks if there is any history</p>
<p><a class="external" href="https://git.typo3.org/Packages/TYPO3.CMS.git/blob/HEAD:/typo3/sysext/backend/Classes/Controller/EditDocumentController.php#l1369">https://git.typo3.org/Packages/TYPO3.CMS.git/blob/HEAD:/typo3/sysext/backend/Classes/Controller/EditDocumentController.php#l1369</a></p>
<p>and then renders the button.</p>
<p>On line 1400</p>
<p><a class="external" href="https://git.typo3.org/Packages/TYPO3.CMS.git/blob/HEAD:/typo3/sysext/backend/Classes/Controller/EditDocumentController.php#l1369">https://git.typo3.org/Packages/TYPO3.CMS.git/blob/HEAD:/typo3/sysext/backend/Classes/Controller/EditDocumentController.php#l1369</a></p>
<p>the condition is checked with the "getNewIconMode" method and respect if it's hidden</p> TYPO3 Core - Bug #79127 (Needs Feedback): Responsive LiveSearch toolbar item is rendered no matte...http://forge.typo3.org/issues/791272017-01-01T20:11:56ZSoren Mallingsoren@meteko.dk
<p><em>This is a result of a rather large work on trying to make the TYPO3 backend custom for a project.</em></p>
<p>The backend layout file Main.html (EXT:backend/Resources/Private/Templates/Backend/Main.html) contains a rendering of a LiveSearchToolbarItem even though a person might not have access</p>
<pre>
<button class="topbar-button topbar-button-search t3js-topbar-button-search">
<core:icon identifier="actions-search" alternativeMarkupIdentifier="inline" />
</button>
</pre>
<p>This causes the search to be printed in responsive view. Since you don't have access to the toolbar item (checkAccess() method from ToolbarItemInterface) you don't get a printed LiveSearch to use.</p>
<p><strong>Solution suggestion</strong></p>
<p>This part of ToolbarItem rendering (including the User Settings wrench icon) could be grouped into a viewhelper to render avaialble toolbar items. Perhaps introduce a rendering API for such things (a section in Fluid, or whatever ways the rendering of the backend is going)</p> TYPO3 Core - Bug #52946 (Closed): ExtensionUtility::configurePlugin doesn't set typoscripthttp://forge.typo3.org/issues/529462013-10-18T11:47:06ZSoren Mallingsoren@meteko.dk
<p>Upgrading to 6.2 beta 1 I've experienced that</p>
<p>TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin -> \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addTypoScript doesn't register/writes the typoscript to the TypoScript Object Browser.</p>
<p>It writes it very well to $GLOBALS['TYPO3_CONF_VARS']['FE']['defaultTypoScript_' . $type . '.']</p>
<p>This seems to be a issue for Extbase only extension as EXT:gridelements got it's typoscript written as it used to</p> TYPO3 Core - Bug #45699 (Closed): Implement pre- and post-hook around SELECT querieshttp://forge.typo3.org/issues/456992013-02-21T11:22:22ZSoren Mallingsoren@meteko.dk
<p>To use in example content/record security, a hook is implemented before and after the SELECT call.</p>
<p>The SELECT call is the only database call without such hook</p> TYPO3 Core - Bug #37906 (Closed): sys_action toolbar items doesn't go to right submodulehttp://forge.typo3.org/issues/379062012-06-11T16:22:47ZSoren Mallingsoren@meteko.dk
<p>The toolbar items in the sys_actions toolbar doesn't go to the right submodule in the "Task center" module - unless the last chosen submodule was "Tasks".</p>
<p>This patch add the "mode" setting, so the right submodule is chosen</p>
<p>How to test:</p>
<p>1. Open "Task Center" <br />2. Choose "Overview" as submodule<br />3. Click a created sys_action from the toolbar<br />4. You are still seeing the overview page</p>
<p>Apply patch and do the same again, you are now redirected to the actual task</p> TYPO3 Core - Bug #28426 (Closed): Only one panel is visible at a timehttp://forge.typo3.org/issues/284262011-07-24T15:49:46ZSoren Mallingsoren@meteko.dk
<p>Panels inside each tab ("Basic form elements", "Predefined form elements", "Content elements" etc.) are closed when ever a new panel is opened.</p>
<p>This makes the user interface "jump up and down" and position of a expected panel.</p> TYPO3 Core - Bug #25056 (Closed): Pagetree: No indication of pages being copied, when copying a b...http://forge.typo3.org/issues/250562011-02-16T11:22:23ZSoren Mallingsoren@meteko.dk
<p>If you copy a large pagetree, there is no indication of the pages being copied. This will make the user think that something went wrong or is broken</p>
<p>(issue imported from #M17612)</p> TYPO3 Core - Bug #25042 (Closed): options.moduleMenuCollapsable does not have any effect on extjs...http://forge.typo3.org/issues/250422011-02-15T13:00:08ZSoren Mallingsoren@meteko.dk
<p>After extjs based modulemenu was introduced the us TSConfig setting "options.moduleMenuCollapsable" does not have any functionality</p>
<p>A <br />(issue imported from #M17595)</p> TYPO3 Core - Bug #12177 (Closed): Closing dialog forces reloadhttp://forge.typo3.org/issues/121772011-01-13T13:46:20ZSoren Mallingsoren@meteko.dk
<p>if you click on the "Close" icon in the upperright corner of a modal window, the list of extensions is force-reloaded. Is this necessary, as you are "aborting" a action so nothing should/would be saved?</p> TYPO3 Core - Bug #23850 (Closed): HSC header is not bold, in be_group "Page types"http://forge.typo3.org/issues/238502010-10-27T09:42:09ZSoren Mallingsoren@meteko.dk
<p>I love the new HSC!</p>
<p>If using accessListRenderMode = checkbox and go to "Page types" in a be_group the first line isn't bold, as in ex. tt_content</p>
<p>(issue imported from #M16139)</p> TYPO3 Core - Bug #22768 (Closed): Wrong icons for elements in "Create new element"http://forge.typo3.org/issues/227682010-05-30T23:05:39ZSoren Mallingsoren@meteko.dk
<p>The "sys_template" got no icon<br />"Domain" doesn't use correct icon<br />"Alternative page language" doesn't use correct icon</p>
<p>(issue imported from #M14543)</p> TYPO3 Core - Bug #22767 (Closed): "Create new element" got a lot of space between possible elementhttp://forge.typo3.org/issues/227672010-05-30T23:03:21ZSoren Mallingsoren@meteko.dk
<p>The list of new element to create got a lot of space, after the new sprite icons has been introduced</p>
<p>(issue imported from #M14542)</p> TYPO3 Core - Bug #22715 (Closed): Writing name of existing database, doesn't use databasehttp://forge.typo3.org/issues/227152010-05-25T19:23:43ZSoren Mallingsoren@meteko.dk
<p>At install tool step 2, you are able to write a new database to create or choose a database from a select list.</p>
<p>If you write the name of a already existing database, the name isn't written to localconf.php and the next step will result in a error.</p>
<p>Solutio:<br />----------<br />check if written databasename exist in array of existing databases and then write it, if true.</p>
<p>Going to a meeting in 20 minutes, but will try to create patch later tonight!<br />(issue imported from #M14478)</p> TYPO3 Core - Bug #21698 (Closed): Extension category title not properly rendered in backendhttp://forge.typo3.org/issues/216982009-11-26T09:43:06ZSoren Mallingsoren@meteko.dk
<p>The extension category title is not rendered properly for the extension not having a category name, it's shown as</p>
<p><em>[]</em></p>
<p>Screenshot attached</p>
<p>(issue imported from #M12771)</p>