You're right, this is a useful warning. Turns out it wasn't coming from my app. I load WEBLOCKS-CLSQL-DEMO with my app, and that's the source of the warning. Minor bug, worth fixing?
Thanks, -Keith On May 14, 2:39 am, "Leslie P. Polzer" <[email protected]> wrote: > Keith M. Corbett wrote: > > > I'm using weblocks-dev, and I've been using the same sources since > > about mid-March. Recently I pulled updates from the repository. Now I > > get this warning when I start my web app: > > > ; Warning: Couldn't determine application's public files folder, using > > standard Weblocks files. > > ; While executing: (WEBLOCKS:COMPUTE-WEBAPP-PUBLIC-FILES-PATH (T)), in > > process Hunchentoot worker (client: 127.0.0.1:58814)(6). > > > I don't see any other sign of trouble. Static content in my public > > files directory is still served as expected. > > > What does this warning really mean? > > This just means that you do not have designated the public files > folder for your application. Weblocks will fall back to its vanilla > stylesheet and script collection. > > Not a bad thing of course, but in some cases it's useful to get a > warning about that. > > Leslie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
