TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692015-04-15T11:08:15ZTYPO3 Forge
Redmine TYPO3 Core - Bug #66429 (Closed): Remove IdentityMaphttp://forge.typo3.org/issues/664292015-04-15T11:08:15ZMathias Brodalambrodala@pagemachine.de
<p>The <code>IdentityMap</code> class has been deprecated since 6.1 and should be removed now.</p>
<p>Within <code>Repository</code> it is completely unused already by the core.</p>
<p>In the <code>DataMapper</code> it is still used but can be simply replaced with calls to the persistence session instead.</p>
<p>One huge advantage is being able to trigger garbage collection for mapped objects after unregistering them from the persistence session which can free a lot of memory.</p> TYPO3 Core - Bug #66411 (Closed): New locking API exceptions too generichttp://forge.typo3.org/issues/664112015-04-14T09:57:35ZMathias Brodalambrodala@pagemachine.de
<p>The new locking API currently only uses <code>RuntimeException</code> to hint at errors during lock acquisition.</p>
<p>While this already has the disadvantage of catching other @RuntimeException@s the issue becomes rather clear with the non-blocking example:</p>
<pre>
try {
$result = $locker->acquire(LockingStrategyInterface::LOCK_CAPABILITY_SHARED | LockingStrategyInterface::LOCK_CAPABILITY_NOBLOCK);
catch (\RuntimeException $e) {
if ($e->getCode() === 1428700748) {
// some process owns the lock, let's do something else meanwhile
}
}
</pre>
<p>This requires knowing about this special case and knowing the magic number here. A dedicated exception would make this clearer.</p> TYPO3 Core - Bug #66347 (Closed): Alternative text used as link title in File Linkshttp://forge.typo3.org/issues/663472015-04-10T10:40:46ZMathias Brodalambrodala@pagemachine.de
<p>If an alternative text was specified for a file, it is used as link title for file, preview and icon in File Links.</p>
<p>This should be fixed to use the title instead.</p> TYPO3 Core - Bug #65058 (Closed): Fix new content element wizard links click areahttp://forge.typo3.org/issues/650582015-02-13T14:39:20ZMathias Brodalambrodala@pagemachine.de
<p>With <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Port Content Element Wizard to Bootstrap (Closed)" href="http://forge.typo3.org/issues/64892">#64892</a> a regression has been introduced wrt the click area of links in the new content element wizard, see <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Format new content element wizard links as inline-block (Closed)" href="http://forge.typo3.org/issues/56063">#56063</a> for details.</p> TYPO3 Core - Feature #62960 (Closed): Add hook for mailer initializationhttp://forge.typo3.org/issues/629602014-11-14T16:58:17ZMathias Brodalambrodala@pagemachine.de
<p>The <code>TYPO3\CMS\Core\Mail\Mailer</code> class is the central instance for mailing and should have a hook called upon initialization.</p>
<p>This hook could be used e.g. to register Swift mailer plugins at runtime.</p> TYPO3 Core - Feature #60822 (Closed): Get class tag values via reflectionhttp://forge.typo3.org/issues/608222014-08-06T12:09:14ZMathias Brodalambrodala@pagemachine.de
<p>The <code>ReflectionService</code> currently allows getting tag values for properties and methods. The same should be available for classes since the data is already collected in <code>ReflectionService::reflectClass()</code> anyways.</p>
<p>Suggestion: add <code>ReflectionService::getClassTagsValues($className)</code> and <code>ReflectionService::getClassTagValues($className, $tag)</code> and use the existing data.</p> TYPO3 Core - Bug #56418 (Closed): Missing margin/padding on content element fieldshttp://forge.typo3.org/issues/564182014-02-28T10:12:47ZMathias Brodalambrodala@pagemachine.de
<p>Editing a content element in the backend currently shows some fields without margin/padding:</p>
<p><img src="http://forge.typo3.org/attachments/download/26156/ce-fields-padding.png" alt="" loading="lazy" /></p> TYPO3 Core - Task #56177 (Closed): Windows issues with long CSV file name from commit 2db3d30http://forge.typo3.org/issues/561772014-02-21T11:49:53ZMathias Brodalambrodala@pagemachine.de
<p>The commit 2db3d30 added the following file:</p>
<blockquote>
<p>typo3/sysext/workspaces/Tests/Functional/DataHandling/InlineRelationalRecordEditing/CommaSeparatedValue/DataSet/Assertion/createAndLocalizeParentContentRecordWithHotelAndOfferChildRecordsAndDiscardLocalizedParentRecord.csv</p>
</blockquote>
<p>It seems like this file path is too long for either Windows or Git on Windows. If you pull/merge this commit, the file cannot be created, if you do a clean clone, this file is deleted immediately and cannot be restored.</p>
<p>Suggestion: use a shorter file name.</p> TYPO3 Core - Task #56063 (Closed): Format new content element wizard links as inline-blockhttp://forge.typo3.org/issues/560632014-02-18T09:01:38ZMathias Brodalambrodala@pagemachine.de
<p>The links within the new content element wizard are currently rendered as default inline elements which allows only clicking on the actual text. Even clicking between title and description does not work.</p>
<p>The solution is simple: format these links as inline-block to make the whole link clickable.</p> TYPO3 Core - Bug #56062 (Closed): List bullets in wizard for new content elementshttp://forge.typo3.org/issues/560622014-02-18T08:58:02ZMathias Brodalambrodala@pagemachine.de
<p>Since the introduction of list styles (49b0696) the wizard for new content elements also gets list bullets which yields a odd layout:</p>
<p><img src="http://forge.typo3.org/attachments/download/26082/typo3-62-new-content-element-wizard.PNG" alt="" loading="lazy" /></p> TYPO3 Core - Feature #55757 (Closed): Add PageTSconfig analyzerhttp://forge.typo3.org/issues/557572014-02-07T12:26:47ZMathias Brodalambrodala@pagemachine.de
<p>Similar to what the Template Analyzer does for the TypoScript Object Browser an additional mod function for analyzing PageTS would be useful.</p>
<p>ATM one can only see the currently parsed PageTS for pages. It is impossible to find out where and how this configuration was set which makes debugging for larger sites harder than it should be.</p>
<p>A PageTSconfig analyzer could help here by showing the content of added PageTS files and dynamically added sections like <code>defaultPageTSconfig</code>.</p> TYPO3 Core - Bug #55153 (Closed): Duplicated translation entry for clear cache menu pageshttp://forge.typo3.org/issues/551532014-01-20T09:20:06ZMathias Brodalambrodala@pagemachine.de
<p>With <a class="changeset" title="[TASK] Cache menu needs clear namings and permissions With the introduction of the grouping mech..." href="http://forge.typo3.org/projects/typo3cms-core/repository/1749/revisions/1b83cad80a4cffe054faea3ec1f30d7b18389942">1b83cad</a> the clear cache menu items where reworked. This however introduced a duplicated translation entry for the "pages" item. (<code>rm.clearCacheMenu_pages</code>)</p> TYPO3 Core - Task #53455 (Closed): Update backend page titlehttp://forge.typo3.org/issues/534552013-11-08T15:22:28ZMathias Brodalambrodala@pagemachine.de
<p>Since the introduction text of the install tool has been updated recently for 6.2 I think it is about time the page title of the backend is also updated to reflect the brand change. Thus "TYPO3 <version>" becomes "TYPO3 CMS <version>".</p> TYPO3 Core - Bug #53188 (Closed): REDIRECT_TYPO3_DISABLE_CORE_UPDATER ignoredhttp://forge.typo3.org/issues/531882013-10-29T08:38:13ZMathias Brodalambrodala@pagemachine.de
<p>Using Apache mod_rewrite in certain setups makes environment variables from original requests available in the target request as <code>REDIRECT_<envvar></code>, thus setting <code>TYPO3_DISABLE_CORE_UPDATER</code> becomes <code>REDIRECT_TYPO3_DISABLE_CORE_UPDATER</code>.</p>
<p>The latter is currently not considered by TYPO3, thus the core updater cannot be disabled via the environment variable and the mentioned setup.</p>
<p>See <a href="http://stackoverflow.com/a/9406994" class="external">this Stackoverflow</a> post for an explanation and <a href="https://github.com/apache/httpd/blob/e1fac1db26/modules/http/http_request.c#L389" class="external">link to the Apache source code</a>.</p> TYPO3 Core - Bug #52880 (Closed): Class "\extDirect_DataProvider_BackenduserSettings" not foundhttp://forge.typo3.org/issues/528802013-10-16T10:00:20ZMathias Brodalambrodala@pagemachine.de
<p>Trying to create a template record on a fresh 6.2 beta1 installation fails:</p>
<pre>
Fatal error: Class '\extDirect_DataProvider_BackenduserSettings' not found in .../typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 4149
</pre>
<p>A file search for this class name yields two <code>makeInstance</code> calls:</p>
<ul>
<li>typo3\sysext\backend\Classes\InterfaceState\ExtDirect\DataProvider.php:46 (<code>__construct()</code>)</li>
<li>typo3\sysext\backend\Classes\Tree\Pagetree\ExtdirectTreeCommands.php:361 (<code>addRootlineOfNodeToStateHash()</code>)</li>
</ul>
<p>It seems like the correct path is <code>\TYPO3\CMS\Backend\User\ExtDirect\BackendUserSettingsDataProvider</code> instead.</p>