TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-10-27T12:31:20ZTYPO3 Forge
Redmine TYPO3 Core - Bug #102272 (New): custom doktype icons not visible in page treehttp://forge.typo3.org/issues/1022722023-10-27T12:31:20ZMaik Hagenbruchmaikhagenbruch@gmail.com
<p>I tried to add new page types. For this i used this documentation.<br /><a class="external" href="https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/PageTypes/CreateNewPageType.html">https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/PageTypes/CreateNewPageType.html</a></p>
<p>I registered own icons and used them. <br />in the page tree toolbar on top i can see the new icons.<br />but in the page tree itself, beside the paget title, there is no icon (not a 'broken icon' too)</p>
<p>after that i tried it without my own icons. Instead i used typo3 known icons - that worked perfect.</p>
<p>after that i took the svg content from the registered icon and pasted it in a new file and use this file for my new icon.<br />This resulst in the same behaviour as described above.</p> TYPO3 Core - Bug #99769 (New): Output of fluid paths in admin panel debug viewhttp://forge.typo3.org/issues/997692023-01-31T12:03:06ZMaik Hagenbruchmaikhagenbruch@gmail.com
<p>If i use the admin panel to show the fluid template path in the debug view to much from the path is stripped.</p>
<p>the function stripPathSitePrefix of TYPO3\CMS\Core\Utility\PathUtility gets the path as<br />'EXT:ext_name/Resources/Private/Page/Portal/Partials/Navigation/MetaLanguage/Switch.html'<br />and strips the length of Environment::getPublicPath() which is '/var/www/html/public'.<br />This results in a string like 'es/Private/Page/Portal/Partials/Navigation/MetaLanguageSwitch.html'</p>
<p>i think it would be better to return the full path starting with 'EXT:...' or without 'EXT:' but in every case the full path.</p> TYPO3 Core - Bug #97835 (New): Allow invalid Fluid tags inside f:commenthttp://forge.typo3.org/issues/978352022-06-30T09:20:02ZMaik Hagenbruchmaikhagenbruch@gmail.com
<p>Currently i update all <f:widget.paginate></p>
<p>if i wrap this widget with f:comment the f:widget.paginate still throws an error.<br />I now i have to remove this widget, but for testing i want wrap this in a comment to write the new code.</p>
<p>i think fluid should ignore code which is wrapped with comments</p> TYPO3 Core - Feature #97753 (New): Backend module upgrade taskhttp://forge.typo3.org/issues/977532022-06-09T08:56:34ZMaik Hagenbruchmaikhagenbruch@gmail.com
<p>In the upgrade backend module there is the part "scan extension files".<br />This should help to identify deprecated or removed dependencies.</p>
<p>In some cases, there are issues found which are not needed to fix.</p>
<p>2 Examples:</p>
<p>1.<br />$cObj = $configurationManager->getContentObject();<br />"Deprecation: <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Wording: Rename AbstractContentObject->getContentObject() to getContentObjectRenderer() (Closed)" href="http://forge.typo3.org/issues/68748">#68748</a> - Deprecate AbstractContentObject::getContentObject()"</p>
<p>But, my usage of this method is from another class as the deprecated one.</p>
<p>2. return $this->synonyms;<br />"Deprecation: <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Deprecate various functionality in CharsetConverter (Closed)" href="http://forge.typo3.org/issues/85122">#85122</a> - Functionality in CharsetConverter" <br />But, this line of code is from a ModelClass which returns a property.</p>
<p>I think the scanner doesn't look closely enough. This is ok, but, it was very usefull if i can mark those issues as "no change needed" or something like that. So it would be easier to go through all of them and decide by myself if a code change is needed or not.</p> TYPO3 Core - Task #83999 (Closed): Little Thing on using flexforms displayCondhttp://forge.typo3.org/issues/839992018-02-21T13:45:34ZMaik Hagenbruchmaikhagenbruch@gmail.com
<p>Its just a little thing which bothers me a bit. Maybe i dont understand this behaviour correctly. I will explain.<br />If i use displayConds and onChange="reload" on backend fields there is an popup which asks me</p>
<p>"Diese Änderung wird die im Formular verfügbaren Felder beeinflussen. Möchten Sie jetzt speichern, um die Anzeige zu aktualisieren?"</p>
<p>In this Case i can sys "ok" and the form reloads or i can say "cancel" and ther form does not reload, but the choosen value which triggered this popup is changed.</p>
<p>In my oppinion the fields value should be set back to the last choosen to show the correct fields.<br />Maybe its even better to remove the "cancel" option in the popup because you HAVE TO reload the form to see<br />the changed fields. Maybe this "popup" can completely removed in this case.</p> TYPO3 Core - Task #83997 (New): Little Thing on using flexforms displayCondhttp://forge.typo3.org/issues/839972018-02-21T12:15:46ZMaik Hagenbruchmaikhagenbruch@gmail.com
<p>Its just a little thing which bothers me a bit. Maybe i dont understand this behaviour correctly. I will explain.<br />If i use displayConds and onChange="reload" on backend fields there is an popup which asks me</p>
<p>"Diese Änderung wird die im Formular verfügbaren Felder beeinflussen. Möchten Sie jetzt speichern, um die Anzeige zu aktualisieren?"</p>
<p>In this Case i can sys "ok" and the form reloads or i can say "cancel" and ther form does not reload, but the choosen value which triggered this popup is changed.</p>
<p>In my oppinion the fields value should be set back to the last choosen to show the correct fields.<br />Maybe its even better to remove the "cancel" option in the popup because you HAVE TO reload the form to see<br />the changed fields. Maybe this "popup" can completely removed in this case.</p> TYPO3 Core - Bug #83996 (Closed): Little Thing on using flexforms displayCondhttp://forge.typo3.org/issues/839962018-02-21T12:15:02ZMaik Hagenbruchmaikhagenbruch@gmail.com
<p>Its just a little thing which bothers me a bit. Maybe i dont understand this behaviour correctly. I will explain.<br />If i use displayConds and onChange="reload" on backend fields there is an popup which asks me</p>
<p>"Diese Änderung wird die im Formular verfügbaren Felder beeinflussen. Möchten Sie jetzt speichern, um die Anzeige zu aktualisieren?"</p>
<p>In this Case i can sys "ok" and the form reloads or i can say "cancel" and ther form does not reload, but the choosen value which triggered this popup is changed.</p>
<p>In my oppinion the fields value should be set back to the last choosen to show the correct fields.<br />Maybe its even better to remove the "cancel" option in the popup because you HAVE TO reload the form to see<br />the changed fields. Maybe this "popup" can completely removed in this case.</p> TYPO3 Core - Bug #83995 (Closed): Little Thing on using flexforms displayCondhttp://forge.typo3.org/issues/839952018-02-21T12:10:44ZMaik Hagenbruchmaikhagenbruch@gmail.com
<p>Its just a little thing which bothers me a bit. Maybe i dont understand this behaviour correctly. I will explain.<br />If i use displayConds and onChange="reload" on backend fields there is an popup which asks me</p>
<p>"Diese Änderung wird die im Formular verfügbaren Felder beeinflussen. Möchten Sie jetzt speichern, um die Anzeige zu aktualisieren?"</p>
<p>In this Case i can sys "ok" and the form reloads or i can say "cancel" and ther form does not reload, but the choosen value which triggered this popup is changed.</p>
<p>In my oppinion the fields value should be set back to the last choosen to show the correct fields.<br />Maybe its even better to remove the "cancel" option in the popup because you HAVE TO reload the form to see<br />the changed fields. Maybe this "popup" can completely removed in this case.</p> TYPO3 Core - Bug #83021 (Closed): EXT:form override settingshttp://forge.typo3.org/issues/830212017-11-17T09:07:02ZMaik Hagenbruchmaikhagenbruch@gmail.com
<p>Szenario:<br />- Create form in backend<br />- improve settings in yaml config file<br />- include form on page in backend and use the option "Override finisher settings"</p>
<p>For example, i set the subject for MailToAdmin in my yaml file but need other email-addresses on each system.<br />Now i get an error on sending this mail, because i did not set the subject in override settings.</p>
<p>I think there should be a test for this. If i set an override so take this value, but if not, so take this value from yaml config.</p> TYPO3 Core - Bug #82569 (Closed): EXT:form setting attachUploads to false does not workhttp://forge.typo3.org/issues/825692017-09-27T16:33:29ZMaik Hagenbruchmaikhagenbruch@gmail.com
<p>I dont know if its an bug or not, but this is not working for me. Maybe i did it wrong.</p>
<p>I configured my a MailToReceiverFinisher and set<br />attachUploads to false ( tried with [0, false, 'false'];<br />After sending this form the mail contains the uploaded file every time.</p>
<p>So i debugged in \TYPO3\CMS\Form\Domain\Finishers\EmailFinisher line 98.</p>
<p>$attachUploads = $this->parseOption('attachUploads');</p>
<p>This is always set to true. If i say<br />$attachUploads = false; manualy directly after this call, the attachments are NOT included in the mail.</p>
<p>My Config: <a class="external" href="https://pastebin.com/EXKaKVk2">https://pastebin.com/EXKaKVk2</a></p>
<p>This is what is saved after saving the form in backend module.</p> TYPO3 Core - Feature #81462 (Closed): remove equalheight js from about module and use flexbox ins...http://forge.typo3.org/issues/814622017-06-03T17:29:14ZMaik Hagenbruchmaikhagenbruch@gmail.comTYPO3 Core - Bug #67860 (Closed): TYPO3 7.3.0 - Image manipulation failshttp://forge.typo3.org/issues/678602015-06-30T16:04:36ZMaik Hagenbruchmaikhagenbruch@gmail.com
<p>If i add a new image in TYPO3 7.3.0 with content element "Images only" and try to open the image editor i get a js error like this:<br />TypeError: undefined is not a function (evaluating 'top.TYPO3.Modal.loadUrl') on ImageManipulation.js line 56</p>
<p>Firefox and Chrome works fine.<br />Bug detected in Safar iVersion 8.0 (10600.1.25.1)</p> TYPO3 Core - Bug #67859 (Closed): TYPO3 7.3.0 - Image manipulation failshttp://forge.typo3.org/issues/678592015-06-30T16:03:20ZMaik Hagenbruchmaikhagenbruch@gmail.com
<p>If i add a new image in TYPO3 7.3.0 with content element "Images only" and try to open the image editor i get a js error like this:<br />TypeError: undefined is not a function (evaluating 'top.TYPO3.Modal.loadUrl') on ImageManipulation.js line 56</p> TYPO3 Core - Bug #62735 (Closed): Error on using suggest wizard in firefoxhttp://forge.typo3.org/issues/627352014-11-06T10:14:08ZMaik Hagenbruchmaikhagenbruch@gmail.com
<p>Im using suggest wizards in a project. All is fine in Chrome and in Safari.<br />Only in Firefox (33.0.2) the suggest wizard fails.</p>
<p>On the right side i choose an element an if i click on it, it should appear in the box of the left side.<br />In Chrome in Safari this works without any trouble but in Firefox i get some errors. So i cant use firefox.</p>
<p>"Error: Load timeout for modules: TYPO3/CMS/Backend/FormEngine<br /><a class="external" href="http://requirejs.org/docs/errors.html#timeout">http://requirejs.org/docs/errors.html#timeout</a> require.js:166<br />TypeError: setFormValueFromBrowseWin is not a function"</p>
<p>I tried the TCA config like the minimal and like this on the ref pages.<br />I used this doku: <a class="external" href="http://docs.typo3.org/typo3cms/TCAReference/AdditionalFeatures/WizardsConfiguration/Index.html">http://docs.typo3.org/typo3cms/TCAReference/AdditionalFeatures/WizardsConfiguration/Index.html</a></p>
<p>I think its a bug and it would be great to get some info about this problem.</p> TYPO3 Core - Bug #54449 (Closed): Fatal error in configuration module while modifying TYPO3_LOADE...http://forge.typo3.org/issues/544492013-12-16T13:21:40ZMaik Hagenbruchmaikhagenbruch@gmail.com
<p>When choosing $TYPO3_LOADED_EXT (Loaded Extensions) in configuration module a fatal error occurs:</p>
<p>#1361915596: The array $GLOBALS['TYPO3_LOADED_EXT'] may not be modified</p>
<p>This happens because the tree method tries to override values in the non-writeable TYPO3_LOADED_EXT array.</p>
<p><strong>\TYPO3\CMS\Lowlevel\View\ConfigurationView : 236</strong><br /><pre>
$tree = $arrayBrowser->tree($theVar, '', '');
</pre></p>
<p><strong>\TYPO3\CMS\Lowlevel\Utility\ArrayBrowser : 111</strong><br /><pre>
if (is_object($arr[$key])) {
$arr[$key] = (array) $arr[$key];
}
</pre></p>