TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-10-26T09:39:02ZTYPO3 Forge
Redmine TYPO3 Core - Task #102263 (Closed): Return string version of Stringable objects in DataMapper::ge...http://forge.typo3.org/issues/1022632023-10-26T09:39:02ZSoren Mallingsoren@meteko.dk
<p>The DataMapper::getPlainValue expects a object to be a instance of TypeInterface in order to return a plain value.</p>
<p>The TypoInterface holds the `__toString` method - making it `a instance of Stringable`.</p>
<p>Objects/value objects coming from own extensions, not implementing the TypeInterface but being a `Stringable` (either by `implements \Stringable` or having the `__toString` method) throws the exception</p>
<p>`throw new UnexpectedTypeException('An object of class "' . get_class($input) . '" could not be converted to a plain value.', 1274799934);`</p>
<p>Suggestion here, being that the condition also allows a object being a stringable</p>
<p>From: <br />`if (TypeHandlingUtility::isCoreType($input)) {`</p>
<p>To:<br />`if (TypeHandlingUtility::isCoreType($input) || ($input instanceof \Stringable)) {`</p> 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 - Task #63524 (Closed): Use panels for "Template" configurationhttp://forge.typo3.org/issues/635242014-12-02T19:16:05ZSoren Mallingsoren@meteko.dk
<p>Use panel-* classes from Twitter Bootstrap<br />to give a better look and feel when browsing<br />the typoscript tree</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 #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 - Feature #46328 (Closed): Make table field selector easier to select fromhttp://forge.typo3.org/issues/463282013-03-15T14:00:23ZSoren Mallingsoren@meteko.dk
<p>The current selector for fields in a table single view, could have been way better! :-)</p>
<p>We at a TYPO3 Camp showing people how they do this :-)</p>
<p>Happy happy!!!</p> TYPO3 Core - Task #39603 (Closed): Move default columns to a backend_layout configurationhttp://forge.typo3.org/issues/396032012-08-08T00:41:03ZSoren Mallingsoren@meteko.dk
<p>Following the thread</p>
<p><a class="external" href="http://lists.typo3.org/pipermail/typo3-team-core/2012-August/052131.html">http://lists.typo3.org/pipermail/typo3-team-core/2012-August/052131.html</a></p>
<p>We came up with a concept of migrating the default 1,0,2,3 column to a backend_layout configuration</p>
<p>This makes it easier to work with the db_layout.php class, as there will be only one way to render the columns.</p>
<p>This task is a part of implementing drag'n'drop functionality, as this will clean up some code output and only have 1(!) markup</p> TYPO3 Core - Task #38623 (Closed): Remove radio buttons from "new content elements" overviewhttp://forge.typo3.org/issues/386232012-07-04T09:35:43ZSoren Mallingsoren@meteko.dkTYPO3 Core - Task #38621 (Closed): Set default renderMode of newContentElements to 'tabs'http://forge.typo3.org/issues/386212012-07-04T09:12:10ZSoren Mallingsoren@meteko.dk
<p>In order to make the selection of a content element as smooth as possible, and avoid showing not needed content types, default renderMode is set to tabs</p>
<p>Find more information here:</p>
<p><a class="external" href="http://buzz.typo3.org/people/steffen-kamper/article/the-new-content-element-wizard-in-version-43/">http://buzz.typo3.org/people/steffen-kamper/article/the-new-content-element-wizard-in-version-43/</a></p> TYPO3 Core - Feature #38255 (Rejected): Post processors should be extendablehttp://forge.typo3.org/issues/382552012-06-21T15:53:41ZSoren Mallingsoren@meteko.dk
<p>It should be possible to extend postprocessor and add configuration</p>
<p>At this moment the postprocessors are hardcoded to only support "mail" where as postprocessors for stuff like persisting would make the FORM tool great for user registration etc.</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 #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 - 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 - Feature #23589 (Rejected): Popup wizard doesn't close when clicking "save & close"http://forge.typo3.org/issues/235892010-09-24T09:13:24ZSoren Mallingsoren@meteko.dk
<p>Using below configuration in TCA.</p>
<p>The popup window doesn't close, but shows the "parent element" that "popped up" the window, since it's set in the returnUrl and you can't overwrite it.</p>
<p>A solution might be to overwrite the returnUrl, would this be accepted as a solution? </p>
<pre><code>'categories' => array(<br /> 'exclude' => 0,<br /> 'label' => 'LLL:EXT:mediadatabase/Resources/Private/Language/locallang_db.xml:tx_mediadatabase_domain_model_media.categories',<br /> 'config' => array(<br /> 'type' => 'select',<br /> 'foreign_table' => 'tx_mediadatabase_domain_model_category',<br /> 'size' => 10,<br /> 'maxitems' => 20,<br /> 'wizards' => array(<br /> '_PADDING' => 2,<br /> '_VERTICAL' => 1,<br /> 'add' => Array(<br /> 'type' => 'popup',<br /> 'title' => 'LLL:EXT:tt_news/locallang_tca.xml:tt_news_cat.createNewParentCategory',<br /> 'icon' => 'add.gif',<br /> 'params' => Array(<br /> 'table'=>'tx_mediadatabase_domain_model_category',<br /> 'pid' => '###CURRENT_PID###',<br /> 'setValue' => 'append',<br /> ),<br /> 'script' => 'wizard_add.php',<br /> 'JSopenParams' => 'height=280,width=465,status=0,menubar=0,scrollbars=1',<br /> ),<br /> ),<br /> ),<br /> ),</code></pre>
<p>(issue imported from #M15782)</p>