browsers can't get past Front Page splash screen when caching is on
alienzed - October 15, 2009 - 03:14
| Project: | Front Page |
| Version: | 6.x-1.2 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Dublin Drupaller |
| Status: | won't fix |
Jump to:
Description
Using IE or iPhone Safari for example, the user gets stuck on the splash screen which constantly just reloads as a cached page.
The only way I've gotten around this is by turning caching for the whole site off, which is bad for performance all around.
#1
#2
#3
that's an unusual problem.
there is a module called exclude (or something like that) which allows you to specify pages to exclude from cache.
can you paste a link to your front page so I can have a look at it. I haven't had the same problem with cache switched on
#4
http://survivethrive.on.ca/ is the site...
And this really bothers because I can't reproduce it on command.
I developed that site with caching off, obviously, and then when it came to deployment, everything seemed fine. Then suddenly I noticed that IE6 couldn't get past the splash screen. The problem was obvious to me, since the splash page and the real page both show up at the same address... http://survivethrive.on.ca/ caching must have been returning the cached splash page instead of the real site.
I proceeded to turn caching(normal) off, which sucked cause the page's server isn't zippity running Drupal 6. Eventually I did some playing around and turned cache back on, thinking I had solved the problem by linking to
http://survivethrive.on.ca/en
or
http://survivethrive.on.ca/fr
instead of the same page with a ?q=en or ?q=fr
Two or three days went by, checking the page like twice a day to make sure it was still accessible. Then BAM Tuesday afternoon I try it and can't get past the splash in Safari, Firefox or IE. I immediately turned caching(normal) off and could browse the site normally again.
Thing is that I can't really risk turning caching on again, as it might loop the splash screen for up to half a day without me even knowing. Setting a minimum cache time doesn't seem like a good idea either since the site could, afaik just stop working for some user for whatever minimum time I set. The site isn't a huge important one, but downtime is absolutely unacceptable. I will look into exclude, thank you!
#5
strange. the site splash page works perfectly for me...just tried it in firefox (3.5.4), google chrome (3.0) and internet explorer (8.06).
When I click on the en or fr option, I don't see the splash page anymore. Is that where the problem lies or is it when you login and visit the front page?
#6
I've had trouble with caching and Front Page too, like when users log out, to the point of disabling caching entirely as I need Front Page's features for one of my sites.
Maybe that exclude module can just exclude Front Page entirely for now, as I doubt Front Page is that hefty. I haven't time to investigate right now though.
#7
CacheExclude looks promising: http://drupal.org/project/cacheexclude
I enabled it and caching, excluded the front page, and no problems yet. Thanks for the tip.
#8
I haven't experienced the same problems you reported alienzed. Try the cacheexclude module as mentioned by Scott & phillip.
#9
please open this issue back up if you're still having problems. the front page.module doesn't have any control over the drupal cache like the exclude from cache.module for example.
.