The window the gauges display in needs the height increased slightly. Where is the setting for this?
I’d like to move the scrolling Davis forecast from the lower right to the top and centered. Where is this code located? Since I increased the size of the gauges, it’s no longer visible.
I have graph popups enabled but they’re not showing. What files need to be uploaded from WD for them?
Both 1 & 2 can and will use the available graphs, as you can see yourself. For all weatherprograms which deliver clientraw the same graphing routines are used.
But number 3 runs in an iframe. Its height is resctricted and NO graphs can be displayed as they will be chipped (? correct Englis?).
An iframe wil not show anything outside the iframe and the grpahs are larger or wider then the iframe.
I think this will answer point 3.
No graphs possible inside the header.
If you visit to my own weather website, http://www.weerstation-wilsele.be/ you will see that I use a low header and the x-small version of the steelseries on the top part of my start-page. There the graphs can be shown.
===
Question 1:
The height for the iFrame the steelseries script runs in is set at line 52 in weather27/wsHeader3.php
Question 2 :
The steelseries-script used in the header is weather27/ws_gauge_frame.php
All steelseries scripts used in the template are more or less the same.
In this case the code should be found at line 96-103
Thanks, Wim. That was exactly what I needed! Although I did leave the scrolling forecast at the bottom, but centered.
The graphs I had mentioned are those that pop up when the mouse cursor is placed over a dial. I’m not getting those. I get the text in the balloon but not the graph.
They should be inside the pop-ups at all the other steel series parts of your site.
They can not be displayed in the header pop ups as the pop-ups would not fit inside the iframe then.
So in the header only the text can be displayed in the pop-ups as they are lower/smaller and fit inside the iframe.
So I do. I was so fixated on my home page that I didn’t notice that. Somehow Wim has those gauges on his home page. I’m forlorn with envy
One thing I’ve noticed with everyone’s wind speed gauge is that on the balloon shows ‘undefined’ for the direction (N, NNE, etc.) but the latest gauge is correct. It must be a script error with that gauge. No idea where to look.
I see what you mean, at the end of the text in the wind speed gauge mouseover the Bearing is stuck on 359 and the text direction is “undefined”. That’s the same on Wim’s demo pages, but in his mystery special header it’s working OK.
=== @niko no “owner’s reserve” special things @all no beta testing of new features, my own site lags behind on purpose to have an old release testbed.
Differences:
I am using header1 WITHOUT gauges, my gauges are displayed on the large main part of the page of 1040 pixels wide * 1400 pixels heigh.
You are using header3 with an iframe in which the gauges are displayed. That iframe is only 180 pixels heigh.
All gauges can display the graphs, default they are set to on in wsStartpage and page 25.
In the header3 they could be displayed also BUT they would not fit inside the 180 pixels height of the iFrame and only partially shown. Very ugly and that is why the display of graphs is switched of in the header.
You can test yourself by going to one gauge in the header until the text pop-up is shown.=> slowly move to the top of the gauge, the pop-up also moves upward AND the text is suddenly partialy clipped. When the graphs would display also the pop-up would ALWAYS be clipped.
If you want the same layout as on the Wilsele page (only gauges in the main part of the page):
Script: http://m82a1.us/weather27/wsStartPage.php?sce=view
Change line 52 by removing the comment mark
Move that uncommented line to line 31 which is empty now and is the first line to be displayed
Change your wsUserSettings.php line 188 from
$SITE['header'] = '3';
to
$SITE['header'] = '1';
========
The mystery header is explained above.
There are always differences between the releases and between the output for the 12 supported weather-programs.
My own website is a mix of 2.6 and earlier scripts which uses separate realtime tag files for every “realtime” script.
The demo pages are release 2.7.
Starting with release 2.7 there is no separate “steelseries” tags-file uploaded. Only one realtime file is needed. And for WeatherDisplay the clientraw file is used.
I checked release 2.8 beta also, the same error is there and also for multiple weatherprograms. I did put it on the ToDo list.
@ALL
Important: To adequately help users there are a few prerequisites which speeds up things considerably
An URL to the page with the problem
Debug should be available by default or by using &debug
Settings should not be PW protected (or password should be mailed / PM)
The printSite program should be available in the menu, but it can be hidden as long p=0000 is available.
And it would be helpfull if you checked :
5. all updates from the support page if it is a known problem/solution
6. the demosite for your weatherprogram if it has the same behavior.
As an example (and maybe to learn some new things) lets check these helpfull prerequisites against this support request:
Settings are not protected, but that does not help as printSite is not available in the menu.
Debug is already switched off, why? Are you totally finished? With debug still on, a lot of extra information is displayed inside the html.
Not OK, so I have to scan previous postings => This is the page with the probelms: http://www.m82a1.us/weather27/index.php?p=25&lang=en#data-area
When you try to pinpoint the problem, it is easier to always use the “smallest” page possible. The start page also contains the gauges, but also a lot of extra code.
================== Hope others will benefit from the text above also.
Back to @mldenison
Your problem:
The inside humidity seems to be invalid (see nr 2 below) . Inside humidity is a slow changing value => used from the general tags file, not from the realtime file
1.1 default tags-file for WD is tags.wd.txt and uploaded by WD as tagsWD.txt
1.2 That file is not available at your site as you are using testtags.php for Saratoga as input file.
You can use Leuven or Saratoga when you start testing the Leuven Template, but it is advised not to use for production as not all fields are compatible
Normaly I could check the input testtags.txt versus the uploaded testags.php but you are mixing Saratoga and Leuven testtags files here. http://www.m82a1.us/weather27/printSite.php?compare&pw=#data-area
The realtime values as displayed for the gauges are loaded in the correct language and UOM’s with http://www.m82a1.us/weather27/ws_realtime.php?wp=WD?lang=en&wp=WD
Checking the returned file: Inside humidity has a empty “inhum”:“”, value Why?: Not all supported weather stations <=> programs supply an inside humidity.
There is a check in the realtime data part to supply an empty value if $ws[‘humiInAct’] is not present.
So it seems that inside humidity is not present when the normal 5 minute tags are uploaded, in your case testtags.php
If you do not want to upload those files: change line 182 in www.m82a1.us/weather27/ws_testtags.php?sce=view (which is now empty) to
$ws[‘humiInAct’] = ??? ;
You have to find the tag for inside humidity in your testtags file, I could not find that one.
If 1 and 2 are not wanted: remove the selections for inside/outside humidity on the steelseries page
In the future, I’ll turn debug on before posting a question.
The printSite utility page is quite informative.
It is somewhat of a challenge for me to get everything set up correctly being my first website. Another guy did most of the installation and setup for me 3-4 weeks ago. Since then, I’ve been trying to tweak it to my liking. Being 72 years old, some things are challenging.
The problem turned out to be that the tagsWD.txt file was set to upload as tagsWD.php. Also. the setting was on to use testtags.txt.
