TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-12-05T13:15:14ZTYPO3 Forge
Redmine TYPO3 Core - Bug #102606 (Under Review): Update Guzzle timeout to 20 secondshttp://forge.typo3.org/issues/1026062023-12-05T13:15:14ZStefan Froemkenfroemken@gmail.com
<p>Hello,</p>
<p>I have a scheduler task which requests an API every 15 minutes. As I use TYPO3 RequestFactory the integrated Guzzle client will get its config from TYPO3_CONF_VARS/HTTP. As default in Guzzle options <a class="external" href="https://docs.guzzlephp.org/en/stable/request-options.html#timeout">https://docs.guzzlephp.org/en/stable/request-options.html#timeout</a> the property "timeout" is set to 0. The same value is default in TYPO3 as configured in DefaultConfiguration.php.</p>
<p>As TYPO3 is PHP based and works in a web environment we have to respect PHP:max_execution_time which is somewhere between 30 and 240 seconds. With "timeout" 0 (infinite) an outgint request which exceeds max_execution_time will stop the TYPO3 request immediatly. In case of a scheduler task you will see that task is still running which is not the case. The problem is: In that state the task will not be executed again until an integrator reset the task.</p>
<p>For me a default of 0 is a very bad idea.<br />I prefer setting that value to 20 seconds. If that value has been reached Guzzle will throw an exception which can be catched and the scheduler task can be resetted to a clean state.</p>
<p>Stefan</p> TYPO3 Core - Feature #101124 (Needs Feedback): Make Templates optional in Extbasehttp://forge.typo3.org/issues/1011242023-06-20T08:46:52ZAristeidis Karavas
<p>Since ResponseInterface has been introduced, one can define a return type, <strong>JsonResponse</strong> , <strong>HtmlResponse</strong> etc.</p>
<p>The problem here is that using for example <strong>JsonResponse</strong> with <strong>Extbase</strong> and not defining a template for it, TYPO3 throws an exception. Now, we have to add a template and format it to a json structure which could be PITA, specially when the JSON is huge. One could use <strong>Middlewares</strong> , but with TYPO3 12, one can not use Extbase features if not in Extbase context. So now we are in a dead end.</p>
<p><strong>Solution</strong><br />Make the template requirement optional, or add a method which deactivates it for the action, like</p>
<pre>
$this->view->withTemplate(false);
</pre> TYPO3 Core - Feature #101005 (Under Review): Add DefaultLanguageRestrictionhttp://forge.typo3.org/issues/1010052023-06-12T19:17:26ZStefan Froemkenfroemken@gmail.com
<p>Hello,</p>
<p>if you're working with TYPO3 QueryBuilder, there are a lot of restrictions added to current query like DeletedRestriction, HiddenRestriction, StarttimeRestriction and some more. Would be cool to have a restriction which automatically adds a WHERE clause for default language to a query. Nearly everywhere in the TYPO3 core and also in extensions you need the records in default language to parse the resulting data through all these versionOL and translation methods of TYPO3 API.</p>
<p>Stefan</p> TYPO3 Core - Feature #99995 (Under Review): Add hideTranslation to RecordLinkHandler configurationhttp://forge.typo3.org/issues/999952023-02-20T13:50:42ZStefan Froemkenfroemken@gmail.com
<p>Hello,</p>
<p>links to translated records like "news" in RTE fields of translated records (f.e. Content Element) are not working.</p>
<p>To prevent that problem a new option should be added to LinkHandler configuration. Maybe "hideTranslation" as known of the ElementBrowserRecordList.</p>
<p>In nearly every Extbase Extension and maybe all other plugin based Extensions an editor has to link to the record in default language.</p>
<p>Stefan</p> TYPO3 Core - Feature #99459 (Under Review): Respect record types in NewRecordControllerhttp://forge.typo3.org/issues/994592023-01-04T18:25:16ZStefan Froemkenfroemken@gmail.com
<p>Hi,</p>
<p>extensions like news or maps2 contains various record types of their database tables. While creating new records over the NewRecordController just the default record type will be processed.</p>
<p>Would be cool to add an EventListener for the extension developers to extend the list of record links or implement a solution to respect all the record types of a table</p>
<p>Stefan</p> TYPO3 Core - Bug #96671 (Under Review): PageTSConfig override for group fields do not workhttp://forge.typo3.org/issues/966712022-01-28T23:12:00ZStefan Froemkenfroemken@gmail.com
<p>Hello Core-Team,</p>
<p>I just see the new Feature in TYPO3 12:</p>
<p><a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Define default page for Record selector / ElementBrowser (Closed)" href="http://forge.typo3.org/issues/91077">#91077</a> - Element browser entry points for TCA type "group"</p>
<p>It works for fields defined directly in TCA, but not for fields in type "flex". Tested with felogin:</p>
<pre>
TCEFORM.tt_content.pi_flexform.felogin_login.sDEF.settings\.pages.config.elementBrowserEntryPoints.tt_content = 3
TCEFORM.tt_content.pi_flexform.felogin_login.sDEF.settings\.pages.config.size = 1
#TCEFORM.tt_content.pi_flexform.felogin_login.sDEF.settings\.pages.disabled = 1
</pre>
<p>I have added the "disabled" line to test, if the path works in general. Jep, the field will is disabled...so the path is correct ;-)</p>
<p>As you will see, either the "size", "max_size" neither the "elementBrowserEntryPoints" will be accepted.</p>
<p>Stefan</p>