Saratoga WD & Base USA updates problem

Two problems in trying to update…

  1. checking for updates since 2017-11-01, one of the files listed for update is ajaxAWNwx.js . Problem is I don’t show this file as having ever been used before…I don’t find it on my host or in my file folder. Can anyone tell me what this is for? Do I need it? Should I just upload it to my server in the root directory?

  2. currently running version 1.02 of nws-alerts-config.php. This is the last of the updates I needed to complete…after d/l and configuration I uploaded to host. All I get then is a blank screen in the color of my background which in my case is black…switch back to 1.02 and all is well…any ideas what I’m doing wrong?

Thanks for advice and suggestions…

Steve www.bwsrh.com

I can “view source” of http://www.bwsrh.com/ajaxAWNwx.js - but I don’t what it is…

Thanks Niko…maybe if it ain’t broke don’t fix it !!!

Steve

…AWN looks like something weather network related, Atlantic maybe?

That latest update implemented support for Ambientweather. Just upload the entire package to your server root like you do for other Saratoga updates. Check the readme file to see which of the files, if any, need to be modified for your specific installation. if you don’t use Ambientweather then you can ignore the instructions to modify that file.

The ajaxAWNwx.js file is new with support added for using the Ambientweather.net site for data.

All the AJAX JavaScripts are included with the Base-* files and default customized for the default units (USA->Imperial, World, Canada->Metric) and that is why they are not included in the *-plugin distributions. And Don has it correct… if you don’t use that plugin, then just ignore the customization instructions.

This method of distribution (all the AJAX files in the Base) allows folks to easily switch weather software by selecting a different Plugin as all the parts are available on the site already. When you use the check-fetch-times.php?show=versions Version checker, it only assesses the current status of your Base and active Plugin and the update tool only offers the updates the same way.

Thanks Ken for the update…

any idea why I’m having problems with my nws-alerts-config.php - question #1?

Steve

Hi Steve,
Maybe I am not understanding the question/concern. I run a view-source of your site with ?mu=1 (to force an update of nws-alerts) and see

<!-- nws-alerts noCron=true .. running nws-alerts.php inline -->
<!-- nws-alerts.php - V1.42 - 27-Jan-2018 -->
<!-- 4 unique Zone entries found. Zones='MDZ012,MDC029,MDZ015,MDC035' -->
<!-- cache age 431 seconds - no fetch needed -->
<!-- manual update of cache requested -->
<!-- Cron job not used -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=MDZ012&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.52.160.34 port=443 (from sce=198.71.62.69)
      Times: dns=0.253 conn=0.286 pxfer=0.356 get=0.276 total=0.632 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=MDC029&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.52.160.34 port=443 (from sce=198.71.62.69)
      Times: dns=0.000 conn=0.033 pxfer=0.103 get=0.473 total=0.576 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=MDZ015&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.52.160.34 port=443 (from sce=198.71.62.69)
      Times: dns=0.000 conn=0.033 pxfer=0.103 get=0.283 total=0.386 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=MDC035&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.52.160.34 port=443 (from sce=198.71.62.69)
      Times: dns=0.000 conn=0.033 pxfer=0.103 get=0.214 total=0.317 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwacapget.php?x=MD125A97AEAF70.HighWindWarning.125A97CC5F70MD.PHINPWPHI.5ba873ff27dfe7ec8b805c908d647488 -->
<!-- HTTP stats:  RC=200 dest=23.52.160.34 port=443 (from sce=198.71.62.69)
      Times: dns=0.000 conn=0.035 pxfer=0.108 get=0.038 total=0.145 secs -->
<!-- Cache file updated: Thu 03-1-2018 11:49 am -->
<!-- Alert box data file updated -->
<!-- Icon data file updated -->
<!-- Alert logging enabled -->
<!-- Log file updated Thu 03-1-2018 11:49 am -->
<!-- Total process time: 2.0601 seconds -->

so the alerts are being fetched.

Clicking on the alerts in the top bar and the menubar does launch the proper detail display page.

So… can you elucidate the issue more so I can better understand?
Thanks!

Hi Ken…tnx…easiest way I can describe is when I have version 1.02 of nws-alerts-config.php in my host root directory, my web site runs just fine. If I upgrade to version 1.03, do the customization and upload to the root… going to www.bwsrh.com only gives me a blank screen the color of which is my background choice of black…nothing is displayed…no website can be seen at all…

go back to 1.02 and all is well…hopefully this explanation will help!

Steve

Ken…can u take a look at ur updated version 1.03

are u missing a
?> on line 123
// end nws-alerts-config.php

in my case diffmerge showed this in the comparison of 1.02 and 1.03
I added ?> to 1.03, uploaded it and all seems to be fine

Thanks

Steve

I’ve started to use the convention recommended by php.net to omit closing tags

If a file is pure PHP code, it is preferable to omit the PHP closing tag at the end of the file. This prevents accidental whitespace or new lines being added after the PHP closing tag, which may cause unwanted effects because PHP will start output buffering when there is no intention from the programmer to send any output at that point in the script.

Since nws-alerts-config.php is pure PHP, the closing ?> was deliberately omitted.

I don’t know why that omission would cause your screen to be blank as you described.

Thanks Ken…but for whatever reason if I omit it in this latest version 1.03, my website doesn’t work…I brought it as a carry over from 1.02 which did have ?>

whatever, I’m no expert but I would ask do u see me having any problems using ?> with ver 1.03 or should I migrate back to 1.02

Thanks for the help!

Steve

No issue with you adding back the closing ?> … it’s just strange that the omission (per PHP recommendations) causes the glitch in your site.

Thank you for your help Ken!

Steve