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 - 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 #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 #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 - 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 - 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 #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>