RobW

Greetings to all that are having problems with getting David's Weather Workflow to work on Snow Leopard. I have finally gotten it to work (e.g. type forecast and get weather data for the location you entered initially) on two separate Snow Leopard 10.6.8 machines. Having a working Mountain Lion machine (10.8.3) with Alfred 2 and the Weather Workflow installed as well helped understand the problem a bit better. On the working Mountain Lion machine, a settings.plist file was created at: ~/Library/Application Support/Alfred 2/Workflow Data/jdfwarrior.weather/ On both Snow Leopard machines, a differently named settings file - settings.plist.plist - file was created at: ~/Library/Application Support/Alfred 2/Workflow Data/ Removing the extra .plist from the settings file did not allow forecast to work properly, nor did placing it into the jdfwarrior.weather directory. After a number of trial and error tests, the following is what seems to work on Snow Leopard: In the .../Workflow Data/ directory, you need BOTH a settings.plist and a settings.plist.plist. The settings.plist.plist file is the file that has the current location and is the file that will be updated as you set your weather location. The settings.plist file needs to be there as a sort of initializer for other parts of the code to function properly, even though the data in that file is not used (though the data may still need to be valid structurally and otherwise). You can tell which settings Alfred is reading from if you open the file in a text editor and change the zip code it uses for look-up (e.g. change it from a Seattle zip to a Phoenix zip), then do a forecast and you will see different weather data than your area. Example below of what to change to see a different forecast for verification that Alfred is reading from the .plist.plist file rather than just the .plist file: Seattle zip in the .plist.plist file appears (in bold) on this line: <string>/q/zmw:98105.1.99999</string> Phoenix zip in the .plist.plist file appears (in bold) on this line: <string>/q/zmw:85004.1.99999</string> Hope that helps some folks and perhaps aids David in correcting the issue with his fine workflow. Cheers, Rob