TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-06-29T15:23:08ZTYPO3 Forge
Redmine TYPO3 Core - Bug #101202 (Resolved): CKEditorInspector is not working anymore in TYPO3 v12.4.2http://forge.typo3.org/issues/1012022023-06-29T15:23:08ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>Before updating TYPO3 I always got the inspector shown, with TYPO3 v12.4.2 this option is gone, instead I get an error shown:</p>
<p><img src="http://forge.typo3.org/attachments/download/37784/clipboard-202306292220-sy4sf.png" alt="" loading="lazy" /></p>
<p>the link on the right side of the screenshot leads to this codeblock in ckeditor5.js:</p>
<pre>
this.options.debug && window.CKEditorInspector.attach(t, {
isCollapsed: !0
})
</pre> TYPO3 Core - Bug #100970 (Needs Feedback): in USER / USER_INT the calling CE isn't exposedhttp://forge.typo3.org/issues/1009702023-06-07T09:26:31ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>While writing a USER / USER_INT class it seems impossible to know which element was called to trigger the execution.<br />So all elements have to be crawled and likely the register of TSFE be filled with elements that have been processed, but there isn't any way to get a reliable hint about the calling element.</p> TYPO3 Core - Bug #100857 (Resolved): missing check for array keys in ContentObjectRendererhttp://forge.typo3.org/issues/1008572023-05-11T05:54:07ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>The array keys $conf['max'] and $conf['begin'] are not properly checked and throw an error if only one of the TypoScript keys is used.<br />Details in the attached patch file.</p> TYPO3 Core - Bug #100849 (Needs Feedback): ContentContentObject::render has wrong conditionhttp://forge.typo3.org/issues/1008492023-05-10T03:50:10ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>The method <pre>TYPO3\CMS\Frontend\ContentObject::render()</pre> has the condition <pre>if (!($frontendController->recordRegister[$registerField] ?? false)) {</pre>.<br />The code inside the condition therefore is executed if the register never has an entry yet with the key $registerField.<br />In some special cases though, this register is already existing, but without content, so the rendered output stays empty.<br />In my opinion the check is wrong here, rather should just be checked if the required variable $registerField exists with a value:<br /><pre>if ($registerField) {</pre></p>
<p>So, what are the special cases where this existing condition fails?<br />Creating a simple plugin with own CType, and adding it as [typoscript]: CONTENT element with required render instructions.</p>
<pre>
plugin.tx_mysitepackage_hero = CONTENT
plugin.tx_mysitepackage_hero {
table = tt_content
select {
where = AND {#CType}="tx_mysitepackage_hero"
orderBy = sorting desc
}
renderObj = COA
renderObj {
20 = TEXT
20.stdWrap.field = header
20.stdWrap.noTrimWrap = |<h1>THIS IS MY RENDERED CONTENT HEADER: |</h1>|
}
}
</pre><br />This element is not rendered but I'd expect it to. TYPO3 Core - Bug #100766 (New): install tool is derailed by old extensions using defined('TYPO3_M...http://forge.typo3.org/issues/1007662023-04-26T15:45:25ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>While it's know that TYPO3_MODE isn't used anymore in v12, it's quite common that updating extensions might be still required.<br />Old extensions have checks included like this:</p>
<p>defined('TYPO3_MODE') || die();</p>
<p>This is stopping TYPO3 v12 completely and never shows any hint what could be wrong. The install tool shouldn't be derailed by the missing of this constant, but scanning for it and reporting the need for removal or replacement.<br />Currently TYPO3 v12 is completely unusable if an extension is still having this check included.</p>
<p>Therefore I plead to include a definition for it at least in the install tool, so that an upgrade wizard could inform about required changes.</p> TYPO3 Core - Bug #100538 (Resolved): Return value of TYPO3\CMS\Adminpanel\Service\ConfigurationSe...http://forge.typo3.org/issues/1005382023-04-10T06:40:08ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>Running Acceptance Tests with installed adminpanel breaks with the error</p>
<blockquote>
<p>Return value of TYPO3\CMS\Adminpanel\Service\ConfigurationService::getBackendUser() must be an instance of TYPO3\CMS\Core\Authentication\BackendUserAuthentication, null returned</p>
</blockquote> TYPO3 Core - Bug #97833 (New): TCA: Buttons for inline->appearance->usecombination behave wronghttp://forge.typo3.org/issues/978332022-06-30T00:41:17ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>The example tx_styleguide_inline_usecombination has two buttons:</p>
<p>Button 1 shall create a <strong>new</strong> record, of the child table.<br />Button 2 (beside the select field) shall create a relation to an <strong>existing</strong> record of the child table.</p>
<p>The behavior is this:</p>
<p>Button 1 is creating new records only if there are no records to create a relation. Else a relation is created and the label on the button turns out to be misleading.<br />Button 2 (beside the select field) is creating a relation to an existing record and if no records are available anymore (all existing ones have already a relation) a new record is created.</p>
<p>Both buttons work similar and depend on the situation if a child record to create a relation is available. <br />If there exist child records without relation a relation is created, else a new record. <br />So the behavior of the buttons never depends at all on their intended purpose but on the potential child records.</p>
<p>Comment:<br />I've an extension that is using the feature with the two buttons and I'd need a core-fix that the extension is running well.</p>
<p>The issue is described also here:<br /><a class="external" href="https://github.com/TYPO3/styleguide/issues/331">https://github.com/TYPO3/styleguide/issues/331</a></p> TYPO3 Core - Bug #97317 (New): Duplicates when pages are copiedhttp://forge.typo3.org/issues/973172022-04-06T10:38:43ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>Creating a copy with the clipboard tends to create undesired additional copies.<br />One reason I remarked is when the site is reloaded, that might be the case even without user-action by the browser.<br />Further things like large page-trees could be possible reasons too.</p>
<p>I never verified how the task to create the copies are temporally saved, at least it's not sufficient.<br />The copies have to be filtered / deleted manually to remove undesired ones.</p>
<p><img src="http://forge.typo3.org/attachments/download/36829/clipboard-202204061734-08jvw.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #94470 (New): Site Error Pageshttp://forge.typo3.org/issues/944702021-07-02T10:54:12ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>I work with an installation where 64 Domains are hosted.</p>
<p>The defined Error-Pages are shown for the first 49 Domains and for further Domains not anymore.<br />For the domains 50+ the general error-page is shown "Oops an error occured".</p> TYPO3 Core - Bug #93328 (New): redirect for empty slughttp://forge.typo3.org/issues/933282021-01-20T13:40:34ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>Adding a slug to a page with before empty slug creates a redirect for the root-page and breaks so the whole site.<br />Considering <a class="issue tracker-1 status-1 priority-4 priority-default" title="Bug: Popups for Redirect (New)" href="http://forge.typo3.org/issues/93327">#93327</a> I would at least get a warning about it but adding a redirect for the root-page without further automatic checks is devastating.<br />I propose a check for pages without slug and also if the current page had a slug before as requirement to create a redirect for those pages - including reasonable decisions based on the findings. Nevertheless, the final decision has to be shown for confirmation like described in <a class="issue tracker-1 status-1 priority-4 priority-default" title="Bug: Popups for Redirect (New)" href="http://forge.typo3.org/issues/93327">#93327</a> as the proposed tests would be quite limited without further context.</p> TYPO3 Core - Bug #93327 (New): Popups for Redirecthttp://forge.typo3.org/issues/933272021-01-20T13:27:10ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>The popup for redirects is too general and never allows to verify created redirects on the fly.<br />Instead I prefer having the old URL respectively slug shown and the new one.<br />Then it's much easier to decide about it and the list of redirects never has to be crawled till the correct one is found.<br />As the list of redirects can get quite long this visual feature would be very useful - especially in cases where the automatically created redirect would break something.<br />Also the display top right without any blocking-mechanism is too trivial considering that changes might break a whole site.</p> TYPO3 Core - Bug #92699 (New): variables in ContentObjectRenderer::checkIfhttp://forge.typo3.org/issues/926992020-10-24T12:14:29ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>Some variable are not checked properly before usage:</p>
<p>For many variables is checked this:<br /><pre>
if (isset($conf['a']) || isset($conf['a.'])) {
</pre><br />but used are both.<br />Concrete example:<br /><pre>
if (isset($conf['isTrue']) || isset($conf['isTrue.'])) {
$isTrue = isset($conf['isTrue.']) ? trim($this->stdWrap($conf['isTrue'], $conf['isTrue.'])) : trim($conf['isTrue']);
if (!$isTrue) {
$flag = false;
}
}
</pre><br />This example is throwing an error if $conf['isTrue.'] is set but $conf['isTrue'] not.</p> TYPO3 Core - Feature #87091 (New): Localize Installtoolhttp://forge.typo3.org/issues/870912018-12-06T09:58:19ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>Currently the installtool is only in English available.<br />Even not required by me I think it would be desirable having the whole system available with translations.<br />This adds an extended translation-layer to the backend and I think it would perhaps convince more people using TYPO3.</p> TYPO3 Core - Bug #85483 (New): Installing distribution with included extension is raising cache-e...http://forge.typo3.org/issues/854832018-07-05T08:45:57ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>Installing a distribution with included extension where a cache is defined, this cache is not initialized and therefore an error is thrown:<br /><pre>
Oops, an error occurred!
A cache with identifier "cache_news_category" does not exist.
More information regarding this error might be available online.
</pre><br />Related data aren't imported from data.t3d</p> TYPO3 Core - Bug #85377 (New): Wrong sorting in list module by fields which are relations http://forge.typo3.org/issues/853772018-06-25T09:26:58ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>The sorting of e.g. categories in BE is not working, see attached screenshot.<br />It might be obvious about the reasons, nevertheless the editor can't use it reliable.</p>
<p>Version 9.3</p>