I am working on an older site running 7.26. I recently installed Page Title, and it works fine... until it doesn't. It will just stop working, placing an empty string in the page title. For instance, on a page that should be 'Page | Site' it will just put '| Site'. On the individual pages the page title field is present, but it is blank. If I flush the cache, everything will begin working again.. for about 30 minutes, when it goes back to this state.

This is not the first module that has done this for me, and the time frame is consistent. I have eliminated Cron as a factor (it only runs every day anyway). I have set my cache limits at every imaginable setting, and no difference. Currently they are at minimal: none and maximum: 15 minutes. While trying to get at the source of the problem, it appears the page title hook, page_title_node_load, is not being called. If I flush caches, it gets called fine for the next 30 minutes or so.

This has been going on for some time, and don't want to have to bypass this module as I have done with others in the past. Any help would be greatly appreciated.

Ryan Consylman,
Web Developer,
Visual Impact Group,
York, PA

Comments

VM’s picture

can this be reproduced on a vanilla installation?

rcons74’s picture

I have no idea. I've done several Drupal installations, one with the same host, and have never had a problem like this with them.

I'm not sure if this is relevant, but disabling and re-enabling the module also causes it to work again for this short time.

VM’s picture

the previous question is important. It will aid in figuring out if the problem is with the module and core, or some other variable within the environment ie: specific module combination.

rcons74’s picture

It cannot be reproduced on a vanilla installation on the same server. I will try exploring the modules, disabling certain ones and trying to find a culprit.

Any additional help as to where to look would be greatly appreciated.

rcons74’s picture

I have managed to isolate the problem a bit further, and would appreciate any guidance. It seems that the page load hooks are not firing after the cache builds enough. I have tested heavily for module interaction, but haven't been able to find a culprit, and the site really has very few modules as well as no custom modules. What could be preventing module hooks from firing when the cache is built?

Jaypan’s picture

Are your hooks in the .module file, or other files? If they are not in the .module file, then they will work when the cache is cleared, as most pages are included after a cache rebuild, but later on, the other files will not be included (unless explicitly included), and therefore your hooks will not be found.

rcons74’s picture

I finally found the problem and I wanted to post it in case anyone else runs into the same issue. We were given the task of simply making some updates to the customer's live site, but apparently the customer still had a staging site running from when the site was built. The staging site was a sub-domain of the live site, pointed to the same database, but had a separate code base that was about a year old. For whatever reason, many of the company personnel were using the staging site as the live site and regularly accessing various interactive pages.

The result of this was that when someone would access the site through staging, the cache was populated into the database from the staging code, missing all the hooks and features of any module installed since the site went live. When the caches were flushed, everything would work fine until the cache got rebuilt from the staging site. We were able to get the staging site information and shut it down, and now everything is fine.