TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692018-02-09T21:17:52ZTYPO3 Forge
Redmine TYPO3 Core - Bug #83835 (Under Review): Linkvalidator should check more fields by default, such a...http://forge.typo3.org/issues/838352018-02-09T21:17:52ZSybille Peterssypets@gmx.de
<p>Tested (25.03.2024): should just work if added to the searchFields (with TYPO3 v12 and v13):</p>
<pre>
mod.linkvalidator.serachFields.sys_file_reference = link
</pre>
<p>Since TYPO3 v12, linkvalidator also checks fields if type = "link".</p>
<hr />
<a name="Reproduce"></a>
<h1 >Reproduce<a href="#Reproduce" class="wiki-anchor">¶</a></h1>
<p>1. Change default page TSconfig for linkvalidator to include sys_file_reference:</p>
<pre>
mod.linkvalidator {
searchFields {
pages = media,url
tt_content = bodytext,header_link,records
sys_file_reference = link
}
...
}
</pre>
<p>2. Create a "text & images" or "text & media", add an image, add a dead (not existing link) in the "Link" field for the image metadata.</p>
<p><img src="http://forge.typo3.org/attachments/download/33181/linkval4.png" alt="" loading="lazy" /></p>
<p>3. Restart "Check link", the dead link should now appear in the Reports</p>
<a name="Results"></a>
<h1 >Results<a href="#Results" class="wiki-anchor">¶</a></h1>
<p>Clicking the pen will jump to the edit wizard for sys_file_reference, but you can't change the link there, you need the edit wizard for tt_content.</p>
<p><img src="http://forge.typo3.org/attachments/download/33179/linkval1.png" alt="" loading="lazy" /><br /><img src="http://forge.typo3.org/attachments/download/33178/linkval2.png" alt="" loading="lazy" /></p>
<p>So, Linkvalidator does not properly handle sys_file_reference records (and probably wasn't intended to because it was developed before FAL).</p> TYPO3 Core - Bug #83125 (Closed): Selecting a bookmark in the backend should mark the page as sel...http://forge.typo3.org/issues/831252017-11-27T22:11:17ZSybille Peterssypets@gmx.de
<a name="System"></a>
<h2 >System<a href="#System" class="wiki-anchor">¶</a></h2>
<ul>
<li>TYPO3 8.7.8</li>
<li>Basic TYPO3 Installation (introduction package)</li>
</ul>
<a name="Reproduce"></a>
<h2 >Reproduce<a href="#Reproduce" class="wiki-anchor">¶</a></h2>
<ol>
<li>Create a bookmark of a page</li>
<li>Select the bookmark</li>
</ol>
<p>This will load the bookmarked page correctly but the page tree will just get reloaded but stay the same.</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>I would expect some visual feedback for the bookmarked page in the page tree, ideally expanding the page tree and displaying it as selected (similar to selecting it manually).</p> TYPO3 Core - Bug #82092 (Closed): Document that TYPO3 CMS 7.6 is not compatible with MySQL strict...http://forge.typo3.org/issues/820922017-08-12T12:56:39ZSybille Peterssypets@gmx.de
<p>It is still necessary to use MySQL strict mode for TYPO3 7.6.21</p>
<p>I just tested this and ran into the already known "SQL error" when trying to create a page in a bare TYPO3 system. ("SQL error: 'Incorrect integer value: '' for column 'storage_pid' at row 1'")</p>
<p>For TYPO3 8, MySQL strict mode is apparently supported: <a class="external" href="https://forge.typo3.org/issues/72610">https://forge.typo3.org/issues/72610</a></p>
<p>The "system requirements" page does not mention strict mode (which is probably ok since the currently supported version is TYPO3 8) but the other obvious sources for TYPO3 7.6 did not either, e.g. see here:</p>
<ul>
<li>System requirements on docs.typo3.org (select v7.6 on the left sidebar in the bottom): <a class="external" href="https://docs.typo3.org/typo3cms/InstallationGuide/In-depth/SystemRequirements/Index.html">https://docs.typo3.org/typo3cms/InstallationGuide/In-depth/SystemRequirements/Index.html</a></li>
<li>Installation Guide:Troubleshooting:MySQL (select v7.6 on the left sidebar in the bottom) : <a class="external" href="https://docs.typo3.org/typo3cms/InstallationGuide/latest/Troubleshooting/Mysql/Index.html">https://docs.typo3.org/typo3cms/InstallationGuide/latest/Troubleshooting/Mysql/Index.html</a></li>
<li>Install.md for 7.6 on github : <a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/TYPO3_7-6/INSTALL.md">https://github.com/TYPO3/TYPO3.CMS/blob/TYPO3_7-6/INSTALL.md</a></li>
</ul>
<p>The Install.md for TYPO3 6.2 mentions strict mode: <a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/TYPO3_6-2/INSTALL.md">https://github.com/TYPO3/TYPO3.CMS/blob/TYPO3_6-2/INSTALL.md</a></p>
<p>It would be even better to also check for strict mode on the environment check on FIRST_INSTALL but I will see if there is already an issue for this and if not I will create one ...</p>
<p>Since strict mode is officially supported in TYPO3 8 and TYPO3 8 is the current LTS version, the problem is not so severe but there still may be people using TYPO3 7.6.</p> TYPO3 Core - Feature #80092 (Closed): Reliably upgrade TYPO3 (patch/ release updates) from comman...http://forge.typo3.org/issues/800922017-03-02T11:15:34ZSybille Peterssypets@gmx.de
<p><strong>My current problem:</strong></p>
<p>Continually enhancing Upgrade mechanism for TYPO3 patch update (m.m.a >> m.m.b) from command line and still running into problems.</p>
<strong>Current Upgrade Mechanism</strong>
<ol>
<li>replace symbolic link to TYPO3 Source</li>
<li>clear PHP OpCache</li>
<li>(typo3_console)./typo3cms cache:flush --force</li>
</ol>
<p>this will result in the followinng:</p>
<p><strong>problem on upgrade 7.6.15 to 7.6.16:</strong><br />Extension-Manager:</p>
<pre>
Oops, an error occurred!
Could not analyse class: "TYPO3\CMS\Extensionmanager\ViewHelpers\ReloadSqlDataViewHelper" maybe not loaded or no autoloader? Class TYPO3\CMS\Extensionmanager\ViewHelpers\ReloadSqlDataViewHelper does not exist
</pre>
<p>This could be fixed by clearing - once more - the PHP OPCache.</p>
<p>Alternative and more brutal methods were tried, among which were some of the following steps:</p>
<ul>
<li>rm typotemp </li>
<li>rm typo3temp/Cache</li>
<li>use coreapi: cacheapi:clearsystemcache</li>
<li>or cacheapi:clearallcaches</li>
<li>use typo3_console without --force: ./typo3cms cache:flush</li>
</ul>
<p>I ran into problems with TYPO3 6 and TYPO3 7 (didn't try TYPO3 8). With TYPO3 4.5 there were no problems whatsoever - ever.</p>
<p>On Updates a number of about 150 TYPO3 installations were updated. Usually the mechanism worked quite well, but still it is not 100% reliable.</p>
<p><strong>My wishlist</strong></p>
<ul>
<li>document recommended way for upgrading from command line on typo3.org</li>
<li>integrate command line tools (i.e. typo3_console, coreapi into TYPO3 core)</li>
<li>make command line tools and configuration for TYPO3 a priority</li>
</ul>
<p><strong>Hints from others</strong></p>
<p>Searches for this topic: the answers where ambiguous: e.g. TYPO3 slack: #cig-deployment:<br />2 answers on the question:</p>
<ul>
<li>"for a 7.6 I suggest to use typo3_console :typo3cms cache:flush --force will do the job" </li>
<li>"But should be avoided to not step into race conditions. typo3cms cache:flush is usually enough."</li>
</ul>
<p><a class="external" href="https://typo3.slack.com/archives/cig-deployment/p1487754150000143">https://typo3.slack.com/archives/cig-deployment/p1487754150000143</a></p>
<p>Any help is really appreciated.</p>
<p>Sybille</p> TYPO3 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 - Feature #75456 (Closed): add no_proxy configuration optionhttp://forge.typo3.org/issues/754562016-04-08T11:48:53ZSybille Peterssypets@gmx.de
<p>TYPO3 has configuration options for proxy:</p>
<pre><code class="php syntaxhl" data-language="php"><span class="nv">$GLOBALS</span><span class="p">[</span><span class="s1">'TYPO3_CONF_VARS'</span><span class="p">][</span><span class="s1">'HTTP'</span><span class="p">][</span><span class="s1">'proxy_host'</span><span class="p">]</span>
<span class="nv">$GLOBALS</span><span class="p">[</span><span class="s1">'TYPO3_CONF_VARS'</span><span class="p">][</span><span class="s1">'HTTP'</span><span class="p">][</span><span class="s1">'proxy_port'</span><span class="p">]</span>
</code></pre>
<p>etc.</p>
<p>However a <strong>no_proxy</strong> option is missing, as described for example here: <a class="external" href="https://wiki.archlinux.org/index.php/proxy_settings">https://wiki.archlinux.org/index.php/proxy_settings</a></p>
<p>TYPO3 uses the PHP HTTP_Request2 package which also does not use this parameter.</p>
<p>However I think it could be implemented in TYPO3 as an option such as</p>
<pre><code class="php syntaxhl" data-language="php"><span class="nv">$GLOBALS</span><span class="p">[</span><span class="s1">'TYPO3_CONF_VARS'</span><span class="p">][</span><span class="s1">'HTTP'</span><span class="p">][</span><span class="s1">'no_proxy'</span><span class="p">]</span>
</code></pre>
<p>and used in typo3/sysext/core/Classes/Http/HttpRequest.php to set the proxy-options to empty if the url contains one of the domains set in no_proxy.</p>
<p>The code of TYPO3 6.2 and 8.0 looks pretty much the same here, so it shouldn't be a problem to implement for all versions.</p> TYPO3 Core - Feature #70979 (Closed): Usability: Better handling of multiple versions in Extensio...http://forge.typo3.org/issues/709792015-10-23T17:04:46ZSybille Peterssypets@gmx.de
<p>IMHO, if the TYPO3 version dependencies in an Extension are set correctly, the EM should correctly display only availabe extension versions <strong>for this current TYPO3</strong> version.</p>
<a name="Reproduce"></a>
<h1 >Reproduce<a href="#Reproduce" class="wiki-anchor">¶</a></h1>
<ol>
<li>TYPO3 6.2.15</li>
<li>install typo3_console</li>
<li>Version 1.2.3 of typo3_console is displayed by default when trying to fetch via Extension Manager, which is the current version but only runs on 7.x. IMHO the last available version for 6.2 should be displayed by default</li>
</ol>
<p>Additionally: The list of available extension versions will not show for which TYPO3 version they are available.</p>
<p>Due to this, it is tedious to select the correct version.</p> TYPO3 Core - Bug #69665 (Closed): Rendering of TypoScript shortcutIcon does not consider HTTPS (i...http://forge.typo3.org/issues/696652015-09-11T12:40:28ZSybille Peterssypets@gmx.de
<p>IMHO it should be possible to enter the URL for shortcutIcon as arbitrary URL, specifically in any the following formats:</p>
<ul>
<li>absolute path, starting with /</li>
<li>absolute URL e.g. <a class="external" href="https://www.example.org">https://www.example.org</a></li>
<li>scheme relative : //www.example.org</li>
</ul>
<p>The current rendering is not flexible enough for HTTP/ HTTPS because the rendered and cached page will be dependant on the URL scheme first used. This may result in a URL with HTTP scheme used for favicon (if the page is first fetched via http), which will then be cached and used for HTTPS as well resulting in security warnings (mixed content).</p>
<a name="TYPO3-source-code-45-and-62-more-or-less-the-same"></a>
<h1 >TYPO3 source code (4.5 and 6.2 more or less the same):<a href="#TYPO3-source-code-45-and-62-more-or-less-the-same" class="wiki-anchor">¶</a></h1>
<pre><code class="php syntaxhl" data-language="php"><span class="k">if</span> <span class="p">(</span><span class="nv">$GLOBALS</span><span class="p">[</span><span class="s1">'TSFE'</span><span class="p">]</span><span class="o">-></span><span class="n">pSetup</span><span class="p">[</span><span class="s1">'shortcutIcon'</span><span class="p">])</span> <span class="p">{</span>
<span class="nv">$favIcon</span> <span class="o">=</span> <span class="nv">$GLOBALS</span><span class="p">[</span><span class="s1">'TSFE'</span><span class="p">]</span><span class="o">-></span><span class="n">tmpl</span><span class="o">-></span><span class="nf">getFileName</span><span class="p">(</span><span class="nv">$GLOBALS</span><span class="p">[</span><span class="s1">'TSFE'</span><span class="p">]</span><span class="o">-></span><span class="n">pSetup</span><span class="p">[</span><span class="s1">'shortcutIcon'</span><span class="p">]);</span>
<span class="k">if</span> <span class="p">(</span><span class="nb">is_file</span><span class="p">(</span><span class="n">PATH_site</span> <span class="mf">.</span> <span class="nv">$favIcon</span><span class="p">))</span> <span class="p">{</span>
<span class="k">if</span> <span class="p">(</span><span class="nb">function_exists</span><span class="p">(</span><span class="s1">'finfo_open'</span><span class="p">))</span> <span class="p">{</span>
<span class="k">if</span> <span class="p">(</span><span class="nv">$finfo</span> <span class="o">=</span> <span class="o">@</span><span class="nb">finfo_open</span><span class="p">(</span><span class="no">FILEINFO_MIME</span><span class="p">))</span> <span class="p">{</span>
<span class="nv">$iconMimeType</span> <span class="o">=</span> <span class="s1">' type="'</span> <span class="mf">.</span> <span class="nb">finfo_file</span><span class="p">(</span><span class="nv">$finfo</span><span class="p">,</span> <span class="p">(</span><span class="n">PATH_site</span> <span class="mf">.</span> <span class="nv">$favIcon</span><span class="p">))</span> <span class="mf">.</span> <span class="s1">'"'</span><span class="p">;</span>
<span class="nb">finfo_close</span><span class="p">(</span><span class="nv">$finfo</span><span class="p">);</span>
<span class="nv">$pageRenderer</span><span class="o">-></span><span class="nf">setIconMimeType</span><span class="p">(</span><span class="nv">$iconMimeType</span><span class="p">);</span>
<span class="p">}</span>
<span class="p">}</span>
<span class="nv">$pageRenderer</span><span class="o">-></span><span class="nf">setFavIcon</span><span class="p">(</span><span class="nc">GeneralUtility</span><span class="o">::</span><span class="nf">getIndpEnv</span><span class="p">(</span><span class="s1">'TYPO3_SITE_URL'</span><span class="p">)</span> <span class="mf">.</span> <span class="nv">$favIcon</span><span class="p">);</span>
<span class="p">}</span>
</code></pre>
<p>As you can see, it is not possible to use relative or absolute paths because TYPO3_SITE_URL is prepended in any case. It is not possible to use absolute URLs because this will result in is_file failing.</p>
<p>This issue has actually already been reported, but for typo3.org, see <a class="external" href="https://forge.typo3.org/issues/58265">https://forge.typo3.org/issues/58265</a></p>
<p>Any help is appreciated.</p> TYPO3 Core - Bug #68635 (Closed): change type of content element: linkvalidator will show irrele...http://forge.typo3.org/issues/686352015-07-29T21:28:56ZSybille Peterssypets@gmx.de
<p>On changing the type of a content element, text is still kept in the database tt_content record (e.g. bodytext) even though it is not used. The linkvalidator should only check database columns, if they are actually used (usually depends on ctype in tt_content).</p>
<p>Example: change a text content element to shortcut.</p>
<p>Reproduce:</p>
<p>1) create a text element and insert a dead link : Linkvalidator will correctly report this<br />2) change content type of content element, e.g. to "insert records" (tt_content.ctype='shortcut') and save (tt_content.bodytext still contains the text with the dead link)<br />3) Linkvalidator will still incorrectly report the dead link, even thought it is not displaed.</p>
<p>Tested in TYPO3 6.2.14, TYPO3 4.5.40</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 #65776 (Closed): check in Upgrade Wizard fails due to truncated file pathhttp://forge.typo3.org/issues/657762015-03-16T16:35:57ZSybille Peterssypets@gmx.de
<a name="Reproduce"></a>
<h1 >Reproduce<a href="#Reproduce" class="wiki-anchor">¶</a></h1>
<ol>
<li>Update from the latest 4.5 to 6.2.10 and run the Upgrade Wizard.</li>
</ol>
<a name="Result"></a>
<h1 >Result<a href="#Result" class="wiki-anchor">¶</a></h1>
<p>Upgrade Wizard shows a number of links to missing files. Some of these are not actually missing. The problem seems to be that the Upgrade Wizard truncates the path of long filenames (length > 200), the File Abstraction Layer however has no problem with path / filename of this size, so the link actually works. The error message of the Upgrade Wizard is wrong.</p>
<a name="More-information"></a>
<h1 >More information:<a href="#More-information" class="wiki-anchor">¶</a></h1>
<p>Error message</p>
<pre><code class="text syntaxhl" data-language="text">File not found (page / uid / path / table / field):,3249,30782,fileadmin/sonderpaedagogik/DownloadsDozeten/Luedtke/Luedtke_Kallmeyer_2007_._Sprachenvielfalt_in_deutschen_Kindergaerten_-_Chance_oder_Hindernis._hoergeschaedigte_kinder_-_erwachsene_hoergeschaedigte.,tt_content,bodytext
</code></pre>
<p>Name of path:</p>
<pre><code class="text syntaxhl" data-language="text">fileadmin/sonderpaedagogik/DownloadsDozeten/Luedtke/Luedtke_Kallmeyer_2007_._Sprachenvielfalt_in_deutschen_Kindergaerten_-_Chance_oder_Hindernis._hoergeschaedigte_kinder_-_erwachsene_hoergeschaedigte.pdf
</code></pre>
<p>Entry in sys_file is correct:<br /><pre><code class="text syntaxhl" data-language="text">uid=8814, identifier="/sonderpaedagogik/DownloadsDozeten/Luedtke/Luedtke_Kallmeyer_2007_._Sprachenvielfalt_in_deutschen_Kindergaerten_-_Chance_oder_Hindernis._hoergeschaedigte_kinder_-_erwachsene_hoergeschaedigte.pdf"
</code></pre></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> TYPO3 Core - Bug #49440 (Closed): Backend usergroup editing: Missing Texts in Access Lists: Allow...http://forge.typo3.org/issues/494402013-06-26T11:13:31ZSybille Peterssypets@gmx.de
<p>Since a change in the grouping of excludefields (TYPO3 4.5.23) some of the description texts are missing and only the keywords in parenthesis are displayed.</p>
<p>Descriptions are missing in German and English.</p>
<p>Most of the missing descriptions seem to be related to <strong>dropdown_sitemap</strong>, <strong>powermail</strong> and <strong>felogin</strong>:</p>
Page
<ul>
<li>(appear)</li>
<li>(description_field)</li>
<li>(exclude_doktypes)</li>
<li>(exclude_pages)</li>
<li>(expall)</li>
<li>(fade)</li>
<li>(link_text)</li>
<li>(include_not_in_menu)</li>
<li>(expand_levels)</li>
<li>(show_levels)</li>
<li>(list_tag)</li>
<li>(show_spacers) </li>
<li>(link_target)</li>
<li>(engine)</li>
<li>(singleview)</li>
<li>(singlepid)</li>
<li>....</li>
</ul>
Website User
<ul>
<li>(felogin_forgotHash)</li>
</ul>
Rules
<ul>
<li>(mandatory)</li>
<li>(maxlength)</li>
<li>(placeholder)</li>
</ul> TYPO3 Core - Bug #37467 (Closed): Change in class.t3lib_div.php may break things for HTTPS via re...http://forge.typo3.org/issues/374672012-05-24T14:51:11ZSybille Peterssypets@gmx.de
<p>The change introduced in TYPO3 4.5.16 as fix for bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Wrong HTTP protocol in combination with a proxy (Closed)" href="http://forge.typo3.org/issues/36004">#36004</a> makes working in backend impossible for some HTTPS reverse-proxy configurations.</p>
<p>It may be a misconfiguration on our end, but as far as I can see, since the change HTTPS will only work with reverse proxy, if <strong>X-Forwarded-For</strong> contains local and proxy IP and</p>
<pre><code class="php syntaxhl" data-language="php"> <span class="err">$</span><span class="p">[</span><span class="s1">'TYPO3_CONF_VARS'</span><span class="p">][</span><span class="s1">'SYS'</span><span class="p">][</span><span class="s1">'reverseProxyHeaderMultiValue'</span> <span class="o">=</span> <span class="s2">"last"</span><span class="p">;</span>
</code></pre>
<p>Login to backend works, but then a network connections error is displayed (<em>"Verbindungsproblem Bei dem Versuch eine Verbindung zum Server herzustellen ist ein Fehler aufgetreten. Bitte überprüfen Sie Ihre Netzwerkverbindung."</em>)</p>
<p>Analyzing this shows that the changed line 4151 in class.t3lib_div.php has caused this problem:</p>
<p>older version:</p>
<pre><code class="php syntaxhl" data-language="php"><span class="k">if</span> <span class="p">(</span><span class="k">self</span><span class="o">::</span><span class="nf">cmpIP</span><span class="p">(</span><span class="nv">$_SERVER</span><span class="p">[</span><span class="s1">'REMOTE_ADDR'</span><span class="p">],</span> <span class="nv">$proxySSL</span><span class="p">))</span> <span class="p">{</span>
</code></pre>
<p>newer version:<br /><pre><code class="php syntaxhl" data-language="php"><span class="k">if</span> <span class="p">(</span><span class="k">self</span><span class="o">::</span><span class="nf">cmpIP</span><span class="p">(</span><span class="k">self</span><span class="o">::</span><span class="nf">getIndpEnv</span><span class="p">(</span><span class="s1">'REMOTE_ADDR'</span><span class="p">),</span> <span class="nv">$proxySSL</span><span class="p">))</span> <span class="p">{</span>
</code></pre></p> TYPO3 Core - Feature #36542 (Closed): Changed domain handling on "View webpage" from backend caus...http://forge.typo3.org/issues/365422012-04-25T12:32:51ZSybille Peterssypets@gmx.de
<p>Due to fix for Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: t3lib_befunc::getViewDomain returns wrong or no domain (Closed)" href="http://forge.typo3.org/issues/30892">#30892</a>:</p>
<p>This new behaviour causes problems for us.</p>
<p>For a long time (due to bug or not) the domain currently used in the backend was used for loading a page with "View webpage". Due to the change in getViewDomain, the first domain from the domain records is now used.</p>
<p>On multi-site installations we use a generic domain for working in the backend and this should be consistent with the domain used for viewing the page from the backend.</p>
<p>We now have to patch the core or completely change handling.</p>
<p>Ideal would be to make this configurable !!!</p>