TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-02-11T13:18:51ZTYPO3 Forge
Redmine TYPO3 Core - Bug #103100 (Resolved): "Refresh display" or "Check links" button is entirely disabl...http://forge.typo3.org/issues/1031002024-02-11T13:18:51ZSybille Peterssypets@gmx.de
<p>By default, the buttons in "Report" and "Check links" module are disabled. They are enabled via JavaScript if a check option is enabled.</p>
<p>However, in TYPO3 v13 (and possibly below), this does not work correctly: if all options are unchecked (which is the default for new users) and then one of them is toggled (to enabled), it is still not possible to click the button at all, it remains disabled even if options are being checked. It looks like the event listener is not being called.</p>
<a name="Reproduce"></a>
<h2 >Reproduce<a href="#Reproduce" class="wiki-anchor">¶</a></h2>
<p>1. switch to a new user where the options have not been enabled yet<br />2. Either in the "Report" or "Check links" view, enable one of the checkboxes for the link types<br />3. Try to click the button</p>
<p>Result: nothing happens, the button is disabled, so it is not possible to execute the new selection.</p>
<a name="Versions"></a>
<h2 >Versions<a href="#Versions" class="wiki-anchor">¶</a></h2>
<p>Could be reproduced in TYPO3 v13 (main).</p>
<p>Could NOT be reproduce din TYPO3 v12.</p>
<a name="Screenshot"></a>
<h2 >Screenshot<a href="#Screenshot" class="wiki-anchor">¶</a></h2>
<p><img src="http://forge.typo3.org/attachments/download/38255/linkvalidator_checkboxes.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #101414 (Resolved): Alert dialog does not show information about references inli...http://forge.typo3.org/issues/1014142023-07-22T13:09:23ZSybille Peterssypets@gmx.de
<p>This issue handles only one specific case which was already patched in v12 and v13.</p>
<p>More information is in <a class="issue tracker-1 status-1 priority-4 priority-default" title="Bug: Message that there are references which point to this record is not always displayed when trying ... (New)" href="http://forge.typo3.org/issues/101411">#101411</a></p>
<p>Hopefully part of the improvements in <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/72001">https://review.typo3.org/c/Packages/TYPO3.CMS/+/72001</a> can be backported to v11.</p>
<a name="Reproduce"></a>
<h2 >Reproduce<a href="#Reproduce" class="wiki-anchor">¶</a></h2>
<p>1. Create a record [1] (e.g. texmedia), create a shortcut ce [2] which references this<br />2. In page module try to delete the record [1] (using the inline delete button).</p>
<p>We see a generic delete msg. We expect delete msg which warns about references.</p>
<a name="Screenshot"></a>
<h2 >Screenshot<a href="#Screenshot" class="wiki-anchor">¶</a></h2>
<p><img src="http://forge.typo3.org/attachments/download/37847/delete_record_with_references_generic_message.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #99767 (New): Allowed file types are not displayed with type="input", renderType...http://forge.typo3.org/issues/997672023-01-31T10:32:50ZSybille Peterssypets@gmx.de
<p>This used to be the case with type="inline". Here, the allowed file types were displayed in the form and in the link browser.</p>
<a name="Reproduce"></a>
<h2 >Reproduce<a href="#Reproduce" class="wiki-anchor">¶</a></h2>
<p>There is an example extension available to reproduce, was tested with v12 latest main:</p>
<p><a class="external" href="https://github.com/sypets/sypets_example_inputlink">https://github.com/sypets/sypets_example_inputlink</a></p>
<p>1. in Backend insert a plugin using the "Content element wizard" in tab plugins "InputLink plugin" <br />2. check out the fields in "plugin" tab and compare the behaviour of various types<br />3. Look at flexform file</p>
<a name="Screenshot"></a>
<h2 >Screenshot<a href="#Screenshot" class="wiki-anchor">¶</a></h2>
<p><img src="http://forge.typo3.org/attachments/download/37361/Screenshot_show_allowed_file_extensions.png" alt="" loading="lazy" /></p>
<p>in type="file" the allowed file extensions are displayed (as previously in "inline") in type="link" and renderType="linkType" not.</p>
<a name="Versions"></a>
<h2 >Versions<a href="#Versions" class="wiki-anchor">¶</a></h2>
<ul>
<li>used latest v11 (11.5.22)</li>
<li>this can also be reproduced with v12, with type="link"</li>
</ul>
<a name="Example"></a>
<h2 >Example<a href="#Example" class="wiki-anchor">¶</a></h2>
<pre><code class="xml syntaxhl" data-language="xml"><span class="nt"><settings.link></span>
<span class="nt"><TCEforms></span>
<span class="nt"><label></span>Link<span class="nt"></label></span>
<span class="nt"><config></span>
<span class="nt"><type></span>input<span class="nt"></type></span>
<span class="nt"><renderType></span>inputLink<span class="nt"></renderType></span>
<span class="nt"><fieldControl></span>
<span class="nt"><linkPopup></span>
<span class="nt"><options></span>
<span class="nt"><allowedExtensions></span>bib<span class="nt"></allowedExtensions></span>
<span class="nt"><blindLinkFields></span>class,param,target,title<span class="nt"></blindLinkFields></span>
<span class="nt"><blindLinkOptions></span>page,mail,telephone,folder,tx_calendarize_domain_model_event,news<span class="nt"></blindLinkOptions></span>
<span class="nt"><title></span>Select specific file (*.bib)<span class="nt"></title></span>
<span class="nt"></options></span>
<span class="nt"></linkPopup></span>
<span class="nt"></fieldControl></span>
<span class="nt"></config></span>
<span class="nt"></TCEforms></span>
<span class="nt"></settings.link></span>
</code></pre>
<p>Documentation</p>
<ul>
<li>v11: inputLink: <a class="external" href="https://docs.typo3.org/m/typo3/reference-tca/11.5/en-us/ColumnsConfig/Type/Input/Link/Index.html#columns-input-rendertype-inputlink">https://docs.typo3.org/m/typo3/reference-tca/11.5/en-us/ColumnsConfig/Type/Input/Link/Index.html#columns-input-rendertype-inputlink</a></li>
<li>v12: inputLink was deprecated, type="link" should be used: <a class="external" href="https://docs.typo3.org/m/typo3/reference-tca/main/en-us/ColumnsConfig/Type/Link/Index.html#columns-link">https://docs.typo3.org/m/typo3/reference-tca/main/en-us/ColumnsConfig/Type/Link/Index.html#columns-link</a></li>
</ul> TYPO3 Core - Bug #99476 (Rejected): Add getRequest to RenderingContextInterface? (>= v11)http://forge.typo3.org/issues/994762023-01-06T09:55:07ZSybille Peterssypets@gmx.de
<p>RenderingContextInterface does not contain getRequest().</p>
<p>If extending from AbstractViewHelper and using renderStatic, the function looks like this:</p>
<pre><code class="php syntaxhl" data-language="php"><span class="k">public</span> <span class="k">static</span> <span class="k">function</span> <span class="n">renderStatic</span><span class="p">(</span><span class="kt">array</span> <span class="nv">$arguments</span><span class="p">,</span> <span class="nc">\Closure</span> <span class="nv">$renderChildrenClosure</span><span class="p">,</span> <span class="nc">RenderingContextInterface</span> <span class="nv">$renderingContext</span><span class="p">)</span>
<span class="p">{</span>
</code></pre>
<p>It should be possible to call $renderingContext->getRequest(), but then checks with phpstan will fail and you would have to check for the class name of the object (which should not really be necessary.</p>
<p>(Previously, it was possible to call $renderingContext->getControllerContext()->getRequest()).</p> TYPO3 Core - Bug #94595 (Closed): Adminpanel does not update texts if preferred language for BE i...http://forge.typo3.org/issues/945952021-07-20T09:06:54ZSybille Peterssypets@gmx.de
<p>Or, how to change language for adminpanel? I assumed I change the language by changing my language setting as BE user, but it does not work.</p>
<p>Did not find this information in the docs: <a class="external" href="https://docs.typo3.org/c/typo3/cms-adminpanel/master/en-us/Settings/Index.html">https://docs.typo3.org/c/typo3/cms-adminpanel/master/en-us/Settings/Index.html</a></p>
<a name="Reproduce"></a>
<h2 >Reproduce:<a href="#Reproduce" class="wiki-anchor">¶</a></h2>
<p>1. Open page in frontend<br />2. Activate adminpanel<br />3. Change preferred language in backend<br />4. Click on eye (to view) again, deactivate, activate adminpanel, reload page, reload with hard refresh (CTRL-F5) in FE and BE.</p>
<p>Nothing seems to work to change the language. Even if a different page is loaded. Or if I start a different browser and login.</p>
<p>I switched from German to English. I still see texts in Adminpanel in German.</p>
<p><img src="http://forge.typo3.org/attachments/download/36185/adminpanel1.png" alt="" loading="lazy" /></p>
<p><img src="http://forge.typo3.org/attachments/download/36186/adminpanel2.png" alt="" loading="lazy" /></p>
<p>The texts in the BE are in English.</p>
<p><img src="http://forge.typo3.org/attachments/download/36187/backend.png" alt="" loading="lazy" /></p>
<a name="Analysis"></a>
<h2 >Analysis<a href="#Analysis" class="wiki-anchor">¶</a></h2>
<p>currently, I am not sure, how to change the language. Does it used my preferred settings? Does the language in the BE affect it at all?</p>
<p>My preferred language is <strong>en-us</strong> . If I execute this JavaScript in my browser, I get "en-US":</p>
<pre><code class="javascript syntaxhl" data-language="javascript"><span class="p">(</span><span class="kd">function</span><span class="p">()</span> <span class="p">{</span>
<span class="c1">// your page initialization code here</span>
<span class="c1">// the DOM will be available here</span>
<span class="nx">console</span><span class="p">.</span><span class="nf">log</span><span class="p">(</span> <span class="dl">"</span><span class="s2">language =</span><span class="dl">"</span> <span class="o">+</span> <span class="nb">navigator</span><span class="p">.</span><span class="nx">language</span><span class="p">);</span>
<span class="p">})();</span>
</code></pre>
<a name="Versions"></a>
<h2 >Versions<a href="#Versions" class="wiki-anchor">¶</a></h2>
<ul>
<li>TYPO3 version 10.4.17</li>
<li>browser: Chromium (Version 91.0.4472.114), Chrome (70.0.3538.77) and Firefox (90.0)</li>
</ul> TYPO3 Core - Bug #93912 (New): Avoid horizontal scrollbar for redirects modulehttp://forge.typo3.org/issues/939122021-04-13T08:48:19ZSybille Peterssypets@gmx.de
<p>If some URL targets are long, a horizontal scrollbar is displayed. This makes the action button invisible and you have to scroll down.</p>
<p>I think this is not very good from a usability point of view - it actually hides the action buttons.</p>
<p>We had the same problem in the linkvalidator list and switched to a fixed layout (where each column has a fixed width).</p>
<p>Another (better?) alternative would be to shorten both source and targets paths if they exceed a certain length.</p>
<a name="System"></a>
<h2 >System<a href="#System" class="wiki-anchor">¶</a></h2>
<ul>
<li>master (11-dev)</li>
<li>10.4.14</li>
</ul>
<p><img src="http://forge.typo3.org/attachments/download/36001/redirects1.png" alt="" loading="lazy" /></p>
<p><img src="http://forge.typo3.org/attachments/download/36002/redirects2.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #93287 (Closed): Avoid creation of unnecessary redirects on Slug changeshttp://forge.typo3.org/issues/932872021-01-14T07:50:39ZSybille Peterssypets@gmx.de
<p>If you create a new page, you can automatically add the page title in the pagetree. But often this does not work, so you end up having to change it again. Also, the URL created directly from the page title may not be the best choice, so you end up changing this again.</p>
<p>For every URL change, a redirect is now created (in sys_redirect).</p>
<p><strong>If the page is very new, I think a redirect is unnecessary. Also, if the page is hidden, a redirect is unnecessary.</strong></p>
<p>Many redirects degrades performance (see <a class="issue tracker-4 status-8 priority-4 priority-default" title="Task: Redirects: Poor performance of redirect matching for large redirects table (Under Review)" href="http://forge.typo3.org/issues/90143">#90143</a>). Also, many automatically created redirects make managing of manual redirects more difficult.<br />And, if you change it back and forth (which may happen over time), you get a redirect loop. Which results in an unusable page.</p>
<p>Another reason: The editor is presented with 3 choices: Go with the change, revert the change, revert the redirect. This is cognitive overload, especially for a new editor. So preventing this for new pages may also make TYPO3 a little more easily usable, especially at the beginning when you are creating new pages.</p>
<p>... so I think it is a good strategy to create as little redirects as possible.</p>
<p>I think you could avoid this, by</p>
<p>- not creating redirects for redirects from or to <em>"default-title"</em> (or whatever the default title is set to)<br />- not creating redirects for changed slugs if the page is hidden (or in another way not available)<br />- not creating redirects for very new pages<br />- and merging redirect chains (<a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Merge redirect chains (Closed)" href="http://forge.typo3.org/issues/93288">#93288</a>) and avoid redirect loops (<a class="issue tracker-4 status-2 priority-4 priority-default" title="Task: Streamline automatic slug & redirects handling (Accepted)" href="http://forge.typo3.org/issues/89301">#89301</a>) (but that is a separate issue)</p>
<a name="Reproduce-creating-unnecessary-redirects"></a>
<h2 >Reproduce (creating unnecessary redirects)<a href="#Reproduce-creating-unnecessary-redirects" class="wiki-anchor">¶</a></h2>
<p>1. Create a new page using the default title (hidden)<br />2. change the slug (still hidden)</p>
<p>etc.</p>
<p>You will now have a redirect for the page. You can check in sys_redirect table.</p>
<p>Here an example, after changing /test-1/urls/default-title and doing this again for a hidden subpage.</p>
<pre>
select uid,FROM_UNIXTIME(createdon),source_path,target from sys_redirect where source_path like '/test-1/urls%' order by uid limit 5;
+-----+--------------------------+------------------------------------+---------------------------------+
| uid | FROM_UNIXTIME(createdon) | source_path | target |
+-----+--------------------------+------------------------------------+---------------------------------+
| 12 | 2021-01-14 08:28:31 | /test-1/urls/default-title | /test-1/urls/subpage |
| 13 | 2021-01-14 08:36:28 | /test-1/urls/subpage/default-title | /test-1/urls/subpage/subsubpage |
</pre><br /><ins><del>---</del></ins>--------------------------+------------------------------------+---------------------------------+ 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 - Bug #90824 (Closed): Add media file - too many options? Confusing ...http://forge.typo3.org/issues/908242020-03-24T20:40:26ZSybille Peterssypets@gmx.de
<p>For example in the "textmedia" element "media" tab I have 5 options:</p>
<ol>
<li>Add media file</li>
<li>Select & upload files</li>
<li>Add media by URL</li>
<li>Drag and drop to upload files</li>
<li>or "click, browse and choose files"</li>
</ol>
<p>While it is cool that you can do several things, there is some overlap.</p>
<p><img src="http://forge.typo3.org/attachments/download/34997/media.png" alt="" loading="lazy" /></p>
<p>Option 1 is kind of a mega-dialog where you can also upload files and also use an URL. Why have 2 and 3 if you can already do that in 1?</p>
<p>Option 5 is basically the same as 2.</p>
<p>There may be a reason for doing it this way but it is not immediately intuitively understandable for me.</p>
<p>Once you do click on one of the options, the workflow is pretty simple.</p>
<p>Also the phrasing:</p>
<ul>
<li>in option 1 it is "upload <em>media file</em>" </li>
<li>in option 2 it is just "select & upload <em>files</em>"</li>
</ul>
<p>In all these cases it is a media file, so I would always use "media file" or just "file". Otherwise you look at the buttons and wonder what is the difference.</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 - 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 - Bug #84987 (Closed): Add css style for broken page links in ckeditorhttp://forge.typo3.org/issues/849872018-05-12T20:38:10ZSybille Peterssypets@gmx.de
<p>With the old rtehtmlarea broken links (at least page links which linked to not existing page) where displayed differently with a red border and yellow background. This is no longer working with ckeditor.</p>
<p><img src="http://forge.typo3.org/attachments/download/33441/links.png" alt="" loading="lazy" /></p>
<p>The broken links are apparently already marked with an additional attribute (see RteHtmlParser::markBrokenLinks):</p>
<pre><code class="html syntaxhl" data-language="html"><span class="nt"><a</span> <span class="na">data-rte-error= </span><span class="s">...</span>
</code></pre>
<p>If CSS for <a> elements with this attribute are added in the rte_ckeditor, the broken links could be visually displayed as broken links.</p>
<p>The style ('background-color: yellow; border:2px red solid; color: black;') that is added in RteHtmlParser::markBrokenLinks is probably removed by ckeditor.</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>