Yes, this is probably our best option. I thought about this but as you
note it will invalidate some forms that are using commands not in
session fields. For instance:
[form]
[select nextpage][option main][option site][option test][select][submit]
[form]
would no longer work and would need to be rewritten as
[form]
[select thepage][option main][option site][option test][select][submit]
[session nextpage {=thepage}]
[form]
A simple example. And manageable probably. But the question is do we
want to go this direction? I don't mind rewriting the core actions but
there are surely many custom forms that would be affected and lot's of
plugins. All that would get broken. I'm thinking of my main site with
dread...
One possibility is to set a config value that works this way, and
perhaps the zones.top thing also. By default turned off. Give people a
chance to catch up. And then when we feel comfortable we could change
the default. Perhaps as part of a 4.xx series... :) It would be
nice to have a bigger excuse to go 4.xx though...
Cheers
Dan
On Tue, Oct 6, 2009 at 10:11 AM, DrunkenMonk <[email protected]> wrote:
>
>
>> I'm still wondering if there isn't some way to distinguish between
>> commands and data fields.
>
> Commands are at some point used with a [session <command>]?
>
> have [session] create a hidden list of words that have been used as a
> command, treat only these words as commands.
> You'd stop treating hidden inputs as commands as well.
>
> Example 1:
>
> [hidden source "user_input"]
> [session passdata source]
> [submit save]
>
> This will create a hidden input BOLTCOMMANDS consisting of:
> "passdata". Only "passdata" will be treated as a command
>
> Example 2:
>
> [session source "user_input"]
> [session passdata source]
> [submit save]
>
> This will create a hidden input BOLTCOMMANDS consisting of:
> "source,passdata". Source will return the source of the page
> "user_input", and passdata will pass it on.
>
> Is that what you mean?
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
