World Weather Online stated effective April 5th they are no longer offering the free API. I’m hoping you can cross over to Google weather API for future use of your Weather component.
As I know Google Weather API does not exist for years now. But if you read the WWO’s statement carefully you can see that only the new registrations will be limited to premium API. Accounts registered before April 5th will still be able to use the free API. We will think about a way regarding new customers but it does not affect current users.
My apologies. I meant as I use this component in the future and purchase additional licenses. Your weather slider is hands-down the nicest one I have seen on the internet. Perhaps in the future something like forecast.io where you 1000 free API calls per day.
After the changes the free API offers 1000 calls per day according to WWO. But we will look for other weather data providers as well.
Whats new in the recent update?
You can find the changelogs in the documentation: https://support.kreaturamedia.com/docs/weatherslider/documentation.html#whats-new
No clue what’s wrong, but using your script as mentioned in the included documentation (applied for a API key and inserted it), but I get the message:
WeatherSlider Error: Timeout.
Please check your WWO API Key and plugin settings.
Using the latest version from your website (2.6.6).
Nevermind. Figured it out. Needed to change “WWOAPIVersion” to “2”.
So the language is still set by variables, not by a simple NL change or something?
I do have a general question. Is it possible to lower the weather icons (such as sun, clouds, etc)? I looked over the code, but I couldn’t find a way to do it.
Obviously I want to maintain the default weather background. I just want the weather icons (img) be somewhat lower.
Please let me know if this is possible and how. Thank you!
Thank you for the feedback. In case you’re using a free API key registered after November 2014 you need to set the API version to 2.
Unfortunately there is no option to change the size of the weather icons at the moment.
Ehr… I never mentioned resizing them. I want to lower the icons. In other words reposition it lower instead having them at the top.
It should be possible, but I don’t know where to change it. Please advice.
We’re sorry but there is no setting in the plugin for this either.
Weird, browsing through the .js file, there should be a way to do this. To bad you aren’t supporting this. Should only took you 2 mins. Lowering my rating.
Well I fooled around in the weatherslider.kreaturemedia.jquery.js and it is possible, however I don’t understand how it’s calculated.
You can change the height / location of the weathericons somehere here:
height : $(this).height() * ws.o.reduction,
marginLeft : (parseInt($(this).css('margin-left'))-ws.w[what].mL) * ws.o.reduction,
marginTop : (parseInt($(this).css('margin-top'))-ws.w[what].mT) * ws.o.reduction,
visibility : 'visible'
It should be possible to lower the weather icons in general.
Well apparantly by adding + 120 it will lower everything within.
For example like this:
height : $(this).height() * ws.o.reduction,
marginLeft : (parseInt($(this).css('margin-left'))-ws.w[what].mL) * ws.o.reduction,
marginTop : (parseInt($(this).css('margin-top'))-ws.w[what].mT + 120) * ws.o.reduction,
visibility : 'visible'
It’s really ackward that the developer didn’t know this. You would suspect he simply doesn’t care about his clients, or this script was partially stolen elsewhere??
IMHO a developer should have known this.
Thank you for your feedback.
Noticed an “issue”, every time I open the page with your weatherslider it adds to calls to the API. So instead of 500 calls, I can only make 250 calls, because it makes duplicate calls.
Is this normal? Or is there a workaround.
Maybe come up with kind of caching system like a few other weatherscripts out there. So it doesn’t make an API call/count every time you open the website.
Some kind of caching system would be great, because it will:
1. Make less API counts.
2. Make the website even faster.
3. People will adore it and give you a higher rating.
So in general your script will be the best looking and fasted one out there.
Hopefully you will consider this.
We have already implemented a caching solution like this to the WordPress version of WeatherSlider. It is a bit more complicated to apply it to the jQuery version as well but we are planning to add it to the script in the future.
Well I hope it will be added sooner than later, because I already hit my 500 API call limit today, because of the two calls each time. It shouldn’t be that hard to create, especially considering you have it already in the Wordpress version.
It would make your customers happier. So please include a caching system. Thank you.
As I’ve mentioned earlier adding this feature is on our to-do list. Unfortunately we are not yet sure to exactly which version will be this added to, so there is no date of arrival available yet at the moment.
Kreatura Support Team
Hello, I just purchased your plugin but just testing I ran out of credits in the first 3 hours. How soon can you implement forecast.io as an API provider within your plugin… if others have done it, so can you. they give you more free credits per day (1000) and their pricing packages can have smaller start up plans. Hope you can implement it soon.
Thank you for your thoughts, we might implement forecast API to the plugin in the future.
Please read my earlier response under your last comment.
On a normal day, the script stops half the day.
We really need a cache function, because every single day (except for weekends) I hit the query limit. Therefor I cache function is really required to make the best of your script. Not only will it be way, way faster, but also it will result in way less querries…!
I will keep bumping this thread as a friendly reminder and to keep your attention on it.
We do understand the benefits, that’s why the WordPress version already has a caching feature. However, we’re working on another big release, which currently requires our attention. I understand it’s important to you, but you can’t expect us to throw away everything and start immediately implementing this feature. Development takes time, and we have a schedule to follow.
However, I can offer you a halfway solution in the meantime. Due to the caching feature in the WordPress release, the jQuery version already has some hidden features implemented under the hood. You can pass a property called ajaxURL in the plugin init settings. This way WeatherSlider will not try to request data from WWO directly, but rather call a local URL with the location and service parameters in the query string. This gives you a chance to implement your own server-side caching and data handling mechanism. The returned data must match with the one that WWO uses. The service parameter can be either ‘weather’ or ‘timezone’, which refers to the corresponding WWO API method.
I know this isn’t an out of the box solution, but any developer can easily and quickly implement a back-end script for you if caching is really that important on your site. The reason why we didn’t release anything like this yet is due to the lack of universal way to do it. On a CMS platform (such as WordPress), we know exactly the server and software environment and we can make it work automatically without configuration. However, the jQuery version will be used on custom built sites, where we can know nothing about the web server, database, data handling, etc, thus we can’t provide a universal and out of the box solution. Except if we use client-side caching, which achieves little and doesn’t really solve the problem.
I hope the above method will help in your situation. We will come up with a better solution eventually, but in the meantime I would like to ask you to stop flooding the message board with the same message over and over again. We’re working as fast as we can, and this feature will be implemented in a future update.
Kreatura Dev. Team
Obviously this isn’t a real solution, especially considering I am no developer or whatever. If I was, I wouldn’t have purchased this script and created something of my own…So I have no clue on what you mean or how to achieve this. You might as well have spoken in Chinese or Japanese; it would have provided the same outcome…
In regards to your answer and I quote:
“However, we’re working on another big release, which currently requires our attention. I understand it’s important to you, but you can’t expect us to throw away everything and start immediately implementing this feature. Development takes time, and we have a schedule to follow.”
I fully understand that you cannot listen to your buyers and provide them with everything what they ask… Also it seems you are always working on a big (Wordpress) release. There is really no progress at all for the regular users.
The need for a cache function was already mentioned over 1 year ago!! You even replied to this user and I quote: “In the next update we will consider to add some kind of local cache to avoid situations like this.”
I think the issue is more that you don’t care about non-Wordpress users at all, because the only updates I see are for the Wordpress version…
Anyways, I will keep bumping this thread every now and then, because I am growing tired of waiting. The function was requested over a year ago already, so I think I/we have been pretty patient so far.
In the meantime I will enjoy <not> my personal page which doesn’t show the weather as the limit on queries has been reached again for today (just like it almost happens every day).
If you aren’t able to support several similar projects at once, why do you sell your script at all…? Just drop the regular version completely already. It would prove that you really do not care about the regular version and are only biased to Wordpress users…
We aren’t biased to WordPress users. I’ve already explained the technical details why it’s hard to add a feature like this to non-CMS sites. There are no standards to follow. We have no way of knowing about your server environment. There is no API to make this automatic without configuration.
Even when we implement a caching feature in the future, it can never be fully an out of the box solution. It will require some degree of web development experience to configure it the right way. There are technical barriers that nobody can avoid.
This applies to other WP features as well. There is a reason why we can or cannot do certain features on a given platform.
Also, if you use geolocation to provide the users their own weather forecast, then the caching feature might not help a lot. Depending on your site’s traffic, it’s entirely possible that you would need to subscribe to another API plan in either case.
Furthermore, I hope you realize that you’ve bought the item “as is”. Every feature that we advertise is working properly. We do care about user feedback, but there are some situations we simply cannot solve remotely for everyone. The jQuery version does require some web development experience, especially if you want to add/use extra functionality. It’s another matter for a CMS plugin/module where we have solid ground to build on, but we cannot make something to work with the unknown.
Well given the amount of “massive” updates for the Wordpress version, I have a hard time believing this.
A cache function should be this hard for an “experienced” developer like yourself. I am using RSS feeds on my personal page (it’s called MagicParser) and it also has a very simple cache function. As far as I can understand it (I am by no means a developer) the procedure is simple.
If a cached feed is younger than 5 minutes than it will not update. If the feed is older than 5 minutes it will fetch the RSS feeds. I have set a up a cron job to make it call the fetch-feeds.php every 10 minutes, so the servers from which I collect the RSS feeds don’t get hammered and I don’t get banned. FYI MagicParser is over 10 years old and it has a cache function. So I really do not understand why this should be so difficult for you to include something like this.
And in regards to traffic to my page; I already mentioned more than several times, that this is my own personal page. The only traffic to this website is from me, my girlfriend and a few family members. My personal page is my starting page which features news, weather (which runs out of querries obviously and thus becomes completely unusable) and favorite links to websites and work related links.
Apparently you are ignoring this, because I have mentioned this before. Furthermore; I am not the only one who asked for a cache function of some kind. Several other users also asked for this several times. But apparently there is always a big update lurking on the corner and/or it will be a feauture which will be included in the next update… Well we did have an update after the question was asked for the first time, but it was never included.
I already disabled the geolocation lookup, because it was so terribly slow. I now only use a few locations (I think just two).
Anyways, I will keep this alive by bumping the thread every now and then.
The geolocation lookup should not be slow, since we’re using the Google Maps API, which should be fast and reliable.
You don’t have to prove the importance of a caching feature, but I’ve already explained why it is difficult to implement it with the given circumstances. This is why we use words like “consider” or “plan”, since we might need more time to find a universal way implementing it.
There’s many types of caching. It could also be client-side or server-side. The former can be easily achieved, but it’s effective only in very narrow situations. A server-side solution would be similar to your example, but it would still require configuration, and the actual implementation would vary depending on a lot of factors.
What you should understand is that the actual implementation isn’t hard, but making it universal and to work out of the box is borderline impossible without a known environment or API. In English that means that the coding part isn’t the problem, instead we literally don’t know what to code for. We would have questions like:
- Does the target site uses PHP or another language?
- Does it have a database? If so, which DB solution it uses?
- Does it have filesystem access and proper permissions set?
- Does it have enabled network functions, if yes, which one should we support?
- ... et cetera
In contrast, WordPress has its own server requirements, so every WP website will use the same server environment and it provides a stable API, which bridges the gap between sites. Again, a custom built script is not a problem, but it won’t work on any site, and we could not even write one without knowing how your site is built. We could certainly make an example file, but some level of web development knowledge would still be required.
Please also keep in mind that jQuery plugins are not designed as full featured server-side solutions with user interface. It in some extend a developer asset, that users with experience can extend and modify for their own needs.
I hope this provides enough insight to understand why it is so problematic add a feature like this in a client-side script. Client-side means that it runs in your browser, so it has no access on its own to your web server.
We will try to add a PHP script similar to your example as soon as we can, without needing an awful lot of configuration. In the meantime I would like to ask you to consider our reasoning and try to be more understanding, as it is a technical barrier and is not about our willingness to help.
Maybe something like this can help or provide insight to a working caching system…?
Though it’s for something else, maybe you can get an idea from it…?
Thank you for the link, however it does not really fit our case.
In the meantime we have put together a cache extension that contains instructions and you can use it as an example. If you write us an email from our profile page we can send it to you.
Sorry that my link didn’t help you.
Okay, that’s great news! I will send you a message. Thank you once again.
Wow the cache function really works perfectly! Hardly any API calls anymore and (in my humble opinion) my page now also loads faster!
10+ for customer support and for the cache function. I can highly recommend this script to anyone who is still in doubt!!!
Thank you for the feedback and your kind words. We have also replied to your email.
Hello, i’ve purchased your Plugin and it works well so far. But is ist possible to change the api by my self?
I want to use the openweathermap.org api, because there is still a free account avaliable.
Unfortunately there is no option in the plugin to change weather data provider at the moment.
Thanks for the quick answer,
do you work at a solution for this? Or maybe change the standard weather provider soon?
Am I allowed to change the code by myself to insert a settings option for a second api provider?
We are also thinking about changing weather providers, we will look at our options and decide what’s best.
Yes, you are allowed to make these modifications to the script in the meantime if you would like to.
Got the API key as per your instruction mentioned in Documents, but we are getting this error: Timeout. Please check your WWO API Key and plugin settings.
Usually these issues are related to the WorldWeatherOnline API and your own API key. Please verify at your WWO profile that the API key is working and valid, please also check that you have set the proper API option and you entered the key correctly.
It is also possible that there is a temporary issue with the WWO servers and that is causing the trouble, in which case it should return to normal shortly
I just purchased this without seeing the disclaimer about the premium API. Where do you stand on another weather provider? This looks like a great weather widget, but if I have to pay $10 a month to use it, I will probably look for another alternative. It’s my fault for not reading all the info before purchasing.
We are planning to switch to a different weather data provider as we’re not completely satisfied with WWO’s services recently. However our other projects are keeping us busy at the moment so we’re not yet sure when will be able to make this change happen.
haven’t you tried https://openweathermap.org/forecast5 for API? Their only limit for api is maximum 60 calls per minute what is totally irrelevant with caching. They offer 5 days forecast, segmented every day by 3 hours and weather updates every 2 hours. With a cron job and saving json locally everyone can work on free API. I compared JSON objects returned from both, there are quite big differences but I think it is worth of it since world weather free API is just a 60 days Trial, after trial is your plugin useless, unless you open new account and start new trial.
Thank you for your thoughts and feedback, I am going to forward your idea to the devs so they can check on this API provider.
Use, by you or one client, in a single end product which end users are not charged for. The total price includes the item price and a buyer fee.
Use, by you or one client, in a single end product which end users can be charged for. The total price includes the item price and a buyer fee.
View license details
Get it now and save up to $3
Power Elite Author