TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-09-07T09:04:46ZTYPO3 Forge
Redmine TYPO3 Core - Bug #101868 (Resolved): #100719 breaks TYPO3 Console due to breaking change in Defau...http://forge.typo3.org/issues/1018682023-09-07T09:04:46ZHelmut Hummeltypo3@helhum.io
<p>Although, DefaultFactory is marked as internal API, I suggest to not break the API in a bugfix release.</p> TYPO3 Core - Bug #99465 (Closed): Accessing site configuration via TypoScript getData triggers a ...http://forge.typo3.org/issues/994652023-01-05T12:24:43ZHelmut Hummeltypo3@helhum.io
<p>The following stdWrap code currently triggers a log warning:</p>
<pre>
if.isTrue.data = site:settings.optional.property
</pre>
<p>My expectation is, that this "incident" should rather be logged at least as notice instead,<br />since the value accessed could intentionally be an optional value.</p> TYPO3 Core - Bug #98121 (Closed): <typo3-backend-icon> does not reflect icon size when size is se...http://forge.typo3.org/issues/981212022-08-10T22:50:54ZHelmut Hummeltypo3@helhum.io
<p>When using the custom element <typo3-backend-icon><br />with a JS framework, that renders the DOM (e.g. Vue <a class="external" href="https://github.com/vuejs/core/issues/3738">https://github.com/vuejs/core/issues/3738</a> <a class="external" href="https://github.com/vuejs/core/issues/3792">https://github.com/vuejs/core/issues/3792</a>),<br />it can happen, that they set the properties of the custom element<br />instead of an attribute.</p>
<p>Since Lit does not reflect these properties to attributes by default,<br />but the icon-element relies on CSS set on the host element that depends<br />on the size attribute, the icon is not rendered in the correct size.</p>
<p>See: <a class="external" href="https://web.dev/custom-elements-best-practices/">https://web.dev/custom-elements-best-practices/</a><br />on why reflecting properties to attributes might be a good idea<br />in some cases.</p>
<p>To reproduce put the following in a Fluid template of a backend module (TYPO3 12/ main):</p>
<pre>
<f:be.pageRenderer includeJavaScriptModules="{0: '@typo3/backend/element/icon-element.js'}"/>
<div id="app" style="font-size: 8px"></div>
<script>
let icon = document.createElement('typo3-backend-icon');
icon.identifier = 'actions-search';
icon.size = 'large';
document.getElementById('app').appendChild(icon);
</script>
</pre>
<p>Expected:</p>
<p>Large icon</p>
<p>Actual:</p>
<p>Very small icon</p>
<p>For TYPO3 11, the page renderer VH is different:</p>
<pre>
<f:be.pageRenderer includeRequireJsModules="{0: 'TYPO3/CMS/Backend/Element/IconElement'}"/>
</pre>
<p>The rest is the same</p> TYPO3 Core - Bug #92201 (Closed): \TYPO3\CMS\Core\Resource\ResourceFactory::getStorageObject is c...http://forge.typo3.org/issues/922012020-09-04T18:21:57ZHelmut Hummeltypo3@helhum.io
<p>Calling \TYPO3\CMS\Core\Resource\ResourceFactory::getStorageObject <br />eventually leads to a call to \TYPO3\CMS\Core\Resource\StorageRepository::findByUid<br />which in turn calls \TYPO3\CMS\Core\Resource\ResourceFactory::getStorageObject again</p>
<p>This was introduced with <a class="external" href="http://review.typo3.org/11011">http://review.typo3.org/11011</a>, where the plain DB call<br />was replaced with StorageRepository::findByUid</p> TYPO3 Core - Bug #91260 (Closed): \TYPO3\CMS\Core\Configuration\SiteConfiguration cannot be overr...http://forge.typo3.org/issues/912602020-05-01T19:54:23ZHelmut Hummeltypo3@helhum.io
<p>With <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Define singletons used in install tool in service providers (Closed)" href="http://forge.typo3.org/issues/89892">#89892</a> SiteConfiguration was configured in a ServiceProvider,<br />which makes it available in the failsafe and Symfony container.</p>
<p>However the object is created using, instead of using self::new<br />which would respect XCLASS definition</p> TYPO3 Core - Bug #91213 (Closed): \TYPO3\CMS\Install\Updates\RowUpdater\WorkspaceVersionRecordsMi...http://forge.typo3.org/issues/912132020-04-27T23:24:36ZHelmut Hummeltypo3@helhum.io
<p>\TYPO3\CMS\Install\Updates\RowUpdater\WorkspaceVersionRecordsMigration marks certain records as deleted,<br />which then fails in \TYPO3\CMS\Install\Updates\DatabaseRowsUpdateWizard update query, when the table does not have soft delete.</p> TYPO3 Core - Bug #87367 (Closed): \TYPO3\CMS\Core\Utility\GeneralUtility::flushDirectory fails if...http://forge.typo3.org/issues/873672019-01-08T15:27:07ZHelmut Hummeltypo3@helhum.io
<p>This affects cache flushing where this API method is used.</p>
<p>The reason this fails is, that it is tried to rename the directory (which in fact is a symlink) to allow atomic flushing of the directory.</p>
<p>Steps to reproduce:</p>
<ol>
<li>make va/cache a symlink to any folder</li>
<li>execute cache flush in install tool</li>
</ol> TYPO3 Core - Bug #84191 (Closed): $GLOBALS['TYPO3_CONF_VARS']['SYS']['sitename'] is not properly ...http://forge.typo3.org/issues/841912018-03-09T22:16:30ZHelmut Hummeltypo3@helhum.io
<p>The page module, when selecting the rootpage, show $GLOBALS['TYPO3_CONF_VARS']['SYS']['sitename'],<br />but fails to properly html encode the value.</p>
<p>Thanks to Pradeep Jairamani for reporting that privately to <a class="email" href="mailto:security@typo3.org">security@typo3.org</a></p>
<p>Although this can be considered as stored XSS vulnerability, we can follow our policy to handle this case in public,<br />because it is only exploitable by admins.</p> TYPO3 Core - Bug #70493 (Closed): Revert "[BUGFIX] Admin users should ignore user mounts"http://forge.typo3.org/issues/704932015-10-08T13:23:03ZHelmut Hummeltypo3@helhum.io
This was is incomplete:
<ul>
<li>TCA still contains mounts for admins</li>
<li>Group mounts are still respected</li>
</ul>
<p>Beides that, there are options in the user record to disable that behavior.</p>
<p>Besides that, it is the concept of mounts, that it is useful to see submounts of a global mount.</p> TYPO3 Core - Bug #69463 (Closed): Abstract XSD generator can handle more than two namespace partshttp://forge.typo3.org/issues/694632015-09-01T22:07:24ZHelmut Hummeltypo3@helhum.io
<p>The getTagNameForClass method in the abstract XSD generator class<br />could not handle class names with more than two namespace parts.</p>
<p>This caused e.g. TYPO3\CMS\Fluid\ViewHelpers\Be\Buttons\CshViewHelper to<br />not be transformed to "be.buttons.csh", but just "be.", which in turn<br />cause duplicate id errors in the resulting XSD document.</p> TYPO3 Core - Bug #67294 (Closed): "Ghost entry" remains in PackageStates.php file after extension...http://forge.typo3.org/issues/672942015-06-04T16:31:58ZHelmut Hummeltypo3@helhum.io
<p>After removing an extension in the Extension Manager UI, an entry in PackageStates.php still exists.</p> TYPO3 Core - Bug #42805 (Closed): [BUGFIX] Fix OTABLE content objecthttp://forge.typo3.org/issues/428052012-11-08T23:40:30ZHelmut Hummeltypo3@helhum.io
<p>During namespacing the OTABLE content object<br />which had of two classes has been messed up.</p>
<p>Combine both classes into one.</p> TYPO3 Core - Bug #41070 (Closed): absRefPrefix is not respected for some MEDIA element assetshttp://forge.typo3.org/issues/410702012-09-19T15:56:37ZHelmut Hummeltypo3@helhum.io
<p>The new MEDIA Element uses assets that are in the t3lib/js folder.<br />This folder however is not prefixed with the absRefPrefix, thus being unavailable, when config.absRefPrefix is used.</p> TYPO3 Core - Bug #40879 (Closed): [TASK] Cleanup Unit Testshttp://forge.typo3.org/issues/408792012-09-13T00:12:04ZHelmut Hummeltypo3@helhum.io
<ul>
<li>Skip the IPV6 Test that always fails on darwin/ OSX OS</li>
<li>Remove the potentially skipped tests concerning t3lib_diff since this class is still in use</li>
</ul> TYPO3 Core - Bug #18964 (Closed): "Toggle selection" and "Import selection" in element browser do...http://forge.typo3.org/issues/189642008-06-15T15:46:34ZHelmut Hummeltypo3@helhum.io
<p>The mentioned options do not work in FF3 because the Element.getElementsByClassName function throws an error. This is a known issue concerning prototype and FF3; see: <br /><a class="external" href="http://ejohn.org/blog/getelementsbyclassname-pre-prototype-16/">http://ejohn.org/blog/getelementsbyclassname-pre-prototype-16/</a></p>
<p>Solution:<br />replace Element.getElementsByClassName call with Elment.select as proposed in the document above.<br />(issue imported from #M8720)</p>