TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692019-03-11T15:37:36ZTYPO3 Forge
Redmine TYPO3 Core - Bug #87884 (Closed): Root page of page tree suddenly gets slug "/1"http://forge.typo3.org/issues/878842019-03-11T15:37:36ZSoren Mallingsoren@meteko.dk
<p>This is a issue created for Benni Mack to follow up on a Slack conversation</p>
<p><a class="external" href="https://typo3.slack.com/archives/C2ZKN8P7G/p1551805852037400">https://typo3.slack.com/archives/C2ZKN8P7G/p1551805852037400</a></p> TYPO3 Core - Bug #87841 (Closed): Sitemap generation doesn't take request language into accounthttp://forge.typo3.org/issues/878412019-03-05T08:52:51ZSoren Mallingsoren@meteko.dk
<p>The sitemap.xml only takes content from the default language upon creation.</p>
<p>Case:</p>
<p>on domain.dk/sitemap.xml the sitemap is created with all content from the default language (in this case "Danish")</p>
<p>on domain.net/sitemap.xml it was expected to contain only content from the langauge of that site. Instead it takes the content of the default language.</p>
<p>Issue has been identified with Richard Haeser</p>
<p>Sitemaps can be found <a class="external" href="http://www.meteko.dk/sitemap.xml">www.meteko.dk/sitemap.xml</a> and <a class="external" href="http://www.meteko.net/sitemap.xml">www.meteko.net/sitemap.xml</a></p>
<p>Site configuration</p>
<pre>
rootPageId: 1
base: 'https://meteko.dk'
baseVariants: { }
languages:
-
title: Danish
enabled: true
languageId: '0'
base: /
typo3Language: da
locale: da_DK.utf-8
iso-639-1: da
navigationTitle: ''
hreflang: da-DK
direction: ltr
flag: dk
-
title: English
enabled: true
languageId: '2'
base: 'https://meteko.net/'
typo3Language: default
locale: en_US.utf-8
iso-639-1: en
navigationTitle: English
hreflang: en-US
direction: ltr
fallbackType: strict
flag: gb
errorHandling:
-
errorCode: '404'
errorHandler: Page
errorContentSource: '15'
routes: { }
routeEnhancers:
NewsPlugin:
type: Extbase
extension: News
plugin: Pi1
routes:
-
routePath: '/{news_title}'
_controller: 'News::detail'
_arguments:
news_title: news
defaultController: 'News::list'
aspects:
news_title:
type: PersistedPatternMapper
tableName: tx_news_domain_model_news
routeFieldPattern: '^(?P<path_segment>.+)$'
routeFieldResult: '{path_segment}'
PageTypeSuffix:
type: PageType
map:
sitemap.xml: 1533906435
</pre> TYPO3 Core - Bug #87581 (Closed): Reintroduce removed page tree TSconfig settingshttp://forge.typo3.org/issues/875812019-01-30T09:52:25ZSoren Mallingsoren@meteko.dk
<p>In issue <a class="external" href="https://forge.typo3.org/issues/82919">https://forge.typo3.org/issues/82919</a> a number of page tree settings was removed with the background of they werent used.</p>
<p>Feedback from users and clients have made us aware that at least of them was very actively used (excludeDoktypes) to hide specific doktypes in a pagetree. The client had 40.000 pages of a "Article" doktype that wasn't meant to be displayed in the tree.</p>
<p>This issue and following patch is solely to bring back the excludeDoktypes setting. None of the other settings are touched in this patch</p> 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 #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 #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 #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 #27510 (Closed): Pagetree not respecting TCAdefaultshttp://forge.typo3.org/issues/275102011-06-17T10:55:28ZSoren Mallingsoren@meteko.dk
<p>When creating pages from the drag & drop pagetree the TCAdefaults settings are not respected. Creating pages the old way still respects TCAdefaults though</p>
<p><a class="external" href="http://bugs.typo3.org/bug_view_advanced_page.php?bug_id=18150">http://bugs.typo3.org/bug_view_advanced_page.php?bug_id=18150</a></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 #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 #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> 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 #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 #22287 (Closed): Wrong flashmessage when clearing temporary datahttp://forge.typo3.org/issues/222872010-03-17T08:05:44ZSoren Mallingsoren@meteko.dk
<p>While fixing 0012202 i found out that a wrong flashmessage was shown when clearing temporary data.</p>
<p>A message saying "User setting was saved" was displayed, this should of course be a "Temporary data clared" message</p>
<p>(issue imported from #M13832)</p>