CMS Made Simple Forums

calguy1000 wrote:Check your UDT's and 3rd party modules/plugins to make sure that they are not messing with the cache.

Good advice and I really appreciate your reply, but for those of us that have no idea how to do this, is there a simple series of steps? Or is it a matter of reviewing the code of every module we have installed? Is there a variable or other word we should be searching for?

gocreative wrote:

calguy1000 wrote:Check your UDT's and 3rd party modules/plugins to make sure that they are not messing with the cache.

(...) Or is it a matter of reviewing the code of every module we have installed? (...)

In the case of UDT's yes, I believe it's the only way. As for modules you can deactivate suspect modules, one at the time, and do some testing. May not be the best way. But I'm not aware of any other....

Jo Morg wrote:As for modules you can deactivate suspect modules, one at the time, and do some testing.

The problem is that this error is so intermittent and random that it would be hard to reproduce without hitting Refresh 1000 times in a row. But even that might not work. I guess I'll just have to give that a shot.

Would any kind of debugging/logging help capture the reason for the error, if it was noticed one day and the log immediately checked?

gocreative wrote:

Jo Morg wrote:As for modules you can deactivate suspect modules, one at the time, and do some testing.

The problem is that this error is so intermittent and random that it would be hard to reproduce without hitting Refresh 1000 times in a row.

I'm aware of that... specially because it seems this error only happens on hi traffic sites.
As for a debug setting, it's not a nice thing to have on, if the site is a production site with a thousand hits per hour or so... anyway I'm not sure if it will have anything on it, but you should check both the Admin Log and a file located at (siteroot)\tmp\cache\debug.log. Someone else may have a better advise...

Jo Morg wrote:... it seems this error only happens on hi traffic sites.

That's not the case for me -- all of the sites I've had it with are extremely low traffic, even those that I've literally just launched and no one has visited yet.

Anyway, thanks for your suggestions. I'll see if I can get to the bottom of it but I'm really hoping someone can identify the source of the problem as soon as possible.

Thanks for suggesting places to check. However there are no UDT's, plugins or 3rd Party Modules in my template that clear the cache. The only plugin that goes close is 'MenuManager' (after I deleted the suspect {cms_selflin rel=..} tag, rewrote SEOTools to SEOTools2 and removed any reference to HierarchyManager() or cache.

That just left the core software and a bunch of 3rd party modules beginning 'CG' and MenuManager

Calguy, please define

High traffic sites

- are you saying that CMSMS is not an option for sites that expect more than 2 concurrent visitors?

Has anyone had this error if they've had automatic cache clearing enabled? I've just set mine to clear after 5 days, to see if that makes any difference.

websupportguy wrote:Has anyone had this error if they've had automatic cache clearing enabled? I've just set mine to clear after 5 days, to see if that makes any difference.

Yes, I had that right now
Cache clearing interval is 2 days.

Maybe this is the cause:
http://dev.cmsmadesimple.org/bug/view/7259

Anyway, this should be resolved.

Cheers,
Alex

The ticket associated with this problem is now closed, but there was no closing comment to indicate how it was closed.

I have just had another site suffer this problem.

Can anyone comment on the final solution to this?