View Full Version : Refresh trouble in dotproject
28-05-04, 12:25 PM
hi, I have some problem with the refresh in dotproject with mozilla. For exemple, if i'm in the task list page and i click on edit task, then i change the name of the task and I save. This return me to the task list page but the name of the task that I had change, don't change. And don't change anymore if I click the refresh button of my browser. The only way to correcly refresh the page is to click the refresh button with the **** key pressed.
This trouble don't arrive with IE.
Is someone have the same problem or it's in my config ?
28-05-04, 04:39 PM
Can you tell me what the server is? There was a problem with Apache2 where the headers required to set no caching were being munged by the web server, however I believe we have fixed this particular problem.
Also you don't give any information on the version of Mozilla nor the version of dotProject. Certainly I have no problems with Mozilla 1.7a on Linux with Apache 1.3 and dotproject 1.0.2-1.
29-05-04, 12:33 AM
I use apache 2.0.39 on win2000 server machine. The version of dotproject is 1.0.2. I try it with Mozilla 1.6 and firefox 0.8.
I also try the cvs dotproject and it give me the same problem.
04-06-04, 10:34 PM
How do you access your DotProject site? I know from our experience that if you connect to it using a local IP address (ie 192.168.0.10) then both Mozilla and Firefox don't refresh properly. Opera is the same way. We haven't figured a way around this yet, except by accessing the site using a fully qualified domain name (ie intranet.mydomain.com.) hope this helps
I'm having the same problem:
Apache 2.0.40 (on RH9)
I am using a FQDN. Is there anything I can do to the Virtual Host on Apache to fix this problem? php.ini?
I would ask my staff to use IE for dotproject, but they'd never go for it!
09-08-04, 11:45 PM
I'm using Firefox 0.9.2 and IE and this morning I updated something in IE and the display changed with no problem. In Firefox, it did not change. I went into the backend to check the data and it had updated.
So I dumped Firefox's cache and everything was retrieved from the database correctly.
I'm not sure if there's a Singleton somewhere that's not being reset properly or what, but I hit it about 12 months ago with Netscape 7.0 too.
OK, it might be related to cache, but surely there's part of the HTML header telling the browser not to cache?
emptying cache isn't something we should have to do every time we use dp!
10-08-04, 08:30 PM
There are many things in dp that tell proxies and browsers NOT to cache, but some browsers/proxies don't respect these settings :(
OK, but I'm not getting any closer to a solution. I am happy to have a go at debugging this problem, but I don't know where to start. Someone above has stated that it's an Apache thing, you're saying it's a browser thing.
There is no proxy at my end. Can the person who worked on the Apache 2 problem mentioned above shed any light?
10-08-04, 10:36 PM
Alright, I've been jacking around with it quite a bit over the last day.
I have two installations of the latest release (1.0.2)... one at work and one on my hosting service. At work, I have Apache 2 installed, I'm not sure what's on the hosting service.
On the hosting service, I *always* use the full domain name and have never had a refresh problem. On our work server, if I use the full domain name, I don't have any problems. If I use the computer name or IP address, the cache does not always update.
Hope this is helpful...
I'm using a FQDN... no joy yet. Perhaps your host is using Apache 1.3. Can you phpinfo() your host?
10-08-04, 11:35 PM
Good call, I forgot to do that.
Results: Apache/1.3.29 (Unix)
My work box is running 2.0.40-8
Thanks for checking that. Anyone got further ideas on what Apache 2 is up to? What was it 'munging' before?
Could a developer please detail what went wrong with Apache 2 before?
I can debug this sort of thing, but I need to know where to begin.
I really want to get my team using dotproject, but they won't use anything other than Mozilla/firefox.
15-09-04, 10:23 PM
Good for them. I'm getting the 1.0 Pre-Release now.
I don't believe it's a Mozilla/Firefox issue at all. I *believe* it's due to using a machine name as opposed to a complete URL or IP Address.
I've not run into the problem at all since I started doing to that way...
I'm still confused as to why IE would be fine.
Perhaps it's a cookie/session/cache/proxy thing, which was suggested in an earlier post. Apache 2 and my version of PHP are also a bad idea apparently, but there's not much I can do about them right now.
What confuses me more is that I've built a lot of applications on this platform with no problems of this nature in relation to browsers. Which elements of core are likely to be causing this problem? What's different about dotproject that means that this problem occurs (compared to other PHP software)?
I've looked into my Apache headers, here's what I found:
1 HTTP/1.1 200 OK
2 Date: Wed, 15 Sep 2004 16:52:13 GMT
4 Accept-Ranges: bytes
5 X-Powered-By: PHP/4.2.2
6 Set-Cookie: dotproject=2b1df652bbfd8f6f0027a3bda8353e58; path=/
7 Expires: Mon, 26 Jul 1997 05:00:00 GMT
8 Cache-Control: no-cache, must-revalidate
9 Pragma: no-cache
10 Last-Modified: Wed, 15 Sep 2004 16:52:13 GMT
11 Content-Length: 1917
12 Connection: close
13 Content-Type: text/html;charset=utf-8
I don't think these are being munged by Apache 2, but someone might know better.
I commented this stuff out from index.php:
// write the HTML headers
header ("Expires: Mon, 26 Jul 1997 05:00:00 GMT"); // Date in the past
header ("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT"); // always modified
header ("Cache-Control: no-cache, must-revalidate"); // HTTP/1.1
header ("Pragma: no-cache"); // HTTP/1.0
which got Mozilla/Firefox working.
16-09-04, 07:47 AM
This is odd behaviour as it should do the exact opposite of what you are seeing. I.e. the normal behaviour would be to cache this page unless the anti-caching headers are supplied.
Try replacing the Cache-Control header line with:
header ("Cache-Control: no-cache, must-revalidate, no-store, post-check=0, pre-check=0");
This supplies the full set of options to Cache-Control and should work. This is how it is now done in the current CVS.
thanks, it works fine now.
vBulletin® v3.6.4, Copyright ©2000-2013, Jelsoft Enterprises Ltd.