TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692022-11-14T17:50:58ZTYPO3 Forge
Redmine TYPO3 Core - Task #99086 (Closed): Add default value for "method" attribute in FormViewHelperhttp://forge.typo3.org/issues/990862022-11-14T17:50:58ZSybille Peterssypets@gmx.de
<p>The default is "post" but this does not show up in the automatically generated ViewHelper reference since default is not set in the initializeArguments method:</p>
<p>$this->registerTagAttribute('method', 'string', 'Transfer type (GET or POST)');</p>
<p>However, the attribute is always set, the default value would be "post".</p>
<ul>
<li><a href="https://docs.typo3.org/other/typo3/view-helper-reference/main/en-us/typo3/fluid/latest/Form.html#method" class="external">Documentation</a></li>
</ul> TYPO3 Core - Feature #94526 (New): Add filter to selectSingle type (TCA)http://forge.typo3.org/issues/945262021-07-10T05:36:46ZSybille Peterssypets@gmx.de
<p>It is possible to filter <strong>selectMultipleSideBySide</strong> .</p>
<p>It is not possible to filter <strong>singleSingle</strong></p>
<a name="Suggestion"></a>
<h2 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h2>
<p>Add configurable option to make single select list filterable. The functionality is already there (see SelectBoxFilter.ts).</p>
<p>If this is then used and the size set to a value > 1, it would make a large number of items in select lists more usable.</p>
<p><img src="http://forge.typo3.org/attachments/download/36166/filterselect.png" alt="" loading="lazy" /></p>
<hr />
<p>Note: As alternative, it is possible to use <strong>selectMultipleSideBySide</strong> with filtering - but if only one element should be selected, the usability is not so great as there is no visual hint that only one should be selected (except that you get feedback once you select too many, but not before) and it is overly complex for the simple purpose of only selecting one element.</p> TYPO3 Core - Bug #92493 (Closed): linkvalidator: scheduler task + list of broken links dies if t...http://forge.typo3.org/issues/924932020-10-06T16:55:55ZSybille Peterssypets@gmx.de
<p>Exception: Prepared statement contains too many placeholders - {"exception":"Doctrine\\DBAL\\Driver\\Mysqli\\MysqliException: Prepared statement contains too many placeholders</p>
<p><strong>Note for reproducing</strong> : You can also reproduce this in the backend in an installation with many pages. You don't have to check broken links at all. Just load the list on a page with many subpages (and "Show this level" "infinite") (to get the "Prepared statement contains too many placeholders" exception).</p>
<p>You should create at least one broken link first and run the check for the page, to make sure displaying the list works correctly.</p>
<a name="Scheduler-task"></a>
<h1 >Scheduler task<a href="#Scheduler-task" class="wiki-anchor">¶</a></h1>
<a name="Reproduce-scheduler-task"></a>
<h2 >Reproduce (scheduler task)<a href="#Reproduce-scheduler-task" class="wiki-anchor">¶</a></h2>
<ol>
<li>site with many pages (I have 40000)</li>
<li>create scheduler task with start page and depth "infinite"</li>
</ol>
<a name="Error-in-scheduler-task"></a>
<h2 >Error in scheduler task<a href="#Error-in-scheduler-task" class="wiki-anchor">¶</a></h2>
<p>In the scheduler task it happens when the (old) number of broken links is calculated (before link checking is performed). Linkvalidator recursively fetches a list of all pages (depending on depth) and then performs a DB query on that</p>
<p>Problem is the way linkvalidator queries. It recursively collects a list of all pages from current page (depending on depth). And then performs a query on it with "WHERE record_pid in (223, 34, etc.).</p>
<p>While this may be efficient (in comparison to several queries) for small sites, it creates a problem for large sites.</p>
<a name="Exception-in-scheduler-task"></a>
<h2 >Exception (in scheduler task)<a href="#Exception-in-scheduler-task" class="wiki-anchor">¶</a></h2>
<pre><code class="text syntaxhl" data-language="text">Prepared statement contains too many placeholders - {"exception":"Doctrine\\DBAL\\Driver\\Mysqli\\MysqliException: Prepared statement contains too many placeholders in /var/www/mysite/htdocs/typo3_src-9.5.22/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/Mysqli/MysqliStatement.php:86
Stack trace:
#0 /var/www/mysite/htdocs/typo3_src-9.5.22/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/Mysqli/MysqliConnection.php(131): Doctrine\\DBAL\\Driver\\Mysqli\\MysqliStatement->__construct(Object(mysqli), 'SELECT `link_ty...')
#1 /var/www/mysite/htdocs/typo3_src-9.5.22/vendor/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(901): Doctrine\\DBAL\\Driver\\Mysqli\\MysqliConnection->prepare('SELECT `link_ty...')
#2 /var/www/mysite/htdocs/typo3_src-9.5.22/vendor/doctrine/dbal/lib/Doctrine/DBAL/Query/QueryBuilder.php(206): Doctrine\\DBAL\\Connection->executeQuery('SELECT `link_ty...', Array, Array)
#3 /var/www/mysite/htdocs/typo3_src-9.5.22/typo3/sysext/core/Classes/Database/Query/QueryBuilder.php(191): Doctrine\\DBAL\\Query\\QueryBuilder->execute()
#4 /var/www/mysite/htdocs/typo3_src-9.5.22/typo3/sysext/linkvalidator/Classes/LinkAnalyzer.php(466): TYPO3\\CMS\\Core\\Database\\Query\\QueryBuilder->execute()
#5 /var/www/mysite/htdocs/typo3_src-9.5.22/typo3/sysext/linkvalidator/Classes/Task/ValidatorTask.php(351): TYPO3\\CMS\\Linkvalidator\\LinkAnalyzer->getLinkCounts(3)
#6 /var/www/mysite/htdocs/typo3_src-9.5.22/typo3/sysext/linkvalidator/Classes/Task/ValidatorTask.php(295): TYPO3\\CMS\\Linkvalidator\\Task\\ValidatorTask->checkPageLinks(3)
#7 /var/www/mysite/htdocs/typo3_src-9.5.22/typo3/sysext/scheduler/Classes/Scheduler.php(179): TYPO3\\CMS\\Linkvalidator\\Task\\ValidatorTask->execute()
#8 /var/www/mysite/htdocs/typo3_src-9.5.22/typo3/sysext/scheduler/Classes/Command/SchedulerCommand.php(145): TYPO3\\CMS\\Scheduler\\Scheduler->executeTask(Object(TYPO3\\CMS\\Linkvalidator\\Task\\ValidatorTask))
#9 /var/www/mysite/htdocs/typo3_src-9.5.22/typo3/sysext/scheduler/Classes/Command/SchedulerCommand.php(99): TYPO3\\CMS\\Scheduler\\Command\\SchedulerCommand->loopTasks()
#10 /var/www/mysite/htdocs/typo3_src-9.5.22/vendor/symfony/console/Command/Command.php(255): TYPO3\\CMS\\Scheduler\\Command\\SchedulerCommand->execute(Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))
#11 /var/www/mysite/htdocs/typo3_src-9.5.22/vendor/symfony/console/Application.php(1001): Symfony\\Component\\Console\\Command\\Command->run(Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))
#12 /var/www/mysite/htdocs/typo3_src-9.5.22/vendor/symfony/console/Application.php(271): Symfony\\Component\\Console\\Application->doRunCommand(Object(TYPO3\\CMS\\Scheduler\\Command\\SchedulerCommand), Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))
#13 /var/www/mysite/htdocs/typo3_src-9.5.22/vendor/symfony/console/Application.php(147): Symfony\\Component\\Console\\Application->doRun(Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))
#14 /var/www/mysite/htdocs/typo3_src-9.5.22/typo3/sysext/core/Classes/Console/CommandRequestHandler.php(63): Symfony\\Component\\Console\\Application->run(Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))
#15 /var/www/mysite/htdocs/typo3_src-9.5.22/typo3/sysext/core/Classes/Console/CommandApplication.php(48): TYPO3\\CMS\\Core\\Console\\CommandRequestHandler->handleRequest(Object(Symfony\\Component\\Console\\Input\\ArgvInput))
#16 /var/www/mysite/htdocs/typo3_src-9.5.22/typo3/sysext/core/bin/typo3(23): TYPO3\\CMS\\Core\\Console\\CommandApplication->run()
#17 /var/www/mysite/htdocs/typo3_src-9.5.22/typo3/sysext/core/bin/typo3(24): {closure}()
#18 {main}
Next Doctrine\\DBAL\\Exception\\DriverException: An exception occurred while executing 'SELECT `link_type`, COUNT(`uid`) AS `nbBrokenLinks` FROM `tx_linkvalidator_link` WHERE ((`record_uid` IN (?,
</code></pre>
<a name="Reproduce-linkvalidator-report"></a>
<h2 >Reproduce (linkvalidator report)<a href="#Reproduce-linkvalidator-report" class="wiki-anchor">¶</a></h2>
<ol>
<li>Site with many pages</li>
<li>In report choose all link types and depth "infinite"</li>
</ol>
<a name="System"></a>
<h2 >System<a href="#System" class="wiki-anchor">¶</a></h2>
<ul>
<li>TYPO3 Version: 9.5.22 - I added some log messages, so the line numbers may not be correct</li>
<li>40000 pages (not hidden and not deleted)</li>
</ul> TYPO3 Core - Bug #92286 (Closed): ?ADMCMD_simUser= not automatically appended to URL for child pa...http://forge.typo3.org/issues/922862020-09-11T11:12:40ZSybille Peterssypets@gmx.de
<p>?ADMCMD_simUser=<usergroup> is not automatically appended if page is child of page with FE group and <strong>extendToSubpage</strong> is set for parent.</p>
<pre><code class="text syntaxhl" data-language="text">- parent (FE group + extendToSubpages
|
-> child
</code></pre>
<p>If the parent page is loaded in frontend with view button, ?ADMCMD_simUser= is automatically appended.</p>
<p>I also noticed that in the 403 PageErrorHandler, the $reason['code'] is different in this case:</p>
<ul>
<li>for "parent": "access.page" </li>
<li>for "child": "access.subsection"</li>
</ul> TYPO3 Core - Bug #92033 (Closed): "Page tree error: Got unexpected reponse" with filter - allowed...http://forge.typo3.org/issues/920332020-08-17T15:26:42ZSybille Peterssypets@gmx.de
<a name="Related-to"></a>
<h2 >Related to<a href="#Related-to" class="wiki-anchor">¶</a></h2>
<p>This was first noticed when testing <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/65208">https://review.typo3.org/c/Packages/TYPO3.CMS/+/65208</a></p>
<a name="Reproduce"></a>
<h2 >Reproduce<a href="#Reproduce" class="wiki-anchor">¶</a></h2>
<p>I used current master with my pages table from production (with about 40000 pages). To reproduce this error, I think it is necessary for the queries to take a while so that you get an overlap between the consecutive queries (for 1, 12 and 123) when using the filter.</p>
<ol>
<li>Use the filter to filter for a specific page e.g. 8466 and select it</li>
<li>Clear filter and then press 1 then 2 and 3 with a little delay in between for the query to get invoked but not enough for the query to be finished. (this will invoke filter with '1', '12' and '123'.</li>
</ol>
<a name="Result"></a>
<h2 >Result<a href="#Result" class="wiki-anchor">¶</a></h2>
<p>an error is displayed as flash message:</p>
<blockquote>
<p>Page tree error<br />Got unexpected response from the server. Please check logs for details.</p>
</blockquote>
<p>In the Browser console:</p>
<pre><code class="text syntaxhl" data-language="text">Uncaught SyntaxError: Unexpected token < in JSON at position 0
at JSON.parse (<anonymous>)
at Object.<anonymous> (d3.js?bust=28c4bb4fe3488f05a0e2eacad6f401e00a588ba9:8)
at XMLHttpRequest.c (d3.js?bust=28c4bb4fe3488f05a0e2eacad6f401e00a588ba9:6)
(anonymous) @ d3.js?bust=28c4bb4fe3488f05a0e2eacad6f401e00a588ba9:8
c @ d3.js?bust=28c4bb4fe3488f05a0e2eacad6f401e00a588ba9:6
load (async)
Xk @ d3.js?bust=28c4bb4fe3488f05a0e2eacad6f401e00a588ba9:6
(anonymous) @ d3.js?bust=28c4bb4fe3488f05a0e2eacad6f401e00a588ba9:6
PageTree.filterTree @ PageTree.js?bust=28c4bb4fe3488f05a0e2eacad6f401e00a588ba9:458
PageTree.refreshOrFilterTree @ PageTree.js?bust=28c4bb4fe3488f05a0e2eacad6f401e00a588ba9:488
TreeToolbar.search @ PageTreeToolbar.js?bust=28c4bb4fe3488f05a0e2eacad6f401e00a588ba9:232
(anonymous) @ PageTreeToolbar.js?bust=28c4bb4fe3488f05a0e2eacad6f401e00a588ba9:205
setTimeout @ DebounceEvent.js?bust=28c4bb4fe3488f05a0e2eacad6f401e00a588ba9:13
setTimeout (async)
(anonymous) @ DebounceEvent.js?bust=28c4bb4fe3488f05a0e2eacad6f401e00a588ba9:13
</code></pre>
<p>PageTree.js 472</p> TYPO3 Core - Task #90848 (Accepted): No longer possible to enter several pids in linkvalidator sc...http://forge.typo3.org/issues/908482020-03-27T07:07:13ZSybille Peterssypets@gmx.de
<p>TYPO3 10,9,8 ...</p>
<p>I am not sure when this was changed:</p>
<p>In the scheduler task for linkvalidator it is no longer possible to enter several page ids in "Start page (uid)"</p>
<p>This used to be possible which was very helpful if you had several sites. In that case, you would get an aggregated report in the mail with information per site.</p>
<p>Also, you could exclude inactive sites this way. Now you can only enter startpage of one site or 0. (Of course, you can always enter several scheduler tasks).</p>
<p>In some cases, sites that are being updated will most likely have problems and need to change this. (Not sure if the old behaviour will still work with several pids).</p>
<p><img src="http://forge.typo3.org/attachments/download/35011/linkvalidator_scheduler.png" alt="" loading="lazy" /></p>
<p>Anyhow, it is no longer possible to enter several pids, separated by comma, which used to be possible.</p>
<p>(I would actually prefer an option to determine this automatically, based on sites configuration)</p> TYPO3 Core - Bug #90352 (Closed): Fix changelog: "Use new Translation Server"http://forge.typo3.org/issues/903522020-02-11T10:05:22ZSybille Peterssypets@gmx.de
<p>The changelog "Use new Translation Server" has a title indicating it is a feature,<br />but has a filename starting with "Important".</p> TYPO3 Core - Task #89993 (Closed): Add documentation about difference between ViewHelpers be.cont...http://forge.typo3.org/issues/899932019-12-19T07:09:32ZSybille Peterssypets@gmx.de
<p>The description for both is pretty much the same.</p>
<p>The examples look very similar too. I honestly don't know what be.pageRenderer is for in comparison to be.container.</p>
<hr />
<ul>
<li><a href="https://docs.typo3.org/other/typo3/view-helper-reference/master/en-us/typo3/fluid/latest/Be/PageRenderer.html" class="external">be.pageRenderer</a></li>
</ul>
<pre>
be.pageRenderer
ViewHelper which allows you to create extbase based modules in the style of TYPO3 default modules.
Examples
All options:
<f:be.pageRenderer pageTitle="foo"
includeCssFiles="{0: '{f:uri.resource(path:\'Css/Styles.css\')}'}"
includeJsFiles="{0: '{f:uri.resource(path:\'JavaScript/Library1.js\')}', 1: '{f:uri.resource(path:\'JavaScript/Library2.js\')}'}"
addJsInlineLabels="{0: 'label1', 1: 'label2'}" />
Custom CSS file EXT:your_extension/Resources/Public/Css/styles.css and JavaScript files EXT:your_extension/Resources/Public/JavaScript/Library1.js and EXT:your_extension/Resources/Public/JavaScript/Library2.js will be loaded, plus some inline labels for usage in JS code.
</pre>
<ul>
<li><a href="https://docs.typo3.org/other/typo3/view-helper-reference/master/en-us/typo3/fluid/latest/Be/Container.html" class="external">be.container</a></li>
</ul>
<pre>
be.container
ViewHelper which allows you to create extbase based modules in the style of TYPO3 default modules.
Examples
Simple:
<f:be.container>your module content</f:be.container>
“your module content” wrapped with proper head & body tags. Default backend CSS styles and JavaScript will be included.
All options:
<f:be.container pageTitle="foo"
includeCssFiles="{0: '{f:uri.resource(path:\'Css/Styles.css\')}'}"
includeJsFiles="{0: '{f:uri.resource(path:\'JavaScript/Library1.js\')}', 1: '{f:uri.resource(path:\'JavaScript/Library2.js\')}'}"
addJsInlineLabels="{0: 'label1', 1: 'label2'}"
>
your module content
</f:be.container>
“your module content” wrapped with proper head & body tags. Custom CSS file EXT:your_extension/Resources/Public/Css/styles.css and JavaScript files EXT:your_extension/Resources/Public/JavaScript/Library1.js and EXT:your_extension/Resources/Public/JavaScript/Library2.js will be loaded, plus some inline labels for usage in JS code.
</pre> TYPO3 Core - Feature #89322 (Closed): Add a distributed locking strategy based on Redishttp://forge.typo3.org/issues/893222019-10-01T15:16:18ZSybille Peterssypets@gmx.de
<p>Currently, it is not possible to use TYPO3 in a cluster for high availability / load-balancing if default lock strategy based on flock fails on NFS file system (see <a class="issue tracker-1 status-1 priority-3 priority-lowest" title="Bug: FileLockStrategy fails on NFS folders (New)" href="http://forge.typo3.org/issues/72074">#72074</a>).</p> TYPO3 Core - Bug #89240 (Closed): "Edit page properties" icon is displayed, even if page editing ...http://forge.typo3.org/issues/892402019-09-24T10:50:35ZSybille Peterssypets@gmx.de
<a name="Reproduce"></a>
<h2 >Reproduce<a href="#Reproduce" class="wiki-anchor">¶</a></h2>
<ol>
<li>Create a user / group which does not have access to editing pages (pages not set in tables_modify)</li>
<li>Switch to this user</li>
<li>Select page</li>
<li>Click on "Edit page properties"</li>
</ol>
<p>Empty form appears. Also a reload animation is shown and does not end.</p>
<p><img src="http://forge.typo3.org/attachments/download/34571/edit.png" alt="" loading="lazy" /></p>
<a name="System"></a>
<h2 >System<a href="#System" class="wiki-anchor">¶</a></h2>
<p>Used current TYPO3 master (10.1.0-dev).</p> TYPO3 Core - Task #88223 (Closed): Add description for returnUrl in EditRecordViewHelper.phphttp://forge.typo3.org/issues/882232019-04-26T13:06:43ZSybille Peterssypets@gmx.de
<pre><code class="php syntaxhl" data-language="php"><span class="nv">$this</span><span class="o">-></span><span class="nf">registerArgument</span><span class="p">(</span><span class="s1">'returnUrl'</span><span class="p">,</span> <span class="s1">'string'</span><span class="p">,</span> <span class="s1">''</span><span class="p">,</span> <span class="kc">false</span><span class="p">,</span> <span class="s1">''</span><span class="p">);</span>
</code></pre> TYPO3 Core - Task #87135 (Closed): Add 9.5.x to ChangeLoghttp://forge.typo3.org/issues/871352018-12-12T19:16:45ZSybille Peterssypets@gmx.deTYPO3 Core - Feature #76895 (Rejected): Add [FE][lockSSL] option in TYPO3_CONF_VARS (as in [BE][l...http://forge.typo3.org/issues/768952016-06-30T17:12:06ZSybille Peterssypets@gmx.de
<p>Proposal to add an option to enforce HTTPS if currently logged in as FE user. Could be implemented as in already existing [BE][lockSSL] option.</p>
<p>This would make Extensions like https_enforcer more or less redundant, because TYPO3 core would handle this functionality:</p>
<p>1) already existing in core: Force HTTPS for specific page (pages.url_scheme)<br />2) already existing in core: Force HTTPS if logged in as BE-User: [BE][lockSSL]<br />2) not exisiting? : Force HTTPS if logged in as FE-User</p> TYPO3 Core - Bug #66793 (Closed): "simulate time" in admin-panel does not respect timezonehttp://forge.typo3.org/issues/667932015-05-05T09:54:27ZSybille Peterssypets@gmx.de
<p>The entered time in the text field "simulate time" is evaluated as UTC / GMT even though a different timezone is set on client + server machine (CEST / "Europe/Berlin").</p>
<p>This problem exists in 4.5.40 and 6.2.12.</p>
<a name="More-info"></a>
<h1 >More info:<a href="#More-info" class="wiki-anchor">¶</a></h1>
<p>php.ini:<br /><pre><code class="php syntaxhl" data-language="php"><span class="n">date</span><span class="mf">.</span><span class="n">timezone</span> <span class="o">=</span> <span class="s2">"Europe/Berlin"</span>
</code></pre></p>
<p>System timezone: CEST</p>
<p>LocalConfiguration.php:</p>
<pre><code class="php syntaxhl" data-language="php"><span class="s1">'phpTimeZone'</span> <span class="o">=></span> <span class="s1">'Europe/Berlin'</span><span class="p">,</span>
<span class="s1">'serverTimeZone'</span> <span class="o">=></span> <span class="s1">'2'</span><span class="p">,</span>
</code></pre>
<a name="reproduce"></a>
<h1 >reproduce<a href="#reproduce" class="wiki-anchor">¶</a></h1>
<ol>
<li>Set allowed time from 9:00 to 10:00 for a page (e.g. 9:00 5-5-2015)</li>
<li>Enter 7:18 in "simulate time" in admin panel</li>
</ol>
<a name="Result"></a>
<h1 >Result<a href="#Result" class="wiki-anchor">¶</a></h1>
<p>Allowed content (9:00 to 10:00) is displayed for entered time of 7:18 > not correct</p>
<a name="conclusion"></a>
<h1 >conclusion:<a href="#conclusion" class="wiki-anchor">¶</a></h1>
<p>"simulate time" in admin-panel is evaluated as UTC (it does not use current timezone)</p>
<a name="Test"></a>
<h1 >Test<a href="#Test" class="wiki-anchor">¶</a></h1>
<p>entered time for content: 6:00 - 9:00</p>
<p>entered time in "simulate time" in admin panel:</p>
<p>3:00 : content not visible<br />4:00 : content visisble<br />5:00 : content visible<br />6:00 : content visible<br />6:59 : content visisble<br />7:00 : content not visisble</p>
<p>+2 hours offset</p> TYPO3 Core - Bug #51360 (Closed): Linkvalidator: specifying TSconfig in scheduler has no effecthttp://forge.typo3.org/issues/513602013-08-26T17:22:37ZSybille Peterssypets@gmx.de
<p>It is possible to set for example subject and content type via page TSconfig. This works fine. However, setting TSconfig in linkvalidator task in scheduler has no effect.</p>
<p>Using version TYPO3 4.5.29</p>