Since upgrading to the latest version, I am receiving this message site-wide:

Notice: Trying to get property of non-object in _weather_get_link_for_geoid() (line 218 of /home1/s3viking/public_html/drupal/sites/all/modules/weather/weather.common.inc).
Notice: Trying to get property of non-object in _weather_get_link_for_geoid() (line 222 of /home1/s3viking/public_html/drupal/sites/all/modules/weather/weather.common.inc).

The best I can figure is that there maybe a country listed as a non-string object. Any suggestions are welcome.

CommentFileSizeAuthor
#1 weather_Capture.PNG20.19 KBjvannuys
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jvannuys’s picture

jvannuys CreditAttribution: jvannuys commented
Issue summary: View changes
FileSize
weather_Capture.PNG20.19 KB
toddy’s picture

toddy CreditAttribution: toddy commented
Assigned: Unassigned » toddy
Status: Active » Postponed (maintainer needs more info)

Hi,

thanks for the bug report. It looks to me like the geoid of the weather place is not found in your database. Did you add custom locations to your installation? Which locations do you have configured for weather displays?

Regards,
Tobias

jvannuys’s picture

jvannuys CreditAttribution: jvannuys commented

Hi Toddy,

My custom locations are Jacksonville, Florida, San Diego, California and Washington, D.C.

I may have a couple of others, but those are what I am displaying on the front page and remember putting into a custom file. I did a review of the DB for weather_places and didn't see anything out of the ordinary, but it sounds like I need to check the custom file where these were typed in and/or add them to the DB as actual records. Does that make sense?

jvannuys’s picture

jvannuys CreditAttribution: jvannuys commented

Hello again. I have resolved my issue. I had a custom location that was wiped during the upgrade. I have added it to the table and the message instantly disappeared.

The location was http://www.yr.no/place/United_States/California/San_Diego/ in case there is enough interest to make it a permanent fixture in future upgrades.

I am considering this issue closed.

Thanks,
Josh

toddy’s picture

toddy CreditAttribution: toddy commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

Hi,

this was indeed the problem, glad it resolved for you. I'm planning to support adding custom locations in the near future, then those location should not be deleted after an update of the module.

Regards,
Tobias