Another issue.
I use >>small text>> but it's broken. In the source I found "font-
size: 120%". But my style reads:
.small { font-size: 90%; }
Regards, Markus
On Oct 13, 11:03 pm, Markus <[email protected]> wrote:
> I have the following in a form where check is the value of a text
> field:
>
> [session if "! equal {=check} Aword && ! equal {=check} aword ?
> warn=..."]
>
> When I submit "Aword" no warning message appears, but I get a warning
> message when I submit "aword".
>
> Regards, Markus
>
> On Oct 13, 10:39 pm, The Editor <[email protected]> wrote:
>
>
>
> > I was able to get 3.2.5 out today with lot's of behind the scenes help
> > from Hans. Special thanks to him for many of the improvements in this
> > version.
>
> > Unfortunately our goal of getting out a stable 3.2 version didn't work
> > too well, due to the discovery of a security vulnerability right at
> > the time we began a major foray into changing our character encoding
> > system. Thus the flurry of rather rushed releases... This version may
> > just get us close to a 3.3 release candidate. Please do as much
> > testing of this as you can. I have some goals in mind for the 3.4 mini
> > development series that will likely take a few releases, but I want to
> > wait until we have 3.3 stabilized first. Anyway, I think this one may
> > be close to what we want for 3.3. From the changelog:
>
> > * Fixed small bug in warning system in last release. Do we finally
> > have the messaging system put back together again correctly?
> > * Changed info function to allow writing of info vars to pages with
> > either info OR write auth. In other words, the info auth extends the
> > pages you can write info var values to, beyond those with write
> > access.
> > * Fixed a bug in the BOLTauth function which could return false
> > positives in a poorly constructed auth page.
> > * More work on the sorting mechanism to get natural sorting working
> > properly in both regular searches and info reports. Much improved--and
> > used by default.
> > * Additional reworking of the character encoding system and markup
> > rules to give enhanced security and better html output. This could
> > cause some problems--but hopefully few.
> > * Plugged additional security holes for sites running BoltWire with
> > insecure server settings. Please contact me if you have questions.
> > * Deleted site header page and made slight fix to default header page.
> > * Tweaked the action.zones display to use stripes.
> > * Action.plugins now returns all available plugins, not just the first
> > few...
> > * Changed BOLTprocess slightly. Now function arrays take the form
> > $BOLTprocess['post'][] = 'func name'; I've updated the switchuser and
> > urllogin plugin documentation.
>
> > Remaining goals for 3.3 series are
> > * Fix < > character encoding. Actually, I'd like to still get this into
> > 3.3.
> > * Rework code markup and source functions so use the same lines of
> > code--for greater consistency and efficiency.
>
> > If you are interested, my main goals for the 3.4 series are:
> > * Get multiple commands to be automatically renumbered so this is
> > invisible to the user.
> > * Require all commands to be set as session variables to avoid
> > problems with accidental command triggering (namespace)
> > * Rework BOLTprocess to allow two way variables to be sent to it, and
> > insert various hooks into the BOLTsavepage / BOLTloadpage functions.
> > * Carefully evaluate all url/utf conversions and try and keep
> > everything within BoltWire consistently utf except as absolutely
> > needed.
>
> > More big character encoding headaches in that utf one, I suspect... :)
>
> > 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
-~----------~----~----~----~------~----~------~--~---
