TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692022-12-06T13:56:27ZTYPO3 Forge
Redmine TYPO3 Core - Bug #99289 (Closed): Can no longer create scheduler task due to "The end date is bef...http://forge.typo3.org/issues/992892022-12-06T13:56:27ZDaniel Siepmanncoding@daniel-siepmann.de
<p>It was possible to create scheduler tasks via backend module without an end date.<br />This doesn't seem to be possible in 12.1.0 any longer.<br />Submitting the form with default dates (current start and empty end) will result in an error "The end date is before the start date." and an filles end date which is equal start date.</p> TYPO3 Core - Feature #98394 (Closed): Allow Extension to prevent downloading of language packshttp://forge.typo3.org/issues/983942022-09-21T12:15:05ZDaniel Siepmanncoding@daniel-siepmann.de
<p>TYPO3 will try to fetch language packs for all installed extensions in all available languages.<br />This exposes locally installed extensions to the outer world (the language server).<br />Furthermore, there might be an extension in the wild with same name, leading to unexpected downloading foreign language packs. Otherwise unnecessary 404 to TYPO3 translation server will happen.</p>
<p>It would be cool if extensions could be defined to ignore the procedure. E.g. via</p>
<pre>
{
"extra": {
"typo3/cms": {
"updateLanguages": false
}
}
}
</pre>
<p>Furthermore: There is no way to do that via composer only right now. But there was a way via ext_emconf.php, see: <a class="external" href="https://github.com/TYPO3/typo3/blob/9d5ff89a9e9f086eca3a1d594797e50a24623ed5/typo3/sysext/install/Classes/Service/LanguagePackService.php#L170">https://github.com/TYPO3/typo3/blob/9d5ff89a9e9f086eca3a1d594797e50a24623ed5/typo3/sysext/install/Classes/Service/LanguagePackService.php#L170</a></p> TYPO3 Core - Bug #95078 (Closed): TypeError in MoveElementController when using sqlitehttp://forge.typo3.org/issues/950782021-09-02T11:57:56ZDaniel Siepmanncoding@daniel-siepmann.de
Steps to reproduce:
<ol>
<li>Use SQLite</li>
<li>Go to List Module</li>
<li>Click on "…" Button to open further actions</li>
<li>Click on "Display change history / Un-do"</li>
</ol>
<p>An PHP TypeError is thrown:<br /><pre>
(1/1) TypeError
Typed property TYPO3\CMS\Backend\Controller\ContentElement\MoveElementController::$page_id must be int, string used
typo3/sysext/backend/Classes/Controller/ContentElement/MoveElementController.php line 114
$assigns['makeCopyChecked'] = (bool)$this->makeCopy;
$assigns['makeCopyUrl'] = GeneralUtility::linkThisScript(['makeCopy' => !$this->makeCopy]);
// Get page record (if accessible):
if ($this->table !== 'pages' && $this->moveUid === $this->page_id) {
$this->page_id = $elRow['pid'];
}
$pageInfo = BackendUtility::readPageAccess($this->page_id, $this->perms_clause);
$assigns['pageInfo'] = $pageInfo;
if (is_array($pageInfo) && $backendUser->isInWebMount($pageInfo['pid'], $this->perms_clause)) {
</pre></p> TYPO3 Core - Feature #94993 (Closed): Allow to use GeneralUtility::xml2array without cachehttp://forge.typo3.org/issues/949932021-08-25T13:11:10ZDaniel Siepmanncoding@daniel-siepmann.de
We need this for two reasons in our customer projects:
<ul>
<li>Many unique calls that consume unnecessary memory due to internal caching</li>
<li>Usage within PHPUnit data providers. It would generate a singleton instance which is unexpected and unrelated to the test, but breaks tests as it is called before resetting singletons. This should also work without tests in UnitTests.</li>
</ul> TYPO3 Core - Bug #94812 (Closed): Autoloading for EXT:filelist is missinghttp://forge.typo3.org/issues/948122021-08-11T12:43:34ZDaniel Siepmanncoding@daniel-siepmann.de
<p>The bug was introduced with <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Avoid root-only fields in extensions composer.json (Closed)" href="http://forge.typo3.org/issues/94747">#94747</a> where autoloading was accidentally removed.</p> TYPO3 Core - Bug #92761 (Closed): TypeError in Wizard TableController if db contains nullhttp://forge.typo3.org/issues/927612020-11-03T15:33:09ZDaniel Siepmanncoding@daniel-siepmann.de
<p>A TypeError might occur when using the TableController as wizard for an input field in TCA.<br />Given the following configuration for TCA field:<br /><pre>
'example_field' => [
'exclude' => true,
'label' => 'example field for table wizard',
'config' => [
'default' => '',
'type' => 'text',
'renderType' => 'textTable',
'cols' => 80,
'rows' => 15,
'wrap' => 'off',
],
],
</pre></p>
<p>And the following ext_tables.sql:<br /><pre>
example_field mediumtext,
</pre></p>
<p>That will result in:<br /><pre>
(1/1) TypeError
Argument 1 passed to TYPO3\CMS\Backend\Controller\Wizard\TableController::configurationStringToArray() must be of the type string, null given, called in /typo3/sysext/backend/Classes/Controller/Wizard/TableController.php on line 316
</pre></p>
<p>As the called method requires a string, but null is passed from db query result.</p>
<p>The code is the same for 9, 10 and master, the issue should exist in all three versions. We've encountered the issue in v10 LTS.</p> TYPO3 Core - Bug #92732 (Closed): API example setFormat in changelog is wronghttp://forge.typo3.org/issues/927322020-10-29T11:39:43ZDaniel Siepmanncoding@daniel-siepmann.de
<p><a class="external" href="https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/10.3/Feature-90266-Fluid-basedTemplatedEmails.html">https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/10.3/Feature-90266-Fluid-basedTemplatedEmails.html</a> states `setFormat` should be used, while `format` is implemented.</p>
<p>See implementation:<br /><a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/10.4/typo3/sysext/core/Classes/Mail/FluidEmail.php#L70">https://github.com/TYPO3/TYPO3.CMS/blob/10.4/typo3/sysext/core/Classes/Mail/FluidEmail.php#L70</a><br /><a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/core/Classes/Mail/FluidEmail.php#L70">https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/core/Classes/Mail/FluidEmail.php#L70</a></p> TYPO3 Core - Bug #91894 (Closed): Cast transOrigPointerField value to integer to ensure return ty...http://forge.typo3.org/issues/918942020-07-30T08:26:37ZDaniel Siepmanncoding@daniel-siepmann.de
<p>When using sqlite, data fetched from DB is not of expected data types.<br />Therefore some return type hints will break.</p>
<p>In order to not break resolvePreviewRecordId(), there has to be a cast.</p>
<p>This prevents users from editing translated records.</p> TYPO3 Core - Bug #90969 (Closed): Administration log broken due to unsupported type annotationhttp://forge.typo3.org/issues/909692020-04-07T12:27:54ZDaniel Siepmanncoding@daniel-siepmann.de
<p><a class="external" href="https://github.com/TYPO3/TYPO3.CMS/commit/555e116f405295edf63394b647d680a9d46de0f7">https://github.com/TYPO3/TYPO3.CMS/commit/555e116f405295edf63394b647d680a9d46de0f7</a> adjusted the type annotation for two properties in the model.<br />These are not supported by extbase and result in the following error:</p>
<blockquote>
<p>(1/1) #1579965021 TYPO3\CMS\Extbase\Persistence\Generic\Mapper\Exception\UnknownPropertyTypeException<br />The type of property TYPO3\CMS\Belog\Domain\Model\LogEntry::tableName could not be identified, therefore the desired value (0) cannot be mapped onto it. The type of a class property is usually defined via php doc blocks. Make sure the property has a valid @var tag set which defines the type.</p>
</blockquote> TYPO3 Core - Bug #90241 (Closed): ArrayUtility "array_key_exists() expects parameter 2 to be array"http://forge.typo3.org/issues/902412020-01-29T12:58:15ZDaniel Siepmanncoding@daniel-siepmann.de
<p>Inside <em>\TYPO3\CMS\Core\Utility\ArrayUtility::getValueByPath()</em> no type check is executed when working with array.<br />This can lead to the PHP warning "array_key_exists() expects parameter 2 to be array".<br />Example call causing the warning:</p>
<pre><code class="php syntaxhl" data-language="php"><span class="nc">\TYPO3\CMS\Core\Utility\ArrayUtility</span><span class="o">::</span><span class="nf">getValueByPath</span><span class="p">(</span>
<span class="p">[</span>
<span class="s1">'foo'</span> <span class="o">=></span> <span class="p">[</span>
<span class="s1">'baz'</span> <span class="o">=></span> <span class="mi">42</span>
<span class="p">],</span>
<span class="p">],</span>
<span class="s1">'foo/baz/baz'</span>
<span class="p">);</span>
</code></pre>
<p>as during 2nd baz, the "array" is an integer.</p>
<p>The expected behaviour would be <em>throw new MissingArrayPathException('Segment ' . $segment . ' of path ' . implode($delimiter, $path) . ' does not exist in array', 1341397869);</em>, just like when the segment does not exist. As it does not exist.</p> TYPO3 Core - Bug #89583 (Closed): 2nd double Quote in error messagehttp://forge.typo3.org/issues/895832019-11-05T09:54:04ZDaniel Siepmanncoding@daniel-siepmann.de
<p>There is a 2nd double quote in exception 1436717266, which might lead to confusion whether it is part of the dynamic value within the exception.</p> TYPO3 Core - Bug #89432 (Closed): Fix Extbase redirect param type annotationhttp://forge.typo3.org/issues/894322019-10-16T15:33:20ZDaniel Siepmanncoding@daniel-siepmann.de
<p>Right now the method accepts strings and nulls for some arguments, but only string is defined within PHPDoc.</p>
<p>This prevents static code analysis for further code using this method, e.g. inside extensions.</p> TYPO3 Core - Task #89409 (Closed): Fix Extbase getArgument return type annotationhttp://forge.typo3.org/issues/894092019-10-14T13:32:50ZDaniel Siepmanncoding@daniel-siepmann.de
<p>Right now the method can return whatever an argument is, but only string is defined within PHPDoc. E.g. arguments can be an array instead.</p>
<p>This prevents static code analysis for further code using this method, e.g. inside extensions.</p> TYPO3 Core - Bug #86592 (Closed): Argument 2 passed to TYPO3\CMS\Extbase\Routing\ExtbasePluginEnh...http://forge.typo3.org/issues/865922018-10-08T10:06:19ZDaniel Siepmanncoding@daniel-siepmann.de
<p>Given the following routing configuration:<br /><pre><code class="yaml syntaxhl" data-language="yaml"><span class="na">routeEnhancers</span><span class="pi">:</span>
<span class="na">ExamplePlugin</span><span class="pi">:</span>
<span class="na">type</span><span class="pi">:</span> <span class="s">Extbase</span>
<span class="na">extension</span><span class="pi">:</span> <span class="s">ExampleExtension</span>
<span class="na">plugin</span><span class="pi">:</span> <span class="s">Address</span>
<span class="na">defaultController</span><span class="pi">:</span> <span class="s1">'</span><span class="s">Address::index'</span>
<span class="na">routes</span><span class="pi">:</span>
<span class="pi">-</span>
<span class="na">routePath</span><span class="pi">:</span> <span class="s1">'</span><span class="s">/edit/{address}'</span>
<span class="na">_controller</span><span class="pi">:</span> <span class="s1">'</span><span class="s">Address::edit'</span>
<span class="na">_arguments</span><span class="pi">:</span>
<span class="s1">'</span><span class="s">address'</span><span class="err">:</span> <span class="s1">'</span><span class="s">address'</span>
<span class="pi">-</span>
<span class="na">routePath</span><span class="pi">:</span> <span class="s1">'</span><span class="s">/update'</span>
<span class="na">_controller</span><span class="pi">:</span> <span class="s1">'</span><span class="s">Address::update'</span>
<span class="na">aspects</span><span class="pi">:</span>
<span class="na">address</span><span class="pi">:</span>
<span class="na">type</span><span class="pi">:</span> <span class="s">PersistedPatternMapper</span>
<span class="na">tableName</span><span class="pi">:</span> <span class="s1">'</span><span class="s">tx_exampleextension_domain_model_address'</span>
<span class="na">routeFieldPattern</span><span class="pi">:</span> <span class="s1">'</span><span class="s">^(?P<company_name>.+)-(?P<uid>\d+)$'</span>
<span class="na">routeFieldResult</span><span class="pi">:</span> <span class="s1">'</span><span class="s">{company_name}-{uid}'</span>
</code></pre></p>
<p>and submitting the edit form, results in the url <em><a class="external" href="https://workshop-extension.at.localhost/plugin/update">https://workshop-extension.at.localhost/plugin/update</a></em> and the error:<br /><pre>
Argument 2 passed to TYPO3\CMS\Extbase\Routing\ExtbasePluginEnhancer::applyControllerActionValues() must be of the type array, null given
</pre></p> TYPO3 Core - Bug #55517 (Closed): ClassLoader not working with NullBackend for legacy classes http://forge.typo3.org/issues/555172014-01-31T14:58:05ZDaniel Siepmanncoding@daniel-siepmann.de
<p>Setting <em>cache_core</em> to <em>NullBackend</em><br /><pre>
$GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations']['cache_core']['backend'] = '\TYPO3\CMS\Core\Cache\Backend\NullBackend';
</pre> <br />creates Fatal Errors for calls to old class names like <em>t3lib_extMgm</em>.<br />You can reproduce it e.g. with a call to the <em>t3lib_extMgm</em> class inside <em>ext_tables.php</em> of an extension.</p>
<p>This error is not catched using the <em>Install Tool</em> <em>Check for broken extensions</em> option.</p>