By brockdray on

Last week we began experiencing a significant problem with our website, http://www.msuu.org, involving caching issues. Our site editors struggled with logging into the site. Often the site thought they were other users. We've been able to get around this mostly, but one major issue remains: the front page of the site is showing old content and refuses to update. It should reflect the content on http://www.msuu.org/main (this is the page set as in Site Information).

I have flushed all caches several times. I have rebuilt permissions (because of the initial user errors). I am currently at a loss for what to do next. Help!

⋅ Categories: Drupal 7.x

Comments

VM’s picture

VM commented

using any 3rd party caching mechanisms?
what exactly is the path set for the front page in site information?

Are you sure the front page isn't being over ridden via a custom theme file or module?

brockdray’s picture

brockdray commented

No 3rd-party caching mechanism. The front page is set to main, which is where I want it to go to. This all worked perfectly until last week, and I don't think anything changed with our theme files.

VM’s picture

VM commented

to debug test path to fort page as node

Any behavior change? I notice that the current front page and the new one at /main both indicates they are generated from node/659. I'd check the theme for any custom page--front.tpl.php files are custom node--659 files.

brockdray’s picture

brockdray commented

No custom theme templates for either page. Like I said, this just started happening last week. Before that, it all worked fine, and we've only made content changes since then.

I've tried to change the front page to something other than /main, but it hasn't made a difference. Even with that change, Drupal still shows the "stuck" version of node/659 (i.e., /main) as the front page.

brockdray’s picture

brockdray commented

The only place it makes a difference is on mobile. On mobile devices, I can see the new front page. In fact, when I Inspect in Chrome and set the page to emulate a mobile device, I can see the changes. But, when I go back, it reverts to the old version. So maybe this is an issue with media queries?!?

brockdray’s picture

brockdray commented

Another weird thing is the parked domains. Both msuu.net and msuu.com are parked domains on the same host. They are supposed to point to the exact same page, but they point to the correct (updated) front page. I spoke with the server host, thinking maybe this was a server cache issue, but they said they couldn't see anything on their end. Oy!

VM’s picture

VM commented

I'm out of ideas at this point. I don't see how Drupal could be the problem based on the above.

brockdray’s picture

brockdray commented

I don't disagree with you. I just don't know what to do next to fix it. Thanks for helping, though.

mmjvb’s picture

mmjvb commented

Or remove history and cookies for your site in your browser. A forced refresh may also just what you need.

ressa’s picture

ressa commented

The two versions of the frontpage seem to be in sync now.

brockdray’s picture

brockdray commented

Thanks, ressa. Yeah, I got this fixed late last night and forgot to update this forum. It turned out to be the server cache. As soon as the host cleared that, everything worked properly. Not a Drupal issue at all.