TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692018-04-03T12:24:52ZTYPO3 Forge
Redmine TYPO3 Core - Bug #84580 (Closed): "Stop page tree" icon/label unclearhttp://forge.typo3.org/issues/845802018-04-03T12:24:52ZMathias Brodalambrodala@pagemachine.de
<p>The option <strong>Stop page tree</strong> which can be enabled for any page has an unclear icon/label.</p>
<p>The icon is a very simple red "+" and the label only reads <strong>Stop page tree</strong>. There is no clear indication that this option prevents the page tree to render the subtree of the page where this option was enabled.</p>
<p>A better icon/label/indication could be added here.</p> 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 #66350 (Closed): 6.2 static template outdatedhttp://forge.typo3.org/issues/663502015-04-10T10:59:27ZMathias Brodalambrodala@pagemachine.de
<p>The <code>v6.2</code> static template of <code>css_styled_content</code> in the current master is not up to date with changes from the 6.2 branch, namely the title attribute rendering of File Links (see <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Title not used for Filelinks (Closed)" href="http://forge.typo3.org/issues/60429">#60429</a>) and a small style differnce.</p>
<p>This should be updated to ensure exactly the same rendering when using 7.x with the <code>v6.2</code> static template as it is in 6.2 with the latest static template.</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 #66344 (Closed): Some exceptions contain HTML codehttp://forge.typo3.org/issues/663442015-04-10T08:49:07ZMathias Brodalambrodala@pagemachine.de
<p>There are currently 4 exceptions in the core whose messages contain HTML code:</p>
<ul>
<li><code>RuntimeException</code> in <code>TYPO3\CMS\Backend\Controller\LoginController::checkRedirect</code></li>
<li><code>RuntimeException</code> in <code>TYPO3\CMS\Backend\Tree\View\AbstractTreeView::getTree</code></li>
<li><code>RuntimeExceptoin</code> in <code>TYPO3\CMS\Core\Authentication\AbstractUserAuthentication::checkAuthentication</code></li>
<li><code>ExtensionManagerException</code> in <code>TYPO3\CMS\Extensionmanager\Utility\Connection\TerUtility::fetchExtension</code></li>
</ul>
<p>Since exceptions are independent from a specific context, this HTML code should be removed.</p> TYPO3 Core - Task #66327 (Closed): Rename FAL driver count methodshttp://forge.typo3.org/issues/663272015-04-08T14:34:12ZMathias Brodalambrodala@pagemachine.de
<p>With <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: File list always fetches all files in folder (Closed)" href="http://forge.typo3.org/issues/56746">#56746</a> count methods where added to FAL drivers but the naming is not intuitive and should be changed.</p> TYPO3 Core - Task #66323 (Closed): Test more edge cases for trimExplodehttp://forge.typo3.org/issues/663232015-04-08T12:32:18ZMathias Brodalambrodala@pagemachine.de
<p>There are a few more edge cases in light of <a class="issue tracker-4 status-5 priority-4 priority-default closed behind-schedule" title="Task: Performance: improve trimExplode 2nd try (Closed)" href="http://forge.typo3.org/issues/66317">#66317</a> which should be tested with the current code base first.</p> TYPO3 Core - Task #65569 (Closed): Remove deprecated "strict" option from PHPUnit configurationhttp://forge.typo3.org/issues/655692015-03-06T14:42:47ZMathias Brodalambrodala@pagemachine.de
<p>Newer PHPUnit versions have deprecated the <code>strict</code> option, thus this message is shown for every invocation:</p>
<blockquote>
<p>Deprecated configuration setting "strict" used</p>
</blockquote>
<p>This option should be removed.</p> TYPO3 Core - Bug #65488 (Closed): TimeTracker not set for eID scriptshttp://forge.typo3.org/issues/654882015-03-03T15:43:45ZMathias Brodalambrodala@pagemachine.de
<p>With the recent request handler refactoring some breaking changes where introduced, among others the global TimeTracker <code>$GLOBALS['TT']</code> not being set for eID scripts anymore:</p>
<pre>
( ! ) Fatal error: Call to a member function push() on null in /var/www/typo3_src/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php on line 1206
Call Stack
# Time Memory Function Location
1 0.0719 240072 {main}( ) .../index.php:0
2 0.0790 639632 TYPO3\CMS\Core\Core\Bootstrap->run( ??? ) .../index.php:33
3 0.1116 2472944 TYPO3\CMS\Frontend\EidRequestHandler->handleRequest( ) .../Bootstrap.php:195
4 0.1249 2482888 require( '/var/www/typo3conf/ext/routing/Classes/Controller/RoutingController.php' ) .../EidRequestHandler.php:61
5 0.2003 2609712 Causal\Routing\Controller\RoutingController->dispatch( ) .../RoutingController.php:332
6 0.2108 2650536 Causal\Routing\Controller\RoutingController->initTSFE( ) .../RoutingController.php:114
7 0.8588 4934936 TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController->determineId( ) .../RoutingController.php:314
</pre> 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 - Bug #64057 (Closed): Checkbox viewhelper checked attribute not set for objectshttp://forge.typo3.org/issues/640572014-12-30T10:01:10ZMathias Brodalambrodala@pagemachine.de
<p>Given a form object with a property which may contain a list of objects (array/ObjectStorage) as well as a list of checkboxes built from all available objects for that property:</p>
<pre>
<f:form object="{object}" name="object">
<f:for each="{availableObjects}" as="availableObject">
<f:form.checkbox
property="foo"
value="{availableObject}"
multiple="1"/>
</f:for>
</f:form>
</pre>
<p>If you select one of the options, the <code>checked</code> attribute is not properly set on the subsequent form display. This is due to the fact that the <code>CheckboxViewHelper</code> converts the incoming value for the <code>value</code> attribute to an identifier through <code>AbstractFormFieldViewHelper::getValue()</code> but does not do the same for the property value. Thus e.g. an UID like <code>42</code> is searched in an array of objects which will never succeed. (<a href="https://git.typo3.org/Packages/TYPO3.CMS.git/blob/303766d123111cafcfbb723946dad92229666e36:/typo3/sysext/fluid/Classes/ViewHelpers/Form/CheckboxViewHelper.php#l90" class="external">Source</a>)</p>
<p>A possible fix is to run <code>PersistenceManager->getIdentifierByObject</code> on each value within <code>property</code> too, thus comparing e.g. an UID with an array of UIDs. This is the same what <code>AbstractFormFieldViewHelper::getValue()</code> does when <code>$convertObjects</code> is set to <code>TRUE</code> (default).</p> TYPO3 Core - Feature #63561 (Closed): Add stdWrap strtotimehttp://forge.typo3.org/issues/635612014-12-04T12:14:25ZMathias Brodalambrodala@pagemachine.de
<p>To complement the existing <code>date</code> and <code>strftime</code> which allow converting timestamps to a formatted date the counterpart <code>strtotime</code> should be added to <code>stdWrap</code>. This allows for processing like this:</p>
<pre>
next_weekday = TEXT
next_weekday {
data = GP:selected_date
strtotime = + 2 weekdays
strftime = %Y-%m-%d
}
</pre>
<p>For <code>GP:selected_date</code> having a value <code>2014-12-04</code> this would output <code>2014-12-08</code>.</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 - 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>