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 - Feature #87823 (Closed): Introduce "class" to StaticRouteResolver configurationhttp://forge.typo3.org/issues/878232019-03-02T18:26:47ZSoren Mallingsoren@meteko.dk
<p>The StaticRouteResolver can handle "staticText" and "uri".</p>
<p>I suggest a new type being a class->method()</p>
<p>Reason for this:</p>
<p>The PSR middleware returns a Response once it's processed. The Request object is present and the current site including it's configuration.</p>
<p>I see some great use case for static routes like</p>
<p>/blog<br />/news</p>
<p>and similar, that can respond to routes that a editor doesn't need to create. The class can then render a typoscript object, alternative template or similar.</p>
<p>Alternatively, this issue can be closed with the descission of saying "you can implement such PSR yourself and should not be a core thing" - I will completely respect that descission.</p> TYPO3 Core - Feature #86962 (Closed): Asset pipeline: Only include assets for rendered content el...http://forge.typo3.org/issues/869622018-11-21T09:48:08ZSoren Mallingsoren@meteko.dk
<p>Inspired by my teachings after working a bit with Ruby on Rails and the keynote as T3CON18 about speed I would like to present a feature on Asset pipeline for rendered content element.</p>
<p>The idea/concept is as so:</p>
<p>Given the tt_content elements that are being rendered, the TYPO3 rendering engine can include only assets (css/js) that are related to the content element or plugin.</p>
<p>For example. Here is a number of content element in colPos = 0. The idea is not limited to a single colPos, but let's keep it simple :)</p>
<pre>
[CType: text]
[CType: image]
[CType: Plugin -> Extbase plugin]
[CType: menu_sitemap]
</pre>
<p>Giving a path configuration similar to how content elements are given a path to it's HTML files</p>
<pre>
lib.assetPipeline {
css.10 = EXT:awesomesite/Resources/Public/Assets/Css/Component/
}
</pre>
<p>The rendering will look at the rendered CType and look for EXT:awesomesite/Resources/Public/Assets/Css/Component/[CType].css to include into the pageGenerators includeCSS part. If you enable concate and compress css you will have a CSS file build for the content of that site and no bloated CSS/JS stuff.</p>
<p>I created a POC for extbase related rendering. Add this code block to the ActionController -> renderAssetsForRequest() method</p>
<pre><code class="php syntaxhl" data-language="php"> <span class="nv">$assetFile</span> <span class="o">=</span> <span class="nc">GeneralUtility</span><span class="o">::</span><span class="nf">getFileAbsFileName</span><span class="p">(</span><span class="s1">'EXT:'</span> <span class="mf">.</span> <span class="nv">$this</span><span class="o">-></span><span class="nf">getControllerContext</span><span class="p">()</span><span class="o">-></span><span class="nf">getRequest</span><span class="p">()</span><span class="o">-></span><span class="nf">getControllerExtensionKey</span><span class="p">()</span> <span class="mf">.</span> <span class="s1">'/Resources/Public/Assets/Css/'</span> <span class="mf">.</span> <span class="nv">$this</span><span class="o">-></span><span class="nf">getControllerContext</span><span class="p">()</span><span class="o">-></span><span class="nf">getRequest</span><span class="p">()</span><span class="o">-></span><span class="nf">getControllerName</span><span class="p">()</span> <span class="mf">.</span> <span class="s1">'.css'</span><span class="p">);</span>
<span class="k">if</span> <span class="p">(</span><span class="nv">$assetFile</span> <span class="o">!==</span> <span class="s1">''</span><span class="p">)</span> <span class="p">{</span>
<span class="nv">$file</span> <span class="o">=</span> <span class="nc">PathUtility</span><span class="o">::</span><span class="nf">stripPathSitePrefix</span><span class="p">(</span><span class="nv">$assetFile</span><span class="p">);</span>
<span class="nv">$pageRenderer</span><span class="o">-></span><span class="nf">addCssFile</span><span class="p">(</span>
<span class="nv">$file</span>
<span class="p">);</span>
<span class="p">}</span>
</code></pre>
<p>The goal of this feature is to bring down the actual bytes being sent and served on each page load.</p>
<a name="Cons"></a>
<h2 >Cons<a href="#Cons" class="wiki-anchor">¶</a></h2>
<p>Given the dynamic combinations of content this will create a larger number of files than usual</p> TYPO3 Core - Feature #52080 (Rejected): Pre- and Post-process hook in DatabaseConnection for sql_...http://forge.typo3.org/issues/520802013-09-17T15:55:06ZSoren Mallingsoren@meteko.dk
<p>Since Extbase moved to use the TYPO3 Database API it's possible to add even more content/record security as focus can be put at one single entry point to the database.</p>
<p>This change introduces two new hooks (four, including the once for DBAL) before and after the general sql_query (used by Extbase).</p>
<p>From here you get the created query and the parent DatabaseConnection object. From here you can ex. check whether or not access should be granted to records fetched.</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 - 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 #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 #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>