TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-04-05T13:17:01ZTYPO3 Forge
Redmine TYPO3 Core - Bug #100468 (Needs Feedback): Missing assets folder when creating public folder aft...http://forge.typo3.org/issues/1004682023-04-05T13:17:01ZDaniel Siepmanncoding@daniel-siepmann.de
<p>Given that:</p>
<ol>
<li>I've created a TYPO3 extension as composer package</li>
<li>That extension does not have a Public/ folder yet</li>
<li>The extension is installed</li>
<li>A new Public/ folder is created within that extension</li>
<li>The folder does not show up within _assets/ folder</li>
</ol>
<p>That might happen during setting up an extension, e.g. a sitepackage.</p>
<p>Workaround:</p>
<ol>
<li><code>composer dumpautoload</code> after the Resources/Public folders are added</li>
</ol>
<p>Maybe we can ease that somehow? Provide a command or maybe "fix" that by a proper 404 handling within TYPO3 itself? I fear that many people will run into that issue when starting with v12.</p> TYPO3 Core - Bug #99493 (New): On CLI no exceptions are loggedhttp://forge.typo3.org/issues/994932023-01-08T18:08:54ZHelmut Hummeltypo3@helhum.io
<p>Since symfony/console catches all exceptions from commands<br />to render the exception, the TYPO3 exception handler is never triggered,<br />thus not only completely unused on CLI, but also does not log anything<br />to the configured logs</p> TYPO3 Core - Bug #96388 (Under Review): Error when replacing polyfill packages in the root compos...http://forge.typo3.org/issues/963882021-12-19T12:15:16ZSimon Gillitypo3@gilbertsoft.org
<p>Symfony recommends to replace the polyfills of installed PHP extensions in the root package to reduce the overhead. Currently when replacing the various polyfill packages an exception is thrown during the autoload dump:</p>
<pre>
Executing "TYPO3\CMS\Core\Composer\PackageArtifactBuilder":
[UnexpectedValueException]
The package "backend" depends on "symfony/polyfill-mbstring" which is not present in the system.
Exception trace:
() at /var/www/html/vendor/typo3/cms-core/Classes/Package/PackageManager.php:1116
TYPO3\CMS\Core\Package\PackageManager->convertConfigurationForGraph() at /var/www/html/vendor/typo3/cms-core/Classes/Package/PackageManager.php:1197
TYPO3\CMS\Core\Package\PackageManager->buildDependencyGraph() at /var/www/html/vendor/typo3/cms-core/Classes/Package/PackageManager.php:1085
TYPO3\CMS\Core\Package\PackageManager->sortPackageStatesConfigurationByDependency() at /var/www/html/vendor/typo3/cms-core/Classes/Composer/PackageArtifactBuilder.php:138
TYPO3\CMS\Core\Composer\PackageArtifactBuilder->sortPackagesAndConfiguration() at /var/www/html/vendor/typo3/cms-core/Classes/Composer/PackageArtifactBuilder.php:103
TYPO3\CMS\Core\Composer\PackageArtifactBuilder->run() at /var/www/html/vendor/typo3/cms-composer-installers/src/Plugin/Core/ScriptDispatcher.php:72
TYPO3\CMS\Composer\Plugin\Core\ScriptDispatcher->executeScripts() at /var/www/html/vendor/typo3/cms-composer-installers/src/Plugin/PluginImplementation.php:93
TYPO3\CMS\Composer\Plugin\PluginImplementation->postAutoloadDump() at /var/www/html/vendor/typo3/cms-composer-installers/src/Installer/Plugin.php:101
TYPO3\CMS\Composer\Installer\Plugin->listen() at n/a:n/a
call_user_func() at phar:///usr/local/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php:191
Composer\EventDispatcher\EventDispatcher->doDispatch() at phar:///usr/local/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php:118
Composer\EventDispatcher\EventDispatcher->dispatchScript() at phar:///usr/local/bin/composer/src/Composer/Autoload/AutoloadGenerator.php:415
Composer\Autoload\AutoloadGenerator->dump() at phar:///usr/local/bin/composer/src/Composer/Installer.php:333
Composer\Installer->run() at phar:///usr/local/bin/composer/src/Composer/Command/UpdateCommand.php:248
Composer\Command\UpdateCommand->execute() at phar:///usr/local/bin/composer/vendor/symfony/console/Command/Command.php:245
Symfony\Component\Console\Command\Command->run() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:835
Symfony\Component\Console\Application->doRunCommand() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:185
Symfony\Component\Console\Application->doRun() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:327
Composer\Console\Application->doRun() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:117
Symfony\Component\Console\Application->run() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:128
Composer\Console\Application->run() at phar:///usr/local/bin/composer/bin/composer:73
require() at /usr/local/bin/composer:29
</pre>
<p>There are currently two issues:</p>
<p>1. The replaces are not detected<br />2. It's always the backend which is listed in the message even if the backend has not dependency to polyfills at all</p>
<p>Minimal composer.json to reproduce:</p>
<pre>
{
"name": "gilbertsoft/test-typo3-11",
"license": "MIT",
"description": "Testing TYPO3 11 polyfill issue.",
"require": {
"typo3/cms-core": "^11.5",
"typo3/minimal": "^11.5"
},
"provide": {
"symfony/polyfill-ctype": "*",
"symfony/polyfill-intl-grapheme": "*",
"symfony/polyfill-intl-icu": "*",
"symfony/polyfill-intl-idn": "*",
"symfony/polyfill-intl-normalizer": "*",
"symfony/polyfill-mbstring": "*",
"symfony/polyfill-php72": "*",
"symfony/polyfill-php73": "*"
}
}
</pre> TYPO3 Core - Feature #87013 (New): Add editMetaData a permission for users, storages, filemountshttp://forge.typo3.org/issues/870132018-11-27T11:35:49ZHelmut Hummeltypo3@helhum.io
<p>To be more flexible with permissions to edit meta data of files, we need to add it<br />to the permission list, so that it can be configured per user, storage and file mount.</p>
<p>To proceed, fix for <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Metadata not editable for a readonly file storage (Closed)" href="http://forge.typo3.org/issues/65636">#65636</a> needs to be merged first</p> TYPO3 Core - Bug #36161 (New): Include current Domain Model UID in calculated HMAChttp://forge.typo3.org/issues/361612012-04-16T16:58:19ZNico de Haenmail@ndh-websolutions.de
<p>We discussed this already at T3DD12. <br />The calculated HMAC does not take the current domain model UID in account as one would assume, if there is a HMAC form verification.</p>