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 #100767 (Closed): typo3-console setup fails with EXT:workspaceshttp://forge.typo3.org/issues/1007672023-04-26T15:53:13ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>EXT:workspaces seems to be responsible for setup-error, so the cli-setup with "typo install:setup" fails.<br />It's difficult to find the reason for it, so the cause isn't know yet.</p> 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 #100301 (Closed): Undefined array key for form fields of type checkboxhttp://forge.typo3.org/issues/1003012023-03-25T14:50:21ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>Defining a form like this<br /><pre>
type: Form
prototypeName: standard
identifier: variant-Test
label: Newsletter Subscription
renderables:
-
type: Page
identifier: page-1
label: General data
renderables:
-
type: Text
identifier: email-address
label: Email address
defaultValue:
variants:
-
identifier: validation-1
condition: 'formValues["checkbox-1"] == 1'
properties:
fluidAdditionalAttributes:
required: required
validators:
-
identifier: NotEmpty
-
identifier: EmailAddress
-
type: Checkbox
identifier: checkbox-1
label: Check this and email will be mandatory
</pre><br />throws an error when the checkbox is not checked:<br /><pre>
PHP Warning: Undefined array key "checkbox-1" in /var/www/html/vendor/symfony/expression-language/Node/GetAttrNode.php line 97
</pre></p>
<p>Select fields with empty value option behave probably similar.<br />I'm not sure if all cases would be covered then.</p> TYPO3 Core - Bug #98323 (Rejected): auto creation of table isn't done if options never fit exact ...http://forge.typo3.org/issues/983232022-09-10T11:19:15ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>Having a configuration like this:<br /><pre>
'related_posts' => [
'exclude' => true,
'label' => 'LLL:EXT:blog_example/Resources/Private/Language/locallang_db.xlf:tx_blogexample_domain_model_post.related',
'config' => [
'type' => 'select',
'renderType' => 'selectMultipleSideBySide',
'size' => 10,
'autoSizeMax' => 30,
'multiple' => 0,
'foreign_table' => 'tx_blogexample_domain_model_post',
'foreign_table_where' => 'AND ###THIS_UID### != tx_blogexample_domain_model_post.uid',
'MM' => 'tx_blogexample_post_post_mm',
'MM_opposite_field' => 'related_posts',
],
],
</pre><br />the table isn't created.<br />The culprit here is the option 'MM_opposite_field', removing it, it works like expected.</p> TYPO3 Core - Bug #98322 (Rejected): IRRE fields have limited TCA-options concerning mm-tableshttp://forge.typo3.org/issues/983222022-09-10T10:25:47ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>This code (of EXT:blog_example, table tx_blogexample_domain_model_person) should autocreate an mm-table with the field `fieldname` but it doesn't. The table is created but without that field.</p>
<pre>
'tags' => [
'label' => 'LLL:EXT:blog_example/Resources/Private/Language/locallang_db.xlf:tx_blogexample_domain_model_person.tags',
'config' => [
'type' => 'inline',
'foreign_table' => 'tx_blogexample_domain_model_tag', // needed by Extbase
'MM' => 'tx_blogexample_domain_model_tag_mm',
'MM_match_fields' => [
'fieldname' => 'tags',
],
'appearance' => [
'useCombination' => 1,
'useSortable' => 1,
'collapseAll' => 1,
'expandSingle' => 1,
],
],
],
'tags_special' => [
'exclude' => true,
'label' => 'LLL:EXT:blog_example/Resources/Private/Language/locallang_db.xlf:tx_blogexample_domain_model_person.tags_special',
'config' => [
'type' => 'inline',
'foreign_table' => 'tx_blogexample_domain_model_tag', // needed by Extbase
'MM' => 'tx_blogexample_domain_model_tag_mm',
'MM_match_fields' => [
'fieldname' => 'tags_special',
],
'appearance' => [
'useCombination' => 1,
'useSortable' => 1,
'collapseAll' => 1,
'expandSingle' => 1,
],
],
],
</pre> TYPO3 Core - Bug #98173 (Rejected): `storeSession=false` in v10 f:widget.autocomplete provokes er...http://forge.typo3.org/issues/981732022-08-19T05:36:40ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>The problem is that I am getting the following error message when typing anything in my search field:</p>
<p><a class="external" href="http://www.local-website.com/?id=2&type=7076&action=autocomplete&term=teststring">http://www.local-website.com/?id=2&type=7076&action=autocomplete&term=teststring</a> - 500 (Internal Server Error).. After examining the exact response of that page request, here's the specific error:</p>
<p>"No widget context was found for the Ajax Widget Identifier "". This only happens if AJAX URIs are called without including the widget on a page"</p>
<p>This happens if the new parameter storeSession="false" is used. In TYPO3 v9 this parameter didn't exist.<br />Using the widget like this should work like intended:</p>
<pre>
<f:widget.autocomplete for="search-items" objects="{allItems}" searchProperty="title"/>
</pre><br />Usually the parameteres look like this:
<pre>
?id=1&type=7076&fluid-widget-id=9c31f0bb1b5f5f953e84f6b57af102b4&action=autocomplete&term=Ma
</pre><br />When the parameter storeSession=false is used it looks like this:
<pre>
?id=1&type=7076&action=autocomplete&term=Ma
</pre><br />That means that the widget doesn't transfer the correct link to the AJAX script.
<p>See <a class="external" href="https://stackoverflow.com/questions/67021493/how-to-get-the-fluid-autocomplete-widget-to-work-in-typo3-v10/73412070">https://stackoverflow.com/questions/67021493/how-to-get-the-fluid-autocomplete-widget-to-work-in-typo3-v10/73412070</a></p> 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 - Feature #87092 (Closed): Localize the essential parts of messages (feedback / error)http://forge.typo3.org/issues/870922018-12-06T10:01:51ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>Currently many messages (feedback / error) are 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 system and I think it would perhaps convince more people using TYPO3.</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 #87084 (Closed): Typo in InstallTool -> check for broken Extensionshttp://forge.typo3.org/issues/870842018-12-05T09:13:14ZDavid Bruchmanndavid.bruchmann@gmail.com
<p>There is a hint shown (not always):<br /><pre>
... it may also help to manually increase debugging output in typo3conf/LocalConfiguration.php:['BE']['debug'] => true, ['SYS']['devIPmask'] => '*', ['SYS']['displayErrors'] => 1,['SYS]['systemLogLevel'] => 0, ['SYS']['exceptionalErrors'] => 12290</pre></p>
<p>There is one single quote missing in <pre>['SYS]['systemLogLevel']</pre></p>