Bug #16421
closedCan't save, modify the content or reload page tree from server -> typo3.com will be loaded
Added by Istvan Szantosi over 18 years ago. Updated over 14 years ago.
0%
Description
After logging in into the backend I would like to modify page content or page properties, then I click on save and typo3.com will be loaded instead of the backend.
Cliking on "reload page tree from server" brings typo3.com into that frame.
Unforatunately I can't modify anything.
Thank You for Your help in advance!
(issue imported from #M3963)
Files
extensions.jpg (27.9 KB) extensions.jpg | Administrator Admin, 2006-08-04 16:09 |
Updated by Andreas Wolf over 18 years ago
Well, I would guess the links you clicked miss the domain name of your server, so the link is something like http://typo3/xxx.php?... Your browser tries to load the page from a server named typo3, then automatically tries www.typo3.com, www.typo3.net and www.typo3.org, I don't know the exact order.
Could you supply some more details (installed extensions, server-environment, e.g. OS, Webserver, exact PHP-version)? And perhaps you could try to copy one of the links you clicked on before this happened (e.g. the Reload Page Tree-link)?
Updated by Istvan Szantosi over 18 years ago
Hello Andreas,
thank You for Your fast response!
You were totally rigth.
The bad link which is typo3 backend searching for is:
http://typo3/alt_db_navframe.php?PM=0_1_0_browsepages
The help link works:
http://www.mysite.hu/typo3...., so this is the point.
Do You have any idea how to fix it?
I tried to delete completely typo and to drop all tables more times, but the new install did not work.
My system is the following:
MYSQL 4.1.11
Debian_4sarge5
phpMyAdmin 2.7.0-pl2
Typo3 4.0
dummy package 4.0.1
Thanks a lot in advance!
Updated by Istvan Szantosi over 18 years ago
Hello again...
Sorry I missed some environment details:
Apache/2.2.3 (Unix) mod_ssl/2.2.3
OpenSSL/0.9.8b
PHP/5.1.4
mod_perl/2.0.2
Perl/v5.8.4
Updated by Andreas Wolf over 18 years ago
Well, I don't think it's a DB-related problem. It more sounds as if TYPO3/PHP could not determine the correct hostname and thus not build correct links. Normally, all links are built relative to the typo3/-dir, so they should always work. But the refresh-link at the bottom of the treeview is absolute (/typo3/typo3/alt_db_navframe.php??currentSubScript=db_list.php for me).
Perhaps there is a problem with your browser - you didn't mention which one you use. For me, it works in Firefox from version 1.0 to 2.0 Beta, and an IE I tested a long time ago also worked.
Could you try to extract the refresh-link from the source of the navtree-frame? I don't think that the link is incorrect - for me it works with Apache 2.0 and PHP 5.1.4 -, but I'm not sure it always works.
Updated by Istvan Szantosi over 18 years ago
Hello Andreas,
You are right, I forgot to mention my browser.
Just to see clear:
I made this site with typo3, I have used Firefox and IE too. It worked fine.
One day to another I have this failure...
I tried now:
Firefox 1.5.0.5
Netsape Browser 8.1
Opera 9.01
IE 6.0
None of them worked :( Always the same...
I have one Typo4 WAMP installed to locally and it is working good with my browser. Do You thing maybe the php version makes this caos? Locally I have php 5.0.5.
I'm a newbe in typo3. Could You please tell me how to "to extract the refresh-link from the source of the navtree-frame"?
THANK YOU!
Updated by Andreas Wolf over 18 years ago
Hello Istvan,
thanks for the additional information. I don't think it could be the PHP-version because I run TYPO3 4.0 under version 5.1.4 on two computers (both Ubuntu Linux, Apache 2.0.5x, MySQL 5.0). I don't even think it is the Apache-version etc., but to my mind the most likely reason for this failure is an extension that makes a mistake somewhere. Could you post a list of extensions you have installed? For this, go to "Installation" (under "Tools" in the T3-backend), there choose "all configuration", search for "[extList]" and copy the input-field there.
@extracting: If you are in Firefox, open the backend, open the nav-frame, right-klick there, in the menu go to "Current Frame"->"Show source" (don't know the exact titles, I use Firefox in German ;). A new window with the HTML-source of the frame will open. There type Ctrl+F and search for "reload". There must be this: <a href="...">Reload page tree from server</a>. Please post this whole string, from "<a" to "a>".
Updated by Istvan Szantosi over 18 years ago
Hello Andreas,
thank You very much for Your time again!
OK, lets see...
I have copied the link as You wrote:
<a href="//typo3/alt_db_navframe.php?&currentSubScript=sysext%2Fcms%2Flayout%2Fdb_layout.php&id="><img src="sysext/t3skin/icons/gfx/refresh_n.gif" width="16" height="16" title="Reload the tree from server" alt="" /></a><a href="//typo3/alt_db_navframe.php?&currentSubScript=sysext%2Fcms%2Flayout%2Fdb_layout.php&id=">Reload the tree from server</a>
For the extensions, I made printscreen(extensions.jpg) . I hope this is what You ment. I had difficulties to find it that way as You wrote.
Thank You!
Updated by Andreas Wolf over 18 years ago
Hm, you don't have loaded any extensions that are not loaded by default - so this can't be the reason for the error. (I described it a bit difficult, but I thought you had perhaps installed a lot of different extensions which would have been hard to get via one screen-shot.)
There clearly is an error somewhere - with me, the link refresh-link looks like this: /admin/mintsp/typo3/alt_db_navframe.php?PM=0_0_2_browsePages. With your link, the part first part before /typo3/ is missing. Somehow, there must be a problem between Apache, PHP and TYPO3. Perhaps the behaviour of Apache 2.2 has changed somewhere and TYPO3 doesn't reflect this.
What we could try now is to find it out via the debug-information TYPO3 gathers from your system. But exposing this information to the public might - theoretically - pose a security-threat to your site. Or it is not allowed with some organizations and company, as it reveals parts of the server-configuration.
You could send the information to me via e-mail - my adress is typo3 [at] andreaswolf.info -, but only if it's allowed and you wish to.
The information neccessary can be found in the Install Tool (under menu Tools in the T3-Backend) in "8: phpinfo()". At first, the information from the text-field "DEBUG" should be sufficient, and perhaps the information from t3lib_div::getIndpEnv() and getenv(). Most information in the other parts is redundant.
To me, this more or less sounds like a bug in TYPO3, due to a changed default-behaviour in Apache and/or PHP, while I would say it's Apache.
Updated by Istvan Szantosi over 18 years ago
Hello Andreas,
sorry, that I was not available in the last days. I have sent You a mail last week (tuesday) with informations You asked for. Maybe You did not received it, but I didn't got any mailer deamon message...
Anyway, I could have misunderstood Your mail address, that's the problem.
I will try it again, but if I don't succeed and You don't get a mail in a hour, please write me Your e-mail address again. Thank You!
My e-mail address is: szantosi_istvan@freemail.hu, if You think, You try to reach me too.
Thank You for the help!
Updated by Andreas Wolf over 18 years ago
Hello Istvan,
yes, I received your mail yesterday, but I forgot to redirect it to my office address - shame on me...
I will have a look at this topic this evening or tomorrow. I think we will find a solution :)
You wrote about a first e-mail - I didn't get any mail from you before, but perhaps SpamAssassin has killed the mail. I will have a look at my spam-folder later on.
Updated by Andreas Wolf over 18 years ago
Hm, I only found one big difference between your and my system information: The var TYPO3_SITE_SCRIPT starts with a slash in your configuration, in mine the slash is missing. I can only guess, but perhaps that's the reason. I don't know why this happens and how this should cause the error, but I don't have a guess for another reason by now.
Perhaps I will have a look at the source of T3 later on and try to find out how the link is computed and if TYPO3_SITE_SCRIPT plays a role in this.
Edit: Well, I don't know why, but in your configuration REQUEST_URI starts with two slashes. As far as I saw, this is the reason why TYPO3_SITE_SCRIPT starts with a /. One is removed, but the other one remains.
Updated by Istvan Szantosi over 18 years ago
Hello Andreas,
thank You for the infos!
Let me know if I can help You!
Updated by Istvan Szantosi over 18 years ago
Hello Andreas,
do You have maybe some tricks how to fix the problem?
Thank You!
Updated by Andreas Wolf about 18 years ago
First of all sorry that I didn't get back on you for weeks, but I was busy and somehow forgot...
The problem clearly is the // in //typo3/alt_db_navframe.php?¤tSubScript=sysext%2Fcms%2Flayout%2Fdb_layout.php&id=
I simulated such a link here in the TYPO3-backend by manipulating the link via Firefox' DOM Inspector and a click on this link gave me a "Server not found"-error.
I suspect that something in your server- or firewall-configuration has to be wrong. I don't know by now what may cause this, but at home I will have a look at your data again - and hopefully find some hint at the problem ;)
Updated by Thomas Hempel about 18 years ago
Hi,
I had this failure too several times. But I this misbehavior is not reproducable on my systems. (I didn't tested the links that where posted here.)
Greets,
Thomas
Updated by Martin Holtz about 18 years ago
Hi,
a few years ago i had an error with sometimes doubled slashes within php 4.1.2
changing the version was the only way to get out.
Perhaps down/upgrade of the php Version helps?
Updated by Andreas Wolf about 18 years ago
@Martin: I don't think this would help - a bug in PHP was my first guess too, but at home I have PHP 5.1.4 running without problems, and Istvan uses exactly the same version. I would rather guess that there is a problem with the Apache-version - perhaps a complete phpinfo() could help.
On the other hand this bug should be fixable by changing the function t3lib_div::getIndpEnv() to return REQUEST_URI beginning with only one slash. That would at least be a workaround, but it would not fix the reason for the problem itself.
Updated by Chris topher over 14 years ago
No feedback for a long time, noone reporting here that this problem is still present in newer versions. No similar bugreports for current versions. I close this one now.