Thinking through this a bit more, I agree you are right. BoltWire was designed for variables like farmPath and imgPath to have paths, while variables like farmURL and fieldURL to take URL's. Then when BoltWire needs paths it uses paths. And when it needs URL's it takes URL's.
Given this, and the number of broken plugins, you are most likely right we can't (or shouldn't) insert a URL into a path variable and expect things to work. I'll respond to your other post with the proposal separately. I have an idea. Cheers, Dan On Tue, Mar 23, 2010 at 4:03 PM, Markus Weimar <[email protected]> wrote: > It's probably simply a misconception that BoltWire can be run using > absolute paths. For example set $boltwire and you won't see a page. -- You received this message because you are subscribed to the Google Groups "BoltWire" 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/boltwire?hl=en.
