TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-12-06T10:10:08ZTYPO3 Forge
Redmine TYPO3 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 - 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 - Task #95849 (Closed): Normalize JavaScript initialization of workspaces previewhttp://forge.typo3.org/issues/958492021-11-02T12:58:06ZOliver Haderoliver.hader@typo3.org
<p>Ensures workspaces PreviewController uses dedicated method to declare client-side settings PageRenderer::addInlineSetting(). This is a preparation to reduce the amount of inline JavaScript later.</p> TYPO3 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 #91166 (Closed): Add 10.4.x Changelog sectionhttp://forge.typo3.org/issues/911662020-04-22T09:26:54ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Task #89743 (Closed): Add additional tests for Route VariableProcessorhttp://forge.typo3.org/issues/897432019-11-22T16:03:07ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Task #89623 (Closed): Add additional workspaces tests covering enable fieldshttp://forge.typo3.org/issues/896232019-11-08T17:38:52ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Bug #80141 (Closed): Add allowLanguageSynchronization chain resolvinghttp://forge.typo3.org/issues/801412017-03-04T20:18:32ZOliver Haderoliver.hader@typo3.org
<p>Currently the localization behavior does not consider localization chains concerning field values to be synchronized over multiple localization hops that use the relative l10n_state "source".</p>
Imagine the following scenario of content element:
<ul>
<li>[uid:10, sys_language_uid:0, l18n_parent:0, l10n_source:0, header:Value]</li>
<li>[uid:11, sys_language_uid:1, l18n_parent:10, l10n_source:10, header:Value, l10n_state:{header:parent}]</li>
<li>[uid:12, sys_language_uid:2, l18n_parent:10, l10n_source:11, header:Value, l10n_state:{header:source}]</li>
</ul>
<p>Now if the record of the default record (uid:10) will be updated and the header value set to "Modified", only direct dependents would be synchronized. The automated update of the direct-child localization record (uid:11) does not trigger another update for the grand-child localization (uid:12). To achieve this, the data-map processor has been extended to collect new modifications to the data-map caused by synchronization processes - as long as modifications could be determined, another synchronization round is triggered for the modified items. This way the localization chain is completely synchronized if required, depending on the according l10n_state settings.</p> TYPO3 Core - Bug #72846 (Closed): Absolute URIs get prefixed with absRefPrefix in typolink proces...http://forge.typo3.org/issues/728462016-01-20T18:52:30ZOliver Haderoliver.hader@typo3.org
<p>An absolute URI (e.g. "/folder/someFile.png") get's prefixed with absRefPrefix (e.g. "/") which results in "//folder/someFile.png" - which is a schema-less URI notation and thus "folder" is interpreted as hostname.</p> TYPO3 Core - Task #59898 (Closed): Add action selector in toolbar in workspaces menuhttp://forge.typo3.org/issues/598982014-06-26T11:41:11ZOliver Haderoliver.hader@typo3.org
<p>Currently there are two selectors in the bottom toolbar of the workspace module. One to handle stage changes on selected elements and one for mass actions (publish, swap, discard) for the whole workspace. To circumvent this, an additional selector shall be added for record selections.</p> TYPO3 Core - Bug #52825 (Closed): \TYPO3\CMS\Extbase\Object\ObjectManagerException vs of \TYPO3\C...http://forge.typo3.org/issues/528252013-10-14T23:51:53ZOliver Haderoliver.hader@typo3.org
<p>\TYPO3\CMS\Extbase\Object\ObjectManagerException is basically the same as the ObjectManager.<br />\TYPO3\CMS\Extbase\Object\ObjectManagerException has been introduced in this change:<br /><a class="external" href="https://git.typo3.org/TYPO3v4/CoreProjects/MVC/extbase.git/commit/569063f64331766ea780cd118f0fd6c707664c16">https://git.typo3.org/TYPO3v4/CoreProjects/MVC/extbase.git/commit/569063f64331766ea780cd118f0fd6c707664c16</a></p>
<p>Update:<br />Link to commit that introduced this change: <a class="external" href="https://git.typo3.org/TYPO3CMS/CoreProjects/MVC/extbase.git/commit/569063f64331766ea780cd118f0fd6c707664c16">https://git.typo3.org/TYPO3CMS/CoreProjects/MVC/extbase.git/commit/569063f64331766ea780cd118f0fd6c707664c16</a></p> TYPO3 Core - Bug #43139 (Closed): Activating NULL value field does not work with blank stringhttp://forge.typo3.org/issues/431392012-11-20T11:07:28ZOliver Haderoliver.hader@typo3.org
<p>Activating a field that supports NULL values and just using a blank string ("") does not work.<br />The problem is a strcmp() call that returns a false-positive on comparing NULL to blank strings.</p> TYPO3 Core - Bug #27976 (Closed): A cache with identifier "workspaces_cache" does not existhttp://forge.typo3.org/issues/279762011-07-08T10:41:58ZOliver Haderoliver.hader@typo3.org
<p>The following exception is thrown on e.g. creating a new localized version of a page in the live workspace:</p>
<pre>#1203699034: A cache with identifier "workspaces_cache" does not exist. (More information)
t3lib_cache_exception_NoSuchCache thrown in file
/Users/olly/Development/typo3/master/t3lib/cache/class.t3lib_cache_manager.php in line 132.</pre> TYPO3 Core - Bug #11163 (Closed): Actions performed on tabs are not executed on the correct works...http://forge.typo3.org/issues/111632010-11-30T14:00:43ZOliver Haderoliver.hader@typo3.org
<p>Actions performed on tabs are not executed on the correct workspace</p>