On Mon, Mar 23, 2009 at 4:34 PM, DrunkenMonk <[email protected]> wrote:
>
> First there is a problem with the boltwire path, which causes a blank
> page.
>
> It seems the farm folder isn't found correctly just by using
> $farmPath, I got it working on a test copy by using $boltwire, but it
> required that I had farm under $boltwire/farm. I'll be hollering if it
> turns out that this is an actual bug and not just something wierd.
At some point, there was a slight change in the directory structure.
That could require you to manually define the $boltwire variable to
get things hooked up right, and possible other vars if you have a
non-standard installation.
> Once that works, my $$actions is a vertical list, and there were
> problems with the skin. But that was all just my tinkering. I'll get
> through it eventually.
There was some desire to see the actions be an actual ul list, but
that requires additional css in the skin. I think these lines will
likely do it:
.actions ul { margin: 0 0 0 -3px; padding: 0; display: inline; }
.actions ul li { margin: 0; padding: 0 5px 0 5px; display: inline;
list-style: none; }
.actions ul li+li { padding-left: 5px; border-left: 1px solid #999; }
Note also that code.skinvars was renamed to code.snippets. So if you
have custom skinvars, they should be copied over to the new location.
> Oh! While I remember, is there a reason the source action isn't in the
> default $$actions list?
It should be there. I see it in mine and in the default code.snippets page...
> Also, currently multiple versions of boltwire will share the same tmp
> folder, with the interesting effect of sharing logins. Now, I use the
> same password since I'm testing, but I find it weird and irritating
> that the logins overlap and cancel each other out.
I don't know that this is normal... Normally each one has a unique
login key, based on the field name. You could try setting manually in
site.config
fieldKey: uniqueid
If it interferes with your logins, just delete it. I don't think it's
used in the login encryption scheme. Just defines where in the session
array info is stored.
>> The second savedata line overwrites the first one. Change the last line to
>
> See, I could kiss you. Thats mentioned in the docs as well, of course,
> but I didnt think of savedata as a session command.
I usually leave the kissing to my wife and daughter. Thanks for the
offer though! And glad it helped. I think you'll be glad to get the
upgrade completed. The only remaining changes in going to 3.xx should
be under the hood, though some plugins could be affected. And then I
plan on taking a long break from pioneering. Just fixing little bugs
and improving the docs here and there. That kind of stuff. Just using
BoltWire. I think it's pretty close to done.
Cheers
Dan
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
