Uwe Jacobs

OpenWeather is sun-setting the OneCall 2.5 API. Everyone who has a OneCall 2.5 subscription can still use it for a short time. Anyone who tries to subscribe to OneCall now must choose the 3.0 version – which is not free anymore.

WordPress deactivated OWM Weather because I had issues with the email listed at the plugin. In order to reinstate the plugin, I have to go again through the plugin verification process. WordPress sent me a long list of item I must fix before the plugin can be reinstated. Many of them passed the test when I started the plugin but seem to fail now. In addition, they want me to change library code like leaflet (map) that is included in the code.

With a heavy heart, I will retire OWM Weather, since I don’t have the resources for these changes. If anyone is interested in continuing the plugin, go ahead.

https://www.ujsoftware.com/owm-weather-blog/owm-weather-template-comparison/ has one full example for each template and they are seem to work.

You said to ignore this. So I marked it as closed and put a dash in the mandatory comment field.

Please update to 5.7.2.

Please update to 5.7.2.

The issue on your site doesn’t seem to be related to the API key. Everything looks normal but for some reason the Ajax call fails with a ‘parseerror’ for the JSON that WordPress returns. You can see that in the developer tools.
I have to further look into this.

I’ll look into that for one of the upcoming releases.

• This reply was modified 1 year, 1 month ago by Uwe Jacobs.

Can you share the url where table 3 or your template is not working?

The sunrise/set data will be corrected in the next release.

–

–

I didn’t realize that str_starts_with() is a PHP 8 function. I’ll fix it in the next release so that it will work with pre-PHP 8 systems as well.

OWM Weather 5.7.0 is now able to show historical weather information. Just turn on the Time Machine on the Basic tab of the Weather post and then set data and time.

Thank you for reaching out and suggesting this unique feature for the OWM Weather plugin. We genuinely value feedback and ideas from our user community as they help us improve and tailor our tools to fit your needs.

To address your query, currently, the OWM Weather plugin doesn’t support displaying static historical weather information for specific past dates. What this means is, if a visitor accesses an old blog post, they will see the current day’s weather rather than the weather on the day the post was created.

However, I’ve looked into the capabilities of the OpenWeather APIs, and you’re right. The One Call API 3.0 offers the potential for accessing historical weather data for the past 40 years. Taking your suggestion into account, I’m excited to inform you that we’re considering integrating this feature in one of our upcoming releases.

The OWM Weather shortcode initially places an HTML stub with a spinner on your website. Here’s a brief rundown of its operation:

1. The HTML stub triggers an Ajax call through owm-weather-ajax.js.
2. This Ajax call communicates with wp-admin/admin-ajax.php.
3. The server-side script then fetches the weather data from OpenWeather.
4. Once retrieved, it formats this weather data.
5. The formatted data is sent back to owm-weather-ajax.js.
6. Finally, the spinner on the website is replaced with the formatted weather information.

From the error details you’ve provided, there seem to be two primary suspects:

1. Caching Problem: Your site or hosting environment might cache the Ajax response, leading to outdated or stale data, causing the JavaScript error.
2. Security Restrictions: There might be a security rule, either on your website or hosting environment, that’s preventing the Ajax call from completing successfully. The 403 errors you’re observing are typically indicative of permission or access issues.

To address these:

1. If you’re using any caching solutions, try excluding the specific Ajax URL from the cache. This ensures that real-time data is always fetched.
2. Review any security plugins or server-side rules that might block or restrict access to the wp-admin/admin-ajax.php endpoint. You may need to whitelist this URL or adjust security settings.