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 - Task #99772 (Closed): Deprecate TCA renderType="inputLink" at some pointhttp://forge.typo3.org/issues/997722023-01-31T14:09:48ZSybille Peterssypets@gmx.de
<p>The type="input", renderType="inputLink" was replaced in TYPO3 v12 with type="link", however the inputLink still works. At some point it can be deprecated and removed.</p>
<p>typo3/sysext/backend/Migrations/Code/ClassAliasMap.php:</p>
<pre><code class="php syntaxhl" data-language="php"><span class="k">return</span> <span class="p">[</span>
<span class="s1">'TYPO3\\CMS\\Backend\\Form\\Element\\InputLinkElement'</span> <span class="o">=></span> <span class="nc">\TYPO3\CMS\Backend\Form\Element\LinkElement</span><span class="o">::</span><span class="n">class</span><span class="p">,</span>
</code></pre> TYPO3 Core - Task #93428 (Closed): Rename function getHeaderFlashMessagesForCurrentPid() in PageL...http://forge.typo3.org/issues/934282021-02-04T07:54:53ZSybille Peterssypets@gmx.de
<p>see explanation in</p>
<blockquote>
<p>- flash messages: those are normally shown after an action, e.g saving something was succesful<br />- callouts: give the user permanent feedback</p>
</blockquote>
<p><a class="external" href="https://forge.typo3.org/issues/93422#note-2">https://forge.typo3.org/issues/93422#note-2</a></p>
<p>Could be renamed to getCalloutsForCurrentPid().</p>
<p>Since PageLayoutController is non-internal I assume this is a breaking change, so cannot be done until v12.</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 #91904 (Accepted): Unify naming of "Install tool" vs "Admin Tool" vs. "System T...http://forge.typo3.org/issues/919042020-07-30T14:57:27ZSybille Peterssypets@gmx.de
<p>"Install Tool" was renamed to "Admin Tool", see <a class="external" href="https://docs.typo3.org/m/typo3/guide-installation/master/en-us/In-depth/TheInstallTool/Index.html">https://docs.typo3.org/m/typo3/guide-installation/master/en-us/In-depth/TheInstallTool/Index.html</a></p>
<blockquote>
<p>The Admin tool was called “Install Tool” in earlier versions, you will likely still see that term in some places.</p>
</blockquote>
<p>When logged in, you will see "Admin tool" in the top left.</p>
<p>There are still some places in the core, where install tool is still used. Might avoid confusion if this is cleaned up.</p>
<p>1. Message, when Install tool is locked:</p>
<blockquote>
<p>The <strong>Install Tool</strong> is locked To enable the <strong>Install Tool</strong>, the file ENABLE_INSTALL_TOOL must be created in the directory typo3conf/. The file must be writable by the web server user. The filename is case-sensitive but the file itself can be empty.</p>
</blockquote>
<blockquote>
<p>Security note: When you are finished with the <strong>Install Tool</strong>, you should rename or delete this file. It will automatically be deleted if you log out of the Install Tool or if the file is older than one hour.</p>
</blockquote>
<p>2. Don't know if we want to change the filename too ENABLE_INSTALL_TOOL. Might cause more problems than it solves.</p>
<p>3. various places in core</p>
<p>4. Some more occurrences in official docs (e.g. install guide).</p>
<p>--</p>
<p><strong>Update:</strong> See also <a class="issue tracker-1 status-1 priority-4 priority-default" title="Bug: Naming of admin vs. system maintainer privilege levels and modules is confusing (New)" href="http://forge.typo3.org/issues/88810">#88810</a> which suggests it should rather be named "System Tool" than "Admin Tool"</p> TYPO3 Core - Feature #91018 (Accepted): Automatically convert Links with "external" URLs to same ...http://forge.typo3.org/issues/910182020-04-14T10:10:03ZSybille Peterssypets@gmx.de
<p>I think it is a common phenomenon, that editors copy URLs out of the site and use it for the links. This may be especially true for large sites where it is tedious to click through the page tree in the link wizard.</p>
<p>The downside is:</p>
<ul>
<li>these links will break if the URL changes. Even if there are redirects, it is not necessary to redirect in this case and it does have an unnecessary performance and load impact.</li>
<li>these URLs are more permanent. The page id will not change, the URL may change. </li>
<li>will not work for translated pages, e.g. when the content is translated you have to change the links. If these were page links they would automatically already point to the translated page</li>
</ul>
<p>There is already an extension which does these conversions but it currently does not work for RTE: <a class="external" href="https://github.com/georgringer/uri2link/">https://github.com/georgringer/uri2link/</a></p>
<p>Also, I am wondering, why do this at a later point? Why not do it when the link is created:</p>
<ul>
<li>e.g. in the Link wizard. Either automatically convert the external URL link to page link in the link wizard or via a button. Make this configurable if this should always be done, be done in control of the editor or not at all.</li>
<li>or, on RTE -> DB transformation</li>
</ul>
<p>The conversion should work for RTE field and non-RTE fields.</p>
<p>In any case it would be good to additionally have a wizard or command line tool which does the conversion for old content.</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 - 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 #85007 (Closed): Remove setting style for broken links in RteHtmlParser::markBr...http://forge.typo3.org/issues/850072018-05-15T09:05:14ZSybille Peterssypets@gmx.de
<p>Once patch <a class="external" href="https://review.typo3.org/c/56943/">https://review.typo3.org/c/56943/</a> is merged, setting the style for broken links in RteHtmlParser should be removed in master.</p> TYPO3 Core - Bug #84887 (Closed): pageTSconfig subpage level is not considered in Linkvalidatorhttp://forge.typo3.org/issues/848872018-04-27T16:36:40ZSybille Peterssypets@gmx.de
<p>Currently, linkvalidator is highly configurable, the settings can be applied via TSconfig for a page / user / group.</p>
<p>When checking links however, only the page TSconfig of the current start page is considered. Different page TSconfig on a subpage is not considered. It does not override the settings.</p>
<a name="Steps-to-Reproduce"></a>
<h1 >Steps to Reproduce<a href="#Steps-to-Reproduce" class="wiki-anchor">¶</a></h1>
<ol>
<li>Create 2 pages with 1 tt_content element each, with a broken link each in in tt_content.header and tt_content.bodytext. I page is parent of the other</li>
<li>Set the TSconfig on the first page to scan bodytext and header</li>
<li>Set the TSconfig of the child page to only scan bodytext</li>
<li>Start "Check links" from the parent page and view report</li>
<li>Start "Check links" from the child page and view report</li>
</ol>
<a name="Expected-result"></a>
<h1 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h1>
<p>Get same number of broken links for child page: 1 (only bodytext)</p>
<a name="Actual-result"></a>
<h1 >Actual result<a href="#Actual-result" class="wiki-anchor">¶</a></h1>
<p>If "Check links" is started on child page, the result is correct.</p>
<p>If "Check links" is started on parent page, the result is 2 links for child page (not correct)</p>
<a name="Solution"></a>
<h1 >Solution<a href="#Solution" class="wiki-anchor">¶</a></h1>
<p>Either:</p>
<ul>
<li>keep current behaviour and document this (I think having a different configuration on a subpage is highly unlikely to ever be required)</li>
<li>change behaviour to check for configuration on subpages</li>
</ul> TYPO3 Core - Task #84840 (Closed): Document EXT:filemetadatahttp://forge.typo3.org/issues/848402018-04-23T16:28:06ZSybille Peterssypets@gmx.de
<p>Migrated from Core API docs project on Forge (<a class="external" href="https://forge.typo3.org/issues/52769">https://forge.typo3.org/issues/52769</a>)</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>