TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692022-04-28T14:46:44ZTYPO3 Forge
Redmine TYPO3 Core - Bug #97508 (Closed): Update to PHPStan 1.6.3http://forge.typo3.org/issues/975082022-04-28T14:46:44ZTymoteusz Motylewskit.motylewski@gmail.comTYPO3 Core - Bug #92856 (New): "Admin Panel" naming confusinghttp://forge.typo3.org/issues/928562020-11-16T16:05:40ZTymoteusz Motylewskit.motylewski@gmail.com
<p>New TYPO3 users are confusing "Admin Panel" with TYPO3 Backend, as in many other systems (WP, Drupal, Magento,...) the "Admin Panel" (or Administration Panel) means the place we call "Backend".<br />More appropriate name would be "developer toolbar" or "debug bar" or sth similar.</p>
<p>Btw, the term "Backend" is also confusing, especialy with IT/devops, where it's used in the meaning of "upstream server".</p> TYPO3 Core - Bug #91017 (Closed): 9.5 changelog show deprecated TS conditions configuration as an...http://forge.typo3.org/issues/910172020-04-14T07:41:21ZTymoteusz Motylewskit.motylewski@gmail.comTYPO3 Core - Bug #90887 (Closed): Cange name in brokenlinkrepository test to not conflict with te...http://forge.typo3.org/issues/908872020-03-30T13:58:11ZTymoteusz Motylewskit.motylewski@gmail.comTYPO3 Core - Bug #90635 (New): Error is thrown when using EXT:extension_name for which is install...http://forge.typo3.org/issues/906352020-03-04T11:14:06ZTymoteusz Motylewskit.motylewski@gmail.com
<a name="Problem"></a>
<h2 >Problem<a href="#Problem" class="wiki-anchor">¶</a></h2>
<a name="Given"></a>
<h3 >Given<a href="#Given" class="wiki-anchor">¶</a></h3>
<p>- an extension e.g. yoast_seo copied to typo3conf/ext/yoast_typo3 (folder different than extension key)<br />- this extension has TYPOScript which references some file using EXT:yoast_seo syntax</p>
<a name="Result"></a>
<h3 >Result:<a href="#Result" class="wiki-anchor">¶</a></h3>
<p>- Backend is broken with "Call to a member function getPackagePath() on null" in ExtensionManagerUtility</p>
<a name="Expected"></a>
<h3 >Expected:<a href="#Expected" class="wiki-anchor">¶</a></h3>
<p>- either the file inclusion is ignored, or the path is correctly resolved (as TYPO3 can correctly translate yoast_seo to yoast_typo3 with <pre>$this->getPackageKeyFromComposerName($packageKey);</pre><br />- breaking whole system is not expected</p>
<a name="Technical-details"></a>
<h2 >Technical details:<a href="#Technical-details" class="wiki-anchor">¶</a></h2>
<p>in this setup<br />- PackageManager->isPackageActive('yoast_seo') return TRUE<br />- PackageManager->getPackageKeyFromComposerName('yoast_seo') returns 'yoast_typo3'<br />- PackageManager->isPackageRegistered('yoast_seo') returns TRUE<br />- PackageManager->isPackageAvailable('yoast_seo')returns TRUE<br />- ExtensionManagementUtility::isLoaded('yoast_seo') returns TRUE<br />- ExtensionManagementUtility::extPath('yoast_seo') throws "Call to a member function getPackagePath() on null" <br />- because PackageManager->getPackage('yoast_seo') returns null</p>
<p>Seems like the API is inconsistent here.</p>
<a name="Possible-solution"></a>
<h2 >Possible solution:<a href="#Possible-solution" class="wiki-anchor">¶</a></h2>
<p>change <br /><pre>
public function getPackage($packageKey)
{
if (!$this->isPackageRegistered($packageKey) && !$this->isPackageAvailable($packageKey)) {
throw new Exception\UnknownPackageException('Package "' . $packageKey . '" is not available. Please check if the package exists and that the package key is correct (package keys are case sensitive).', 1166546734);
}
return $this->packages[$packageKey];
}
</pre><br />to:<br /><pre>
public function getPackage($packageKey)
{
if (!$this->isPackageRegistered($packageKey) && !$this->isPackageAvailable($packageKey)) {
throw new Exception\UnknownPackageException('Package "' . $packageKey . '" is not available. Please check if the package exists and that the package key is correct (package keys are case sensitive).', 1166546734);
}
return $this->packages[$this->getPackageKeyFromComposerName($packageKey)];
}
</pre></p> TYPO3 Core - Bug #89687 (Closed): Page tree sends unnecessary datahttp://forge.typo3.org/issues/896872019-11-14T21:34:48ZTymoteusz Motylewskit.motylewski@gmail.com
<p>The page tree sends information about page items as json.<br />It contains all properties of the item even if they are defaylt values.</p>
<p>In order to save some bandwidth, we should only send non-default values.</p> TYPO3 Core - Bug #86423 (Closed): Use corect icon for editing query in ActionTaskhttp://forge.typo3.org/issues/864232018-09-28T15:01:44ZTymoteusz Motylewskit.motylewski@gmail.com
<p>info icon is used now, it should be edit instead.<br />see screenshot</p> TYPO3 Core - Bug #86360 (Closed): extbase tests on v8 are failing on postgreshttp://forge.typo3.org/issues/863602018-09-23T20:53:47ZTymoteusz Motylewskit.motylewski@gmail.com
<p>Since <a class="external" href="https://review.typo3.org/#/c/58357/">https://review.typo3.org/#/c/58357/</a></p>
<p>these 2 tests are failing:<br /><pre>
TYPO3\CMS\Extbase\Tests\Functional\Persistence\TranslationTest::fetchingHiddenPostsReturnsHiddenOverlay
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'Post10'
+'GR:Post1'
TYPO3\CMS\Extbase\Tests\Functional\Persistence\TranslationTest::fetchingHiddenPostsWithIgnoreEnableField
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'Post10'
+'Post1'
</pre></p> TYPO3 Core - Bug #86332 (Closed): QuerySettings dont get language mode from context in lang 0http://forge.typo3.org/issues/863322018-09-20T15:33:06ZTymoteusz Motylewskit.motylewski@gmail.com
<p>This is a little regression after <a class="external" href="https://review.typo3.org/#/c/57424/">https://review.typo3.org/#/c/57424/</a></p> TYPO3 Core - Bug #86235 (Closed): Undefined variable $applicationContext in Bootstrap.phphttp://forge.typo3.org/issues/862352018-09-12T17:13:13ZTymoteusz Motylewskit.motylewski@gmail.com
<p>since refactoring done in <a class="external" href="https://github.com/TYPO3/TYPO3.CMS/commit/18cffa12268e299bbf0e7273734d9cfabae0ae99#diff-7465272348c392bfb9e20e459875ae33R78">https://github.com/TYPO3/TYPO3.CMS/commit/18cffa12268e299bbf0e7273734d9cfabae0ae99#diff-7465272348c392bfb9e20e459875ae33R78</a><br />the $applicationContext is undefined.</p> TYPO3 Core - Bug #86233 (Closed): Fix code formatting changelog rst fileshttp://forge.typo3.org/issues/862332018-09-12T13:31:52ZTymoteusz Motylewskit.motylewski@gmail.com
<p>see <a class="external" href="https://docs.typo3.org/typo3cms/extensions/core/Changelog/master/Feature-80398-Utf8mb4OnMysqlByDefaultForNewInstances.html">https://docs.typo3.org/typo3cms/extensions/core/Changelog/master/Feature-80398-Utf8mb4OnMysqlByDefaultForNewInstances.html</a></p> TYPO3 Core - Bug #85999 (Closed): Blog example blog fe_user subtype should use namespaceshttp://forge.typo3.org/issues/859992018-08-27T21:21:12ZTymoteusz Motylewskit.motylewski@gmail.com
<p>In all places it is already changed to: ExtbaseTeam\BlogExample\Domain\Model\Administrator<br />but still in TCA overrides it's Tx_BlogExample_Domain_Model_Administrator</p>
<p>Because of this bug, it's not possible to select any record in Blog->Administrator select box in BE.</p> TYPO3 Core - Bug #85976 (Closed): Wrong relation in FAL fixture data for TS and extbase renderinghttp://forge.typo3.org/issues/859762018-08-25T00:45:13ZTymoteusz Motylewskit.motylewski@gmail.com
<p>In the <br />typo3/sysext/frontend/Tests/Functional/Rendering/DataSet/LiveDefaultElements.csv</p>
<p>The sys_file_reference record 127 (Kasper) is related to tt_content 298 "Regular Element #2",</p>
<p>however sys_file_reference 128 (which is a translation of 127) is connected to tt_content 300 ("[Translate to Dansk:] Regular Element #3").</p>
<p>It is wrong, because translated sys_file_reference should be connected to translated version of the tt_content.</p> TYPO3 Core - Bug #85916 (Closed): Time tracking in adminpanel shows strange numbers http://forge.typo3.org/issues/859162018-08-21T12:11:36ZTymoteusz Motylewskit.motylewski@gmail.com
<p>some times are very small and some are negative.</p> TYPO3 Core - Task #64324 (Closed): Move ConditionMatcherTest into one placehttp://forge.typo3.org/issues/643242015-01-17T00:02:55ZTymoteusz Motylewskit.motylewski@gmail.com
<p>Move ConditionMatcherTest into one place.<br />Tests for <br />\TYPO3\CMS\Backend\Configuration\TypoScript\ConditionMatching\ConditionMatcher <br />are placed in two test classes:</p>
<p>TYPO3\CMS\Backend\Tests\Unit\Configuration\TypoScript\ConditionMatching\ConditionMatcherTest</p>
<p>and</p>
<p>TYPO3\CMS\Core\Tests\Unit\Configuration\ConditionMatcherTest</p>
<p>It would be nice to have them merged.</p>