Ken.
I'm just curious as to why wxgraphs.php is part of the base-templates and not part of the saratoga weather station plugins?
wxgraphs.php is not supported in meteobridge, yet it is a requirement to update the file as I get out of date warnings in the check-fetch-times.php?show=versions and wxstatus.php urls.
Just curious....
When I developed the template set for V3, I decided to start with a fully-multilingual version (World) that would share the majority of the code with the Canada(en, fr) and USA versions(en) so common scripts and wx...php pages would be the same across the base distributions -- only country/region specific scripts would be included in the respective bases. Just made it easier for me to maintain fewer disparate scripts.
For wxgraphs.php, it was always intended to support all the plugins that were capable of producing graphs and it's the same script for all the Base distributions. The only exception was with the Ambientweather.net (AWN-plugin), where it was so different, I put a wxgraphsawn.php page in the AWN-Plugin to distribute it. On hindsight, I probably should have added that to the wxgraphs.php, but it's structure made it much more complicated to merge in.
You're correct, Meteobridge doesn't produce native graphics nor the .json files (like CumulusMX), so in the flyout-menu.xml, the menu option is automatically turned off (by having the wxonly= attribute missing MH or MB entries). The version checker considers wxgraphs.php to be a 'core' file, so does check for a current copy.
Hope that helps explain my rationale for using one wxgraphs.php to serve all Base and Plugin types (where possible).
Best regards,
Ken