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 - 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 - 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 - 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 #28426 (Closed): Only one panel is visible at a timehttp://forge.typo3.org/issues/284262011-07-24T15:49:46ZSoren Mallingsoren@meteko.dk
<p>Panels inside each tab ("Basic form elements", "Predefined form elements", "Content elements" etc.) are closed when ever a new panel is opened.</p>
<p>This makes the user interface "jump up and down" and position of a expected panel.</p> TYPO3 Core - Feature #28425 (Closed): Senders e-mail address is a required fieldhttp://forge.typo3.org/issues/284252011-07-24T15:46:14ZSoren Mallingsoren@meteko.dk
<p>In the "Form" tab, the field "Email address of the sender" is a required field.</p>
<p>The sender email should be able to be set, based on a field in the form.</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 #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 #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>