releaf

I was able to resolve my issue by commenting out the part of the javascript that was using the geo.placefinder, combined with a zip code, to find the WOEID. I too hardcoded the WOEID into place and it now works.

var weatherUrl = '//query.yahooapis.com/v1/public/yql?format=json&rnd='+now.getFullYear()+now.getMonth()+now.getDay()+now.getHours()+'&diagnostics=true&callback=?&diagnostics=true&env=store%3A%2F%2Fdatatables.org%2Falltableswithkeys&q=';
			// if(options.location !== '') {
			// 	weatherUrl += 'select * from weather.forecast where woeid in (select woeid from geo.placefinder where text="'+options.location+'" and gflags="R") and u="'+options.unit+'"';
			// } else
			if(options.woeid !== '') {
				weatherUrl += 'select * from weather.forecast where woeid=2372071 and u="'+options.unit+'"';
			} else {
				options.error("Could not retrieve weather due to an invalid location.");
				return false;
			}

I’m also experiencing this issue since updating my WordPress version.

I’m also seeing this behavior.

I was able to get around it by creating a normal text field and then assigning it a class that sets it to display:none; However, that defeats the point of this plugin.