Scanning the HTML directory is something I considered a long time ago, but, as I recall, rejected it because it would require special knowledge of which files should be included in which dropdown list. The scanner would have to recognize patterns like YYYY-MM and YYYY. It started to get too complicated for the small, incremental benefit, so I dropped the idea.
In the case of the Seasons skin, one simple solution is to change titlebar.inc so that instead of populating the drop down list with just the contents of $monthYear, it augments it with the extra files. But, that would have to be done on a case-by-case basis. Other skins would have similar solutions. -tk On Wed, Dec 18, 2019 at 5:39 AM Andrew Milner <[email protected]> wrote: > the OP said he already had the reports, and implied he just wanted to be > able to view them. > > I was thinking along the lines of naming the files ...txt just as they are > now in the NOAA dorectory. Unless weewx has changed the way to view these > NOAA reports was via a selector control on the html page and the selector > control was populated by cheetah. I assumed it was using a directory > listing to generate the linkages in the control to the actual .txt files > and o just adding more .txt files cheetah would be none the wiser as to who > had created the .txt files in that the naming convention would match those > created by weewx. No need to browse the directory - just use the selection > control to view the selected file. > > have we got our wires crossed perhaps?? > > Andrew > > > On Wednesday, 18 December 2019 14:14:55 UTC+2, Thomas Keffer wrote: >> >> It doesn't work that way, at least, not now. The problem is that if you >> drop the files into the HTML directory, WeeWX has no way of knowing they >> exist, and, due to security reasons, browsers are not allowed to, well, >> browse webserver directories. There are ways around that using PHP or >> Javascript code running on the webserver, but you'd have to write that. >> >> The only other option I can think of is to create a special subdirectory >> in the skins subdirectory that holds old files that are to be copied over >> to the HTML directory by the CopyGenerator. Then WeeWX could detect them. >> >> As always, PRs are welcome. :-) >> >> -tk >> >> On Wed, Dec 18, 2019 at 5:06 AM Andrew Milner <[email protected]> >> wrote: >> >>> if the files are named in the same way as standard NOAA files the surely >>> cheetah will think that it 'might have generated' them and so include them >>> in the drop down?? >>> >>> >>> >>> On Wednesday, 18 December 2019 13:11:09 UTC+2, Thomas Keffer wrote: >>>> >>>> That's correct, except that the WeeWX Cheetah code knows only of the >>>> files it has either generated, or might have generated. It has no way of >>>> knowing about new files that have been dropped into the directory. You'd >>>> have to write some custom Javascript code to do that. >>>> >>>> -tk >>>> >>>> On Tue, Dec 17, 2019 at 11:15 PM Andrew Milner <[email protected]> >>>> wrote: >>>> >>>>> have you tried just putting the reports into the NOAA directory and >>>>> naming them in the same way as the weewx NOAA files?? It should work I >>>>> would have thought - the drop down is populated by cheetah when the >>>>> archive.html page is generated I think. >>>>> >>>>> On Wednesday, 18 December 2019 07:20:12 UTC+2, peter wrote: >>>>>> >>>>>> I have NOAA reports from other software I was using before switching >>>>>> to weewx. Database contains only “fresh” data and not the data from >>>>>> previous software. >>>>>> Is it possible to include the links to ma old NOAA reports into the >>>>>> “archive.html.tmpl” page automatically? I’m using neowx skin. A >>>>>> workaround >>>>>> is to manually put the links into the template file. >>>>>> Thanks. >>>>> >>>>> -- >>>>> 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]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/weewx-user/466e010b-77dc-44ab-9f01-80031910a769%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/weewx-user/466e010b-77dc-44ab-9f01-80031910a769%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>> 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]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/8e5bd1ec-1a38-4a45-ae62-66ece80674ab%40googlegroups.com >>> <https://groups.google.com/d/msgid/weewx-user/8e5bd1ec-1a38-4a45-ae62-66ece80674ab%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/d4d23608-c9e6-4b33-955e-1105d7564342%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/d4d23608-c9e6-4b33-955e-1105d7564342%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEDsLLmu2PH08V3vi82pceirsgA8f93qaRpqfmb%2BNDyBeg%40mail.gmail.com.
