TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-02-26T11:08:29ZTYPO3 Forge
Redmine TYPO3 Core - Bug #103199 (Resolved): TransformViewHelper throws exception when spam protection is...http://forge.typo3.org/issues/1031992024-02-26T11:08:29ZHelmut Hummeltypo3@helhum.io
<p>DOMElement::setAttribute(): Argument #2 ($value) must be of type string, int given<br />typo3/cms-frontend/Classes/Html/HtmlWorker.php line 128</p>
<p>Reason is that on data attribute value is of type integer.</p> TYPO3 Core - Bug #99381 (Resolved): TCA columnsOverrides overrides default values set via defValshttp://forge.typo3.org/issues/993812022-12-15T12:11:37ZHelmut Hummeltypo3@helhum.io
<a name="Prerequisite"></a>
<h2 >Prerequisite<a href="#Prerequisite" class="wiki-anchor">¶</a></h2>
<p>Given the following configuration:</p>
<p>TCA/tt_content/types/menu_pages/columnsOverrides/sys_language_uid/config =</p>
<p>default = 0<br />renderType = hidden<br />type = input</p>
<a name="Test"></a>
<h2 >Test<a href="#Test" class="wiki-anchor">¶</a></h2>
<p>When I create a record of type menu_pages in sys_language_uid = 4 via page module</p>
<a name="Expectation"></a>
<h2 >Expectation<a href="#Expectation" class="wiki-anchor">¶</a></h2>
<p>I expect the sys_language_uid is rendered as hidden field with value 4 in HTML of the editing form</p>
<a name="Actual-result"></a>
<h2 >Actual result<a href="#Actual-result" class="wiki-anchor">¶</a></h2>
<p>Currently the hidden field has the value 0</p>
<p>The reason for that is the change in <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: TCA columnsOverrides ignores default value (Closed)" href="http://forge.typo3.org/issues/86876">#86876</a> which does not respect a default value set in "defaultValues"</p> TYPO3 Core - Bug #95660 (Closed): felogin uses different upgrade wizard identifier in class than ...http://forge.typo3.org/issues/956602021-10-15T09:53:02ZHelmut Hummeltypo3@helhum.ioTYPO3 Core - Bug #81926 (Closed): Files cannot be deleted any morehttp://forge.typo3.org/issues/819262017-07-20T12:25:52ZHelmut Hummeltypo3@helhum.io
<p><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: If a processed file is updated, the database row is not written within the same request (Closed)" href="http://forge.typo3.org/issues/80359">#80359</a> introduced a regression, leading to files cannot be deleted any more</p> TYPO3 Core - Bug #81832 (Closed): typo3-ter/wizard-crpagetree cannot be installed with composer a...http://forge.typo3.org/issues/818322017-07-11T12:23:15ZHelmut Hummeltypo3@helhum.io
<p>This is a minimal composer.json to reproduce my issue:</p>
<pre>
{
"repositories": [
{
"type": "composer",
"url": "https://composer.typo3.org/"
}
],
"name": "stefanr/test",
"require": {
"typo3/cms": "^7.6",
"typo3-ter/wizard-crpagetree": "1.1.0"
},
"extra": {
"typo3/cms": {
"cms-package-dir": "{$vendor-dir}/typo3/cms",
"web-dir": "web"
}
}
}
</pre>
<p>When I run<br /><code>composer install </code><br />I get the following error:<br /><pre>Your requirements could not be resolved to an installable set of packages.
Problem 1
- typo3-ter/func 9.0.1 requires typo3/cms-core >= 9.0.0, <= 9.0.99 -> no matching package found.
- typo3-ter/func 9.0.0 requires typo3/cms-core >= 9.0.0, <= 9.0.99 -> no matching package found.
- typo3-ter/wizard-crpagetree 1.1.0 requires typo3-ter/func * -> satisfiable by typo3-ter/func[9.0.0, 9.0.1].
- Installation request for typo3-ter/wizard-crpagetree 1.1.0 -> satisfiable by typo3-ter/wizard-crpagetree[1.1.0].
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.</pre></p> TYPO3 Core - Bug #81279 (Closed): Files unnecessarily copied for local processinghttp://forge.typo3.org/issues/812792017-05-20T11:14:25ZHelmut Hummeltypo3@helhum.io
<p>When opening meta data edit view of a large file is copied for processing<br />to show a thumbnail, even when the file extension isn't in imagefile_ext list.</p>
<p>This is especially annoying when using a FAL driver for a remote storage.</p> TYPO3 Core - Bug #72557 (Closed): Harden fallback class map generationhttp://forge.typo3.org/issues/725572016-01-06T15:28:42ZHelmut Hummeltypo3@helhum.io
<p>It could happen when an extension does not provide any<br />autoload definition, that valid classes are not or<br />invalid classes are taken into account during class map generation.</p>
<p>To fix this, update to latest composer code that supports<br />a blacklist for class map generation and provide tests<br />folder and ext_update files as valid black list.</p>
<p>Also add "Resources" and "res" folder to black list, which<br />very often also contain php classes, which are then manually required.</p>
<p>Also fix, streamline and add tests to verify this behavior.</p> TYPO3 Core - Bug #72520 (Closed): Use correct file extension for language fileshttp://forge.typo3.org/issues/725202016-01-04T13:17:42ZHelmut Hummeltypo3@helhum.io
<p>Remove ".php" and replace with ".xlf"</p> TYPO3 Core - Bug #72519 (Closed): Remove class file includeshttp://forge.typo3.org/issues/725192016-01-04T13:13:16ZHelmut Hummeltypo3@helhum.io
<p>The class loader loads the classes.<br />The includes are obsolete and should be just removed.</p> TYPO3 Core - Bug #72265 (Closed): Disclose exceptions on CLI in production contexthttp://forge.typo3.org/issues/722652015-12-16T14:49:28ZHelmut Hummeltypo3@helhum.io
<p>It is pointless to hide the exception message on CLI<br />in the production context. On CLI there are privileged<br />users only anyway and hiding this information from them<br />leads to wasted hours of debugging.</p> TYPO3 Core - Bug #71915 (Closed): Labels are double HTML encoded in ModuleTemplate usagehttp://forge.typo3.org/issues/719152015-11-28T14:48:08ZHelmut Hummeltypo3@helhum.io
<p>Button/ Item properties are correctly html encoded during rendering.<br />However they are also encoded beforehand when setting the values via the API.<br />The latter encoding should be removed.</p> TYPO3 Core - Bug #66798 (Closed): Checking dependencies of extensions causes fatal errorhttp://forge.typo3.org/issues/667982015-05-05T12:08:23ZHelmut Hummeltypo3@helhum.io
<p>Steps to reproduce:</p>
<ul>
<li>realurl is available in the system but not activated</li>
<li>get extensions -> download "seo_basics" (or any other ext that has a dependency to realurl)</li>
</ul>
<p>Expected result: Extension Dependencies are shown before installation</p>
<p>Actual result:<br /><pre>
PHP Fatal error: Call to a member function getVersion() on a non-object in /TYPO3/master/typo3/sysext/extensionmanager/Classes/Controller/DownloadController.php on line 83
</pre></p> TYPO3 Core - Bug #66705 (Closed): Translating pages in page module not possiblehttp://forge.typo3.org/issues/667052015-05-01T16:30:15ZHelmut Hummeltypo3@helhum.io
<p>The FormEngine refactoring broke the overrideVal handling, which is used in several places.</p> TYPO3 Core - Bug #66602 (Closed): Page of type external URL does not redirect to external URL if ...http://forge.typo3.org/issues/666022015-04-27T14:03:18ZHelmut Hummeltypo3@helhum.io
<p>The referrer check in the redirect to external URL feature must be removed.</p>
<p>Use-Case/ Steps to reproduce:</p>
<ul>
<li>A page with content exists and is indexed by Google.</li>
<li>Page is changed to external URL</li>
<li>Google index is not updated yet and points to URL</li>
<li>URL is visited from search result (referrer is google)</li>
</ul>
Expected result:
<ul>
<li>redirect happens</li>
</ul>
Actual result:
<ul>
<li>content of page is shown</li>
</ul> TYPO3 Core - Bug #65434 (Closed): Composer Class Loader does breaks compatiblity if wrong casing ...http://forge.typo3.org/issues/654342015-03-01T15:17:22ZHelmut Hummeltypo3@helhum.io
<p>Steps to reproduce:</p>
<p>Put this code anywhere:</p>
<pre>
interface_exists('typo3\cms\frontend\contentobject\contentobjectstdwraphookinterface');
interface_exists('tslib_content_stdWrapHook');
</pre>
<p>You'll get a fatal error.</p>