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 #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 - 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 #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 - 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 - 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 #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 - Feature #27345 (Closed): Move "Appearance" tab before "Access" tabhttp://forge.typo3.org/issues/273452011-06-10T11:56:21ZSoren Mallingsoren@meteko.dk
<p>The use of settings in the "Appearance" tab are most likely related to setting in tabs placed before the "Access" tab.</p>
<p>The "Appearance" should be moved before the "Access" tab to give a correct workflow</p> TYPO3 Core - Feature #26103 (Closed): EXT:felogin templateFile should be configurable through a c...http://forge.typo3.org/issues/261032011-04-19T10:35:13ZSoren Mallingsoren@meteko.dk
<p>The HTML template for EXT:felogin should be configurable.</p>
<p>Therefore, css_styled_content got a new constant named</p>
<p>styles.content.loginform.templateFile</p>
<p>as default it holds the hardcodede value from ECT:felogin/ext_typoscript_setup.txt (EXT:felogin/template.html)</p> TYPO3 Core - Feature #22372 (Closed): [Feature request] Add return_url to link even though page d...http://forge.typo3.org/issues/223722010-04-03T15:02:49ZSoren Mallingsoren@meteko.dk
<p>This is a feature request:</p>
<p>Issue:<br />When creating a link in RTE it would be great to have the possibility of adding the current page to the link as a return_url GET parameter.</p>
<p>Ex. if linking to a login page, from one page. Because the login page isn't restrictd, you don't get the return_url GET parameter, and the user will then have to take action in order to get back to the correct page</p>
<p>Solution:<br />Add a checkbox to the link generator, where you can tick of "Add current page as return_url" (or something similar) which then add the current page to the created link</p>
<p>I would like to try and write the patch, as we are in need of this function in a project I'm working on, but i would like to hear whether or not this function could be interesting for the rtehtmlarea extension?</p>
<p>(issue imported from #M13994)</p>