Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#1 2006-03-21 16:01:37
- resplence
- Member
- Registered: 2006-03-07
- Posts: 37
Firefox killed my site (trying to save index.php instead of opening)
I was logged in, managing things around, when I clicked to navigate to a different section and it prompted a warning asking which program I wanted to open “index.php” with. I cancelled and tried to navigate to a different section, log out, etc… but it kept popping-up that same warning. Even when I tried refreshing the page.
So I deleted all private data (cookies, cache, history, saved forms and passwords), exited Firefox and ctrl+alt+del to make sure to kill every running Mozilla process.
Then I tried to access my site and admin area on Firefox, and all I got was a blank page. So I tried opening http://mydomain/index.php and got that warning again. I selected Firefox as the program I’d like to use to open index.php, and set it to always use that setting. Then it started opening blank pages in tabs untill Firefox eventually crashed.
It works ok on IE, even after cleaning IE cache and cookies. I’m logged in there right now, and disabled all plugins, just in case. Other people get a blank page when viewing it on both browsers, though. It seems only I can access my site, with IE.
I don’t get it, everything was working just fine. Any thoughts on what happened and how it could be avoided/solved?
Thanks.
Last edited by resplence (2006-03-21 16:50:27)
Offline
#2 2006-03-21 18:35:02
- resplence
- Member
- Registered: 2006-03-07
- Posts: 37
Re: Firefox killed my site (trying to save index.php instead of opening)
I think I’m gonna uninstall textpattern and install it again. At this moment here’s what happening with my site:
I can view the site normally with IE; I can access the admin area normally with IE; The site responds as expected to my alterations, with IE; I get a blank page on both the root and admin area with Firefox.
Now, with other people: some have access to everything on both browsers; some have access to nothing on both browsers; some can only view it in IE; some can only view it with firefox.
It doesn’t make any sense. I’m also trying to solve this on a thread over at Firefox’s support forums, and noone there can see anything. However, someone just posted this:
—————
The response headers for http://rafaelmadeirashow.com/index.php show a content-type of “text/html; charset=utf-8”.
When I save the page locally, the file is empty. However, the content is shown at Web-Sniffer:
http://tinyurl.com/es5vm
—————
It just doesn’t make any sense.
Last edited by resplence (2006-03-21 18:37:21)
Offline
Re: Firefox killed my site (trying to save index.php instead of opening)
It’s a problem with your server. If you go to the websniffer site and check the box that says “accept gzip”, you don’t get any response shown. Something seems to be killing off either php or apache-process. Also I am not sure what this in the server signature means “PHP-CGI/0.1b”, but the version number seems not so encouraging…
Offline
Re: Firefox killed my site (trying to save index.php instead of opening)
firefox does this if your server doesn’t respond in a timely manner, IE just gives a standard 440 error. If you were being very busy with your site and everything was Ok, then it may be something like your hosting providers have a limit set as to how many times you can times per min/hour etc you can quiery the database and you may have hit that limit. This is done to stop one web site hogging all the server resourses on a shared hosting account for instance.
Offline
#5 2006-03-23 14:10:05
- resplence
- Member
- Registered: 2006-03-07
- Posts: 37
Re: Firefox killed my site (trying to save index.php instead of opening)
Oh, I see. Thanks. I think that’s what happened, since it’s all back to normal again, just like that.
Offline