I upgraded to the latest WD Carterlake AJAX scripts and now get an error in my advisories. I read all the updates for the new NOAA reporting and have setup my atom-advisory for my zone and created the atom-advisory-zone.txt and that appears to be working properly as NOAA information is in the new file. If you use my atom-advisory.php you will see I get a return of “Advisory Information Unavailable, error fetching or reading data from the NOAA advisories server.” Here is the link to my atom-advisory file. http://www.rdoghouse.org/homewx/atom-advisory.php?WAZ510
Yes and No, the information from NOAA is making it to atom-advisory-WAZ510.txt but no new information has been cached in the rss-advisory file since I upgraded yesterday. Also reading the notes it says I can delete that file and just use the new 2.0 feed now. I deleted and created a new atom-advisory-WAZ510.txt and it filled with NOAA advisory information just like it should, you can see it here. http://www.rdoghouse.org/homewx/atom-advisory-WAZ510.txt
Thank you, so what I did was copy over the atom-advisory.php and atom-top-warning.php and did not change any settings in them and it works. If go in and set the Zone and CacheName it will do the same thing again. This makes no since to me at all.
You don’t need to make any changes to atom-advisory.php or atom-top-warning.php (especially not the $cacheName) … the settings are picked up from your Settings.php so the scripts just plop into the template for usage.
The cache name (in $cacheName) should never be changed manually… it’ automatically changes the ‘atom-advisory.txt’ in that field to ‘atom-advisory-ssZnnn.txt’ for the selected zone. If you changed it, then when the script runs, it will try to write to ‘atom-advisory-WAZ510-WAZ510.txt’ (which probably fails).