Possible problem with Canadian data

Events happening in the community are now at Drupal community events on www.drupal.org.
Patricia_W's picture

I'm getting errors in the Drupal log which may be related to the fact that the addresses I am using are Canadian. The site is using CiviCRM 4.2 and Drupal 7.14

I get a bunch of errors like this:
Notice: Undefined property: CRM_Core_DAO::$coy.name as country
Notice: Undefined property: CRM_Core_DAO::$ste.name as state_province ...

Is there something special I need to do to resolve this?

I've also noticed that some errors in the error log seem to be related to the drop down list of Employers for a Contact.

Has anyone any experience with these problems? The site appears to be working correctly except for these errors in the Error log but I would prefer not to have to wade through these errors to see if there are other more serious ones.

Comments

notices

adixon's picture

well, in general, civicrm is not 'notice safe'.

In other words, lines beginning with "Notice:" are things that php notices that it thinks might be an error in your code, but it's not so bad as to interfere, and it might even be okay. Like using uninitialized array keys (long ago are the days when php was the king of cowboy code ..).

Drupal 7 is notice safe (in theory, not always for contrib modules), but CiviCRM hasn't caught up yet. Some of this may depend on the php version you're using as well.

Conclusion:
1. don't worry about the "Notice:" lines if they're civicrm code.
2. employer list errors - might be a different issue.

Thanks for the quick response

Patricia_W's picture

It is reassuring although I hate to see notices like that. A problem that I was having (which I thought might have been related) was trying to get rid of the employer that comes with the initial install (InnerCity Arts). I've browsed for an answer to that and could not.

initial install?

adixon's picture

There's no innercity arts with the initial install unless you choose to prepopulate your database with test data. I wouldn't do that on a real install.

Getting rid of an organization which is used for membership will cause issues, for sure.

Patricia_W's picture

I don't remember installing the test data but obviously I did. But what if this was true production data and I wanted to get rid of an organization ... surely there is a way to do so. It says it is in use but I can't find out where.

getting rid of an organization

adixon's picture

yes, you can get rid of an organization. CiviCRM should provide some guidance if you try and get rid of it and it tells you it can't. But the first place i'd look is in the membership type list. Membership types are always associated with an organization (a bit weird for most users), so if you edit those memberships (delete, change the membership org) then you'll probably be able to get rid of those organizations.

On the other hand, this sounds like a symptom of a bigger problem. Your constituents are probably more valuable than your website, so a quick hack to get going is not a good long term strategy.

Civicanada

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: