CiviCRM Community Forums (archive)

My test site was recently moved to its permanent directory location (same server, same URL).

I updated various settings.php files, resource URLs, etc. Basically everything is fine except for one annoyingly persistent issue.

I'm using the cd_sunlight module with CiviCRM integration. It has stopped queuing new contacts for Congressional lookup (which happens during cron).

No errors are displaying in the log or anywhere; these contacts just aren't being queued for lookup of the Congressional district, so when Drupal cron runs, sunlight's cron has nothing to do, just as if there were no new users.

This worked totally fine before the directory change.  I have an issue posted for the module, but so far no resolution. The developer says there are no hard coded paths that he can think of.

I've flushed templates_c, Drupal's cache, and searched for a substring of the old directory path in the databases. Nothing has helped so far.

Fortunately the site isn't public yet, but only because of this.

Is there any little quirk of CiviCRM's that might cause a problem of this nature with an integrated module, or anywhere I might look for a clue? If not I will return to the cd_sunlight issues queue.

Thanks!

I don't remember, to be honest. It's been about 3 weeks.

I just gave it a go and I don't see that it fixed anything; in fact, now I get a WSOD when I go to search contacts without any filters set. I guess I should have asked first. 

As always I very much appreciate your help, Hershel. I followed your advice and it did solve the new WSOD problem. The query ran fine this time.

None of this seems to have made a bit of difference with the original issue, unfortunately.

I wish I could uninstall/reinstall all my CiviCRM-integrated modules during the CiviCRM reinstall, as that would be a better test and repair attempt, but I am afraid I'd lose too much.

I've been reading about a smaller issue I've been having with Secure Pages, new user registrations, and anonymous sessions, and I'm learning that a physical move can have some pretty obscure consequences that don't seem to be covered in any of the documentation I've read.