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 - 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 - 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 - Bug #83468 (Closed): Custom icon for "Folder" is not shownhttp://forge.typo3.org/issues/834682018-01-04T14:01:34ZSoren Mallingsoren@meteko.dk
<p>I've registered a custom icon for the "Contains" selector in "Page Properties". the code is here</p>
<pre><code class="php syntaxhl" data-language="php"><span class="k">if</span> <span class="p">(</span><span class="no">TYPO3_MODE</span> <span class="o">===</span> <span class="s1">'BE'</span><span class="p">)</span> <span class="p">{</span>
<span class="cd">/** @var \TYPO3\CMS\Core\Imaging\IconRegistry $iconRegistry */</span>
<span class="nv">$iconRegistry</span> <span class="o">=</span> <span class="nc">\TYPO3\CMS\Core\Utility\GeneralUtility</span><span class="o">::</span><span class="nf">makeInstance</span><span class="p">(</span><span class="nc">\TYPO3\CMS\Core\Imaging\IconRegistry</span><span class="o">::</span><span class="n">class</span><span class="p">);</span>
<span class="nv">$iconRegistry</span><span class="o">-></span><span class="nf">registerIcon</span><span class="p">(</span>
<span class="s1">'apps-pagetree-folder-contains-partnerads'</span><span class="p">,</span>
<span class="nc">\TYPO3\CMS\Core\Imaging\IconProvider\FontawesomeIconProvider</span><span class="o">::</span><span class="n">class</span><span class="p">,</span>
<span class="p">[</span>
<span class="s1">'name'</span> <span class="o">=></span> <span class="s1">'rss'</span>
<span class="p">]</span>
<span class="p">);</span>
<span class="p">}</span>
</code></pre>
<p><b>Notice</b> it's a FontAwesome provided icon - dunno if that could cause the missing rendering of the icon</p>
<p>The custom icon is not being displayed in the page tree (see screenshot) but is working as identifier for ex. TCA tables.</p>
<p>!Screen Shot 2018-01-04 at 13.51.18.png!</p>
<p>Choosing the "frontend user" as "Module" gives the expected rendering of the icon, so the support for SVGIcons is working</p>
<p>The icons doesn't seem to be registered in the <defs> part of the pagetree, could that be a reason?</p>
<p>!Screen Shot 2018-01-04 at 14.00.07.png!</p> TYPO3 Core - Feature #49922 (Closed): Allow "additionalWhereClause" for selection of items to pag...http://forge.typo3.org/issues/499222013-07-11T18:23:52ZSoren Mallingsoren@meteko.dk
<p>In user/usergroup specific TSconfig you can set a "additionalWhereClause" for selecting items to the pagetree. This is added to the where clause with a "AND"</p> TYPO3 Core - Bug #49279 (Closed): Exclude doktypes from pagetree by user TSconfighttp://forge.typo3.org/issues/492792013-06-20T09:36:14ZSoren Mallingsoren@meteko.dkTYPO3 Core - Feature #37838 (Closed): Import translation on a per-extension-basehttp://forge.typo3.org/issues/378382012-06-08T11:22:14ZSoren Mallingsoren@meteko.dk
<p>It should be possible to import translation for a single extension, instead of running all extensions.</p>
<p>Another approach could be to move the translation handling out of the extension manager and into a separate module</p> TYPO3 Core - Bug #35322 (Closed): Firefox 11: Multiple RTE on one page fails to "enable" field un...http://forge.typo3.org/issues/353222012-03-28T14:48:20ZSoren Mallingsoren@meteko.dk
<p>This seems to be a Firefox11 issue, only:</p>
<p>In a DAM record, I've git two RTE field placed underneath each other.</p>
<p>The first of the two RTE got the strange issue, of the field not being "enabled"; meaning that you as a editor can't write anything to the field.</p>
<p>If you change to a different tab in the TCEform, and back again, the field is active.</p>
<p>The following Javascript error is thrown (dunno if it's helpful)</p>
<pre>
c.getComputedStyle(g.firstChild.firstChild, null) is null
[Break at this point]
...mo",-1),h=C.getDaysInMonth()-g,e=this.cells.elements,s=this.textNodes,E=(new Dat...
</pre> 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 - Feature #34056 (Closed): Log to sys_log when changes are made to scheduler taskshttp://forge.typo3.org/issues/340562012-02-18T10:53:19ZSoren Mallingsoren@meteko.dk
<p>In order to keep track of who created what task, it would help a lot to have it logged to sys_log like other editing of tt_content element etc.</p> TYPO3 Core - Task #30296 (Closed): Linkvalidator should have a hook for report markershttp://forge.typo3.org/issues/302962011-09-26T16:36:03ZSoren Mallingsoren@meteko.dk
<p>The Linkvalidator scheduler task should provide hooks within the markers, in order for administrators to create more detailed reports.</p>
<p>This hook gives the possibility to get the information about a page, and use it for any data purpose (user in charge, last update etc.)</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>