TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692016-10-04T15:23:33ZTYPO3 Forge
Redmine TYPO3 Core - Bug #78142 (Closed): Conditions with replaced constants not working in TypoScript Ob...http://forge.typo3.org/issues/781422016-10-04T15:23:33ZNicole Cordestypo3@cordes.co
<p>Steps to reproduce:</p>
<p>1) add a typoscript constant</p>
<p><code>test = 1</code></p>
<p>2) add a condition in your typoscript setup</p>
<p><code>[globalVar = LIT:1 = {$test}] <br />lib.hello = world<br />[end]</code></p>
<p>3) go to template -> typoscript object browser</p>
<p>4) choose display constants "Substituted constants in green"</p>
<p>5) try to activate your condition "[globalVar = LIT:1 = 1]" (1 in green)</p>
<p>Expectation:<br />1) lib.hello is world<br />2) selected condition is checked</p>
<p>Actual result:<br />nothing happens</p> TYPO3 Core - Task #69584 (Closed): Remove wrong datasets in sanitizeLocalUrlValidPathsDataProviderhttp://forge.typo3.org/issues/695842015-09-07T14:48:07ZNicole Cordestypo3@cordes.co
<p>Within the GeneralUtilityTest::sanitizeLocalUrlValidPathsDataProvider are still wrong dataset unfortunately. As on Windows systems the GeneralUtility::getIndpEnv('TYPO3_SITE_URL') results in <a class="external" href="http://D:/AbsolutePathToTypo3Installation">http://D:/AbsolutePathToTypo3Installation</a> those test were moved to an own DataProvider which makes sure the HTTP_HOST and SCRIPT_NAME are set correctly before calling GeneralUtility::getIndpEnv().</p> TYPO3 Core - Bug #69475 (Closed): Streamline unit tests for GeneralUtility::sanitizeLocalUrl http://forge.typo3.org/issues/694752015-09-02T14:46:26ZNicole Cordestypo3@cordes.co
<p>Currently the unit tests for the function GeneralUtility::sanitizeLocalUrl are just working by accident. To add further tests we should streamline the tests and set/add expectations.</p> TYPO3 Core - Task #67586 (Closed): Add basic unit tests for \TYPO3\CMS\Frontend\ContentObject\Con...http://forge.typo3.org/issues/675862015-06-17T21:42:37ZNicole Cordestypo3@cordes.co
<p>We should add some basic unit tests for \TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer::typoLink function.</p> TYPO3 Core - Bug #65214 (Rejected): Failing functional test exportPagesAndRelatedTtContenthttp://forge.typo3.org/issues/652142015-02-21T20:49:20ZNicole Cordestypo3@cordes.co
<p>The test exportPagesAndRelatedTtContent from typo3/sysext/impexp/Tests/Functional/Export/PagesAndTtContent/ExportTest.php fails after merging <a class="external" href="https://review.typo3.org/#/c/37016/">https://review.typo3.org/#/c/37016/</a></p> TYPO3 Core - Bug #64682 (Closed): Ensure unix like temp pathshttp://forge.typo3.org/issues/646822015-01-31T12:14:27ZNicole Cordestypo3@cordes.co
<p>Using tempnam() returns a Windows paths containing backslashes. To ensure functionality (and fix functional tests) we should ensure unix like paths with forward slashes.</p> TYPO3 Core - Bug #64680 (Closed): Improve FunctionalTestCaseBootstrapUtility for use on Windows s...http://forge.typo3.org/issues/646802015-01-31T11:52:06ZNicole Cordestypo3@cordes.co
<p>Several tweaks are needed to get functional test running on Windows system.</p> TYPO3 Core - Bug #64679 (Closed): Failing functional tests on Windows systemhttp://forge.typo3.org/issues/646792015-01-31T11:50:31ZNicole Cordestypo3@cordes.co
<p>Still some functional tests fail on Windows system.</p> TYPO3 Core - Bug #64657 (Closed): Failing unit test in SqlSchemaMigrationServiceTest on Windows s...http://forge.typo3.org/issues/646572015-01-30T18:33:05ZNicole Cordestypo3@cordes.co
<p>The test getFieldDefinitionsFileContentHandlesMultipleWhitespacesInFieldDefinitions fails on Windows systems because the expected and actual array have a different array key for the table name. On run time within the code tables names are set explicit to lower cases.</p> TYPO3 Core - Bug #64656 (Closed): Failing unit tests due to wrong path handlinghttp://forge.typo3.org/issues/646562015-01-30T17:19:15ZNicole Cordestypo3@cordes.co
<p>In the TYPO3\CMS\Fluid\Tests\Unit\View\StandaloneViewTest test case multiple tests fail on Windows systems because of wrong directory separator. Within the core classes unix like paths are used but tested agains native Windows paths.</p> TYPO3 Core - Bug #64651 (Closed): Failling unit test in DatabaseConnectionTesthttp://forge.typo3.org/issues/646512015-01-30T16:29:55ZNicole Cordestypo3@cordes.co
<p>There is a check if positive 64bit integer values are supported by the system. As there isn't any check if the system is a 64bit system, this test fails for 32bit systems. As currently 32bit is mostly used on Windows systems (PHP x64 is still experimental) this issue is kind of Windows related.</p> TYPO3 Core - Bug #64644 (Closed): Failling unit test in GeneralUtilityTest for Windows systemhttp://forge.typo3.org/issues/646442015-01-30T15:45:57ZNicole Cordestypo3@cordes.co
<p>Due to another drive mapping on Windows systems paths don't start with an slash but with [C]:\. This causes a wrong test results parsing the starting slash for TYPO3_SITE_PATH.</p> TYPO3 Core - Bug #58559 (Closed): Always convert webRoot to unix styled path in UnitTestBootstraphttp://forge.typo3.org/issues/585592014-05-06T12:26:46ZNicole Cordestypo3@cordes.co
<p>As in the bootstrap of the functional tests, we have to turn webRoot to an unix styled path before using it. Otherwise tests can not be run on Windows systems.</p> TYPO3 Core - Task #46950 (Closed): Remove deprecated codehttp://forge.typo3.org/issues/469502013-04-05T19:44:25ZNicole Cordestypo3@cordes.co
<p>Still some deprecated code is used in version extension.</p> TYPO3 Core - Bug #40490 (Closed): Wrong Scheduler task configuration for namespace versionhttp://forge.typo3.org/issues/404902012-08-31T17:10:23ZNicole Cordestypo3@cordes.co
<p>$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['scheduler']['tasks']['TYPO3\\CMS\\Workspaces\\Service\\AutoPublishServiceTask']</p>
<p>should be</p>
<p>$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['scheduler']['tasks']['TYPO3\\CMS\\Workspaces\\Task\\AutoPublishTask']</p>
<p>to equal own class.</p>