Bug #21600
closed
Page tree will not be shown in the typo3 backend
0%
Description
I use TYPO3 in Japan.
I update beta2 -> beta3 ,
1.Login BE
?
2. Click left menu icon
?
displayed on page-tree window
"The requested URL /mydomain/typo3/¤tSubScript= was not found on this server."
But, page-tree is displayed that it clicks several times.
I tried
alt_mod_framset.php returned state of beta2 and
class.t3lib_div.php 's function sanitizeLocalUrl returned sanitizeBackEndUrl.
Then, it operated normally.
But, I would like to ?he sanitizing function is effective.
(issue imported from #M12649)
Updated by saito about 15 years ago
When adding it. I return them reffer id:0012324
Updated by Oliver Hader about 15 years ago
Can you please tell me the full URL that is used to access your backend?
Besides that, what PHP version are you using. Do you use PHP as CGI?
Updated by saito about 15 years ago
Hi Mr.Oliver.
URL to BE is /mydomain/typo3/backend.php
I think that this is typical url.
PHP is used as a module of apache.
But PHP version is 5.1.6.
This was outside the support range...
If this is a cause, can do nothing but you give it up?
Updated by Chris topher almost 15 years ago
Your PHP version really is to old. Although I am not sure if that really causes your problem, could you upgrade it?
PHP 5.2 is already needed for TYPO3 4.2 and also would be enough for TYPO3 4.3.
Updated by Oliver Hader almost 15 years ago
PHP 5.1 could be the reason since filter_var(), which is used in t3lib_div::sanitizeLocalUrl(), was first available with PHP 5.2.
Updated by saito almost 15 years ago
Hi, Mr.Christopher.
I know PHP is to old.
But this system built on rental server, so I can't version up it.
Thank you for advice.
Hi, Mr.Oliver.
I know filter_var() wasn't available with PHP5.1.
So, I operated though filter_var is not used.
However, because the possibility of the problem of
the version seems to be high, this matter is given up.
Thank you.
Updated by saito almost 15 years ago
Oh no!
Resolution changed reopened from fixed.
Please returns it to fixed.
Sorry.
Updated by