Ahhh, I compared the conf files and found what happened. I do not use [[StandardReport]]and have the section commented out. The upgrade added it back without commenting it out. That, of course, caused the website to be completely changed. No real issue as it was easy to recover from, just wanted to point out that it did change my conf file and that did change the website. I'm using Weewx-WD to provide the data for a Saratoga templated site.
I shall look to see if I can spot and make a correction for this in setup. If so, I'll do a pull request. On Thursday, August 16, 2018 at 5:00:44 PM UTC-4, vince wrote: > > On Thursday, August 16, 2018 at 1:53:55 PM UTC-7, G Hammer wrote: >> >> It would be nicer if either this were corrected or if the upgrade guide >> had a warning in it. >> As there were no program changes in weewx.conf, I just moved the 3.8.1 >> version back in place and wiped the web of all files. >> The scheduled ftp put the site back to the desired state/look. >> >>> >>>> > Hmmmm - I did a 'setup.py build' and 'setup.py install' to upgrade mine > and there was no ripple at all. > > One thing I do that might be helpful as a risk prevention thing is change > the location that the Standard_Skin writes to, so while it still runs, my > actual site uses my modified local skin. You might want to think about > that as a risk prevention thing... > > [[StandardReport]] > skin = Standard > HTML_ROOT = public_html/Standard > > # units entries omitted for brevity... > # units entries omitted for brevity... > # units entries omitted for brevity... > > [[my-local]] > skin = my-local > HTML_ROOT = public_html > > > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
