TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692018-12-04T09:03:38ZTYPO3 Forge
Redmine TYPO3 Core - Bug #87068 (Closed): Use BackendUtility::getPagesTSconfig in TSFE when getting tsconfighttp://forge.typo3.org/issues/870682018-12-04T09:03:38ZSoren Mallingsoren@meteko.dk
<p>Inside the TypoScriptFrontendController the method getPagesTSconfig is used to get the tsconfig from page records. Both via the TSconfig fields but also "included" tsconfig.</p>
<p>The method consist of the same code as BackendUtility::getRawPagesTSconfig (which is called by getPagesTSconfig) - the main difference is, that the frontend method doesn't call emit the signal GetPagesTSconfigPreIncludeSignal to have extensions auto include. So, this gives a different functionality from backend to frontend.</p>
<p>A usecase is inclusion of gridelements layouts. This is used in the frontend for rendering. But when TSFE gets the tsconfig, the signal is not emitted and the tsconfig is not being filled with the layout configuration like it does in the backend</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 - Feature #50360 (Accepted): Having only one record type in "New record" should forwar...http://forge.typo3.org/issues/503602013-07-24T10:49:55ZSoren Mallingsoren@meteko.dk
<p>By using mod.web_list.allowedTables you can adjust the allowed tables. This is useful in storage folders, where you might only want one single record type.</p>
<p>The usability issue comes, when the editor has to click on that single record type. Instead we should forward the editor to the form for that specific record type allowed.</p>
<p>I suggest this being a core feature. In case of objection I suggest a hook, giving the possibility to introduce the functionality via a extension.</p> TYPO3 Core - Bug #35070 (Closed): [Install tool] Image processing doesn't run script of file existshttp://forge.typo3.org/issues/350702012-03-21T10:47:45ZSoren Mallingsoren@meteko.dk
<p>Try this:</p>
<p>Make sure that you have been through the Image processing module once, so the test images have been created.</p>
<p>Enter a wrong path in im_path (or imagine that you move a installation, and the path to IM changes) and go to image processing again.</p>
<p>Install tool will report that everything went perfectly and you will see the create test images.</p>
<p><a class="external" href="https://skitch.com/sorenmalling/8m7e8/new-typo3-site-typo3-4.7-dev">https://skitch.com/sorenmalling/8m7e8/new-typo3-site-typo3-4.7-dev</a></p>
<p>The case is, that no new images are trying to be created (with the wrong im_path!) and you will just see the images from typo3temp</p>
<p>Try and find the image in the typo3temp folder, delete it and rerun the Image Processing, you will now get a error beacause the typo3temp doesn't exists and Image processing will try and create it, with a wrong im_path</p> TYPO3 Core - Task #30920 (Closed): EXT:recycler: defaultTable should be configurablehttp://forge.typo3.org/issues/309202011-10-14T11:22:07ZSoren Mallingsoren@meteko.dk
<p>The default table for content elements, should be configurable on both User TSConfig and Page TSConfig level</p> TYPO3 Core - Task #29774 (Closed): Improve information in show_item.php http://forge.typo3.org/issues/297742011-09-14T14:10:08ZSoren Mallingsoren@meteko.dk
<p>Currently the "Info" popup (show_item.php) provides information with raw data from sys_refindex. A editor will get informations such as actual table name from the database and a uid - but no real hint to what records it's all about.</p>
<p>This patch provides information about table (name shown in list module), field name ( as shown in TCEforms) for both references tables</p> TYPO3 Core - Bug #25276 (Closed): Backend toolbar (additionalBackendItems) doesn't use a common C...http://forge.typo3.org/issues/252762011-03-07T19:21:48ZSoren Mallingsoren@meteko.dk
<p>The backend toolbar with clear cache, bookmarks etc. doesn't use a common css class for styling the drop down. This makes it harder than necessary to create your own additionalBackendItems, as you will have to introduce new css markers yourself</p>
<p>(issue imported from #M17888)</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 #24275 (Closed): "Marked as container for" not shown as select boxhttp://forge.typo3.org/issues/242752010-12-02T13:54:40ZSoren Mallingsoren@meteko.dk
<p>"Mared as container for" which gives the possibility to add a icon to the created page, isn't corectly rendered as selector box (see attachment)</p>
<p>(issue imported from #M16648)</p> TYPO3 Core - Bug #24273 (Closed): help_aboutmoules hardcoded as start up module - returns error i...http://forge.typo3.org/issues/242732010-12-02T13:24:03ZSoren Mallingsoren@meteko.dk
<p>With great features comes great responsibility ;)</p>
<p>As we are now able to uninstal former hardcodede extensions, some issues are shown.</p>
<p>If you uninstall the "aboutmodules" extension and haven't changed your "start up" module, the following error will be shown in the javacsript console/debug console</p>
<p>[string] help_aboutmodules was not found in modules</p>
<p>which is correct. The reason for this issue is at line 119 in t3lib/class.t3lib_beuserauth.php</p>
<pre><code>var $uc_default = Array(<br /> 'interfaceSetup' => '', // serialized content that is used to store interface pane and menu positions. Set by the logout.php-script<br /> 'moduleData' => Array(), // user-data for the modules<br /> 'thumbnailsByDefault' => 0,<br /> 'emailMeAtLogin' => 0,<br /> 'condensedMode' => 0,<br /> 'noMenuMode' => 0,<br /> 'startModule' => 'help_aboutmodules', <------ HERE</code></pre>
<p>The "aboutmodules" is hardcoded as startup module and only changed, if you as a user changes the settings.</p>
<p>What should be done here? Is it a administrator responsibility to change the default module for created users if he/she uninstall the default startup module?</p>
<p>(issue imported from #M16646)</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 #23849 (Closed): No "Page types" icon in be_group editing, when using rendermode...http://forge.typo3.org/issues/238492010-10-27T09:39:38ZSoren Mallingsoren@meteko.dk
<p>In the install tool, find the setting "accessListRenderMode" (great setting, that I haven't found before!). Give it the value "checkbox".</p>
<p>Go and edit a be_group. Go to the "Page types" and find the page types, listed with checkboxes. But, the page type icons are missing/"dead"</p>
<p>(issue imported from #M16138)</p> TYPO3 Core - Bug #23599 (Closed): Sysext Modules are shown in Module Menu, even though extensions...http://forge.typo3.org/issues/235992010-09-24T13:47:46ZSoren Mallingsoren@meteko.dk
<p>After File -> List was moved into a sysext it was possible to uninstall it.</p>
<p>The problem is that in t3lib/stddb/tables.php (line 444) it makes the file -> list module visible with the following array (not depending on the if the extension is installed or not)</p>
<p>$TBE_MODULES = array(<br /> 'web' => 'list,info,perm,func',<br /> 'file' => 'list',<br /> 'user' => 'ws',<br /> 'tools' => 'em',<br /> 'help' => 'about,cshmanual'<br />);</p>
<p>Clicking the "File list" module returns a blank page.</p>
<p>(issue imported from #M15794)</p> TYPO3 Core - Bug #23582 (Closed): Docheader (save, save+view, save+close etc) missinghttp://forge.typo3.org/issues/235822010-09-23T09:43:08ZSoren Mallingsoren@meteko.dk
<p>Editing/creating new elements in any tables, no buttons are shown in the top.</p>
<p>Check out screenshot</p>
<p>(issue imported from #M15771)</p> TYPO3 Core - Bug #22908 (Closed): Suggest wizard result is misplaced and with repeated backgroundhttp://forge.typo3.org/issues/229082010-06-17T00:04:38ZSoren Mallingsoren@meteko.dk
<p>Using the latest truck, the result from the "Suggest" wizard is misplaced and the background is repeated (look at screenshot)</p>
<p>(issue imported from #M14758)</p>