TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-03-14T17:36:06ZTYPO3 Forge
Redmine TYPO3 Core - Bug #103400 (Under Review): Avoid mapping route values that are out of scopehttp://forge.typo3.org/issues/1034002024-03-14T17:36:06ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Task #102610 (Closed): Revert "[BUGFIX] Set HTTP timeout to 20 seconds"http://forge.typo3.org/issues/1026102023-12-06T10:10:08ZOliver Haderoliver.hader@typo3.org
<p>The change for issue <a class="issue tracker-1 status-8 priority-3 priority-lowest" title="Bug: Update Guzzle timeout to 20 seconds (Under Review)" href="http://forge.typo3.org/issues/102606">#102606</a> has the potential to do more harm than good.</p>
<p>The initial intention was to define a HTTP timeout to be lower than the PHP <code>max_execution_time</code>.<br />Defining general timeout of 20 seconds now also limits e.g. long running CLI processes (e.g. importing data).</p>
<p>→ corresponding discussion in Slack: <a class="external" href="https://typo3.slack.com/archives/C03AM9R17/p1701850585082239?thread_ts=1701810994.856119&cid=C03AM9R17">https://typo3.slack.com/archives/C03AM9R17/p1701850585082239?thread_ts=1701810994.856119&cid=C03AM9R17</a>)</p> TYPO3 Core - Bug #101809 (Resolved): Ensure minimal dependency order in PackageManagerhttp://forge.typo3.org/issues/1018092023-08-31T10:23:22ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Bug #101705 (Resolved): Update composer.lock for typo3/html-sanitizer:2.1.3http://forge.typo3.org/issues/1017052023-08-17T11:03:20ZOliver Haderoliver.hader@typo3.org
<p>see <a class="external" href="https://stackoverflow.com/questions/76920144/typo3-11-5-30-error-after-bootstrap-update-undefined-function-mb-split">https://stackoverflow.com/questions/76920144/typo3-11-5-30-error-after-bootstrap-update-undefined-function-mb-split</a></p> TYPO3 Core - Bug #101460 (Resolved): Allow strict-dynamic only for applicable CSP directiveshttp://forge.typo3.org/issues/1014602023-07-27T10:56:06ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Bug #101253 (Resolved): Normalize filename of uploaded fileshttp://forge.typo3.org/issues/1012532023-07-05T18:12:07ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Task #99366 (Closed): Add backward compatibility handling for frontend loginhttp://forge.typo3.org/issues/993662022-12-14T11:10:51ZOliver Haderoliver.hader@typo3.org
<p>Security fix for TYPO3-CORE-SA-2022-013 in <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/77084">https://review.typo3.org/c/Packages/TYPO3.CMS/+/77084</a> enforced the existence of an HMAC signed <code>pid</code> value. There have been reports in custom authentication services, where this might be problematic (albeit it could be solved). To provide better backward compatibility, a new feature flag is introduced.</p> TYPO3 Core - Feature #95054 (Under Review): Add possibility to add HTTP headers in frontendhttp://forge.typo3.org/issues/950542021-08-31T13:46:32ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Task #92509 (Closed): Add base64url encode/decode functionalityhttp://forge.typo3.org/issues/925092020-10-07T20:04:34ZOliver Haderoliver.hader@typo3.org
<p>Add static library functions that allow using base64url-compliant values (according to <a class="external" href="https://tools.ietf.org/html/rfc4648#section-5">https://tools.ietf.org/html/rfc4648#section-5</a>) - this also avoids duplications in user-land code.</p> TYPO3 Core - Task #91242 (Closed): ...http://forge.typo3.org/issues/912422020-04-30T13:01:32ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Task #87666 (Closed): Add language synchronization tests for TCA type inline/CSVhttp://forge.typo3.org/issues/876662019-02-06T14:32:59ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Story #84917 (New): Make use of schema definition & relationship layerhttp://forge.typo3.org/issues/849172018-05-03T14:36:29ZOliver Haderoliver.hader@typo3.org
<ul>
<li>DataHandler, RelationHandler, DataMapProcessor</li>
<li>Extbase DataMapFactory, Storage Backend</li>
<li>FormEngine DataProviders, Containers</li>
<li>RootlineUtility</li>
</ul>
<p>... and more ...</p> TYPO3 Core - Story #84916 (New): Provide generic entity relationship modelhttp://forge.typo3.org/issues/849162018-05-03T14:30:00ZOliver Haderoliver.hader@typo3.org
<p>Expected goal</p>
<pre>
$contentSchemaDefinition = (new SomeService)->getSchemaDefinition('tt_content');
$fileReferenceSchemaDefinition = (new SomeService)->getSchemaDefinition('sys_file_reference');
var_dump($contentSchemaDefinition->getProperty('media')->getRelations());
var_dump($fileReferenceSchemaDefinition->getProperty('uid_foreign')->getRelations());
</pre>
<p>might output something like</p>
<pre>
# relations for tt_content.media
+ ActiveRelation: schemaName "sys_file_reference"
</pre>
<pre>
# relations for sys_file_reference.uid_foreign
+ PassiveRelation: schemaName "tt_content", propertyName: "image"
+ PassiveRelation: schemaName "tt_content", propertyName: "media"
+ PassiveRelation: schemaName "tt_content", propertyName: "assets"
</pre>
<p>Currently the "opposite usage" for relations is not explicitly known. In order to enhance look ups this information should be cached along with the plain schema definition (e.g. TCA).</p> TYPO3 Core - Story #84915 (New): Provide generic entity schema definitionhttp://forge.typo3.org/issues/849152018-05-03T14:19:06ZOliver Haderoliver.hader@typo3.org
<p>Expected goal</p>
<pre>
$factory = new TcaSchemaDefinitionFactory($GLOBALS['TCA']);
$schemaDefinition = $factory->buildForTable('tt_content');
$service = new SchemaDefinitionService();
$mediaProperty = $schemaDefinition->getProperty('media');
$service->isRelational(mediaProperty);
if ($service->getRelationType($mediaProperty) === Relation::TYPE_ONE_TO_MANY_COMPOSITION)) { ... }
</pre>
<p>The API above can still change. Besides that Extbase <code>DataMapFactory</code> could be considered as foundation as well.</p> TYPO3 Core - Bug #21206 (Closed): Add more unit tests for t3lib_matchConditionhttp://forge.typo3.org/issues/212062009-10-08T16:12:05ZOliver Haderoliver.hader@typo3.org
Extend the number of unit tests in t3lib_matchCondition for the expressions:
<ul>
<li>language</li>
<li>usergroup</li>
<li>loginUser</li>
<li>globalString</li>
<li>treeLevel</li>
<li>PIDupinRootline</li>
<li>PIDinRootline</li>
<li>compatVersion</li>
<li>generic tests to access the namespaces GP, TSFE, ENV, IENV</li>
</ul>
<p>(issue imported from #M12153)</p>