> Anything I can fix? Or did you just not have a field style page? Most
> people shouldn't have problems upgrading unless they are relying on
> the core code.style page. One fix is to quickly open and save that
> page before upgrading. Same with code.skin. That way nothing is lost.
I upgraded very late yesterday, and I don't remember exactly where the
problem was. The [[main]] div was being put under the [[side]] div.
The side div was wider than I wanted it anyway, and I may have fixed
it by editing widths... I forget.
I suggest we wait to see if anyone else has this problem (line break
between side and main div, putting main below side), since it's
probably my site and this upgrad specific.
> There's accent_color, but we could add more. I just found these four
> to cover most of the stuff in the skin. In fact, all the colors used
> in the skin.
the || text || markup uses highlight. Or, rather, uses a fixed yellow.
I called it highlight_color and added a line in action=skin
If that is not configurable, then highlight will be worthless for
light text colors. I set it to silver. Looks nice on the black
background.
> I've been having exactly the same need, though I'm not sure how to do
> it. Generally, I open two or three browsers. I'm thinking of some kind
> of preprocessing hook or something that allows a super admin to add
> login=someid to the url of any page and have it temporarily give you
> the permissions of the id. But it won't work right on form
> submissions, because technically they are processed as part of the
> next page. And the login get var won't be in the url. Perhaps there's
> some other easy way to do it. I dunno.
I would be happy with being able to put myself in a group and actually
using this to test permissions. I suggest adding
if( $BOLTuseadmin )
before testing if BOLTid is in BOLTadmin in BOLTauth
Then, we need a custom check to see if we are in BOLTadmin, in order
to a) show a toggle only for super-users and b) use a toggle only for
superusers
I suggest a function checking BOLTid in BOLTadmin, and if true
outputing a neatly formated interface to a toggle session command,
which again checks permissions in the same way. Maybe there's a
cleaner way to do it.
... Anyone want to start looking at incorporating ajax into boltwire?
I'm getting tired of the constant page reloads :p
> >> * Escaped snippets in the form of $$page:mypage to prevent a strange
> >> glitch in skins.
>
> > Oooh! reminds me. How do I get an info variable without processing
> > it's markup? My slogan is a [(quote)] command, I whish to be able to
> > change it in action.skin
>
> Have you tried doing
>
> slogan: /=something **or** other=/
>
> Not tried. But it should return the text escaped and therefore, the
> asterisks rather than bold.
What I want to do is to use the slogan outputed correctly, but be able
to edit it in a textbox,
[r][c]Site Name: [c][text slogan "/={code.snippets::slogan}=/"
size=55]
Does not work. I thought there may be some way to use [(source)], but
I couldnt be bothered, I can change the slogan manually.
Had to remove it from the action though, to stop it overwriting the
qoute call with a result.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
