By DanielR on

I moved my drupal site to a new webhost (HostGator) successfully. Files were transfered by tar'ing and transfering them, and I finally got the database installed properly by exporting it from the old and importing it to the new site.

I had a few database problems at first, but they've been solved. Then, just as a sanity check, I set the database name incorrectly *on purpose* in settings.php, to make sure I get a drupal warning page. This worked well - I went to the front page of my site http://toonut.com/ and got an "unable to select database" page.

Then I set the database name correctly, but I still get that warning instead of my front page. There's nothing wrong with my settings, because I could go to the /user page and log in to the site, and everything works perfectly. I've tried clearing my browser cache, going to the page from another computer (albeit from the same home network) - still I get a warning instead of my front page.

I also tried setting the database name in settings.php incorrectly on purpose again, to something different, but the warning page I get still shows the old incorrect database name.

I tried renaming Drupal's index.php page to index_temp.php hoping that I'd get a no-page-found. No effect.

By the way, when you go to my front page (http://toonut.com/), the "site information" is set up to send you to a View called "frontpage". Strangely enough, if you go there directly (http://toonut.com/frontpage), it works fine.

It feels to me as if somebody else, between my php files and I, is caching http://toonut.com/. If you have any ideas or advice, I would greatly appreciate it.

⋅ Categories: Drupal 5.x

Comments

DanielR’s picture

DanielR commented

I tried loading my front page http://toonut.com/ remotely from another computer somewhere else in the world, and it worked fine - no error page.

I tried loading front page from lynx on my own PC (to make sure it's not a browser issue of any kind), I still get the error page.

I found a somewhat similar issue somebody had with Joomla - about cached error pages, and in their case it also worked fine from another distant computer. See here:
http://forum.joomla.org/index.php?topic=197263.msg934793

Somebody suggested it might be a PHP/Zend optimizer issue with HostGator, and the final "solution" was to use another hosting service. I'd rather not do that.

DanielR’s picture

DanielR commented

Nothing I tried worked, so I went shopping for groceries. Upon arrival, lo and behold, my site was working properly. I'm very unhappy not to have gotten to the bottom of this problem, because if it comes back I'm stuck. For the moment I can't reproduce the problem so nothing can be done.

DanielR’s picture

DanielR commented

This whole country is sitting behind a government-controlled caching proxy, which caches based on IP address.

That's why certain files and pages were only getting refreshed after I'd wait for X hours or I would reboot my router, causing the ISP to allocate me new IP address.