On Thu, Oct 1, 2009 at 8:40 PM, Markus <[email protected]> wrote: > > Does that mean you have to save for example changesummary_1 to pages > instead of the standard changesummary data field?
No, you cannot save a field labeled changesummary_1, as changesummary. There is another option however (which can also be used for target). [session reset_changesummary "new value"] This will reset the value of changesummary to your new value. This is the only way to reset a data field multiple times and save it to different pages with different values. > Would it be possible to automate the creation of unique field names > and hide it from the user? What about numbering them in the order they > are used? (It gets quite complex managing so many underscores and > numbers.) This is a possibility. I'll look into it. But it could also be confusing if the wrong fields got invisibly renamed. We could perhaps limit this to recognized commands, but the whole idea of it sounds ripe for problems. I'm open for further discussion of this. 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 -~----------~----~----~----~------~----~------~--~---
