http://twiki.org/cgi-bin/edit/Codev/SetTemporaryValues?SOMEVARIABLE=something where we render the topic being viewed and set any instance of % SOMEVARIABLE % to something....

This idea also works nicely with my TemplateTopic idea for user definable editable forms..

unfortuanatly I have only hardcoded the 3 Variables that I needed for the RenamePage code into the view.pl code. I haven't figured out a generaic solution.... Please Help !!! :)

-- SvenDowideit - 11 Feb 2001

I should have something hanging around in the drawer ... (for a small discussion see SessionVariables)

(the idea was to get all CGI params and add them to the current preferences)

-- AndreaSterbini - 13 Feb 2001

How about using the same param1 ... param4 parameters (%PARAM1% ... %PARAM4% variables) that are in use by the oops script? This could be done very easily and it would prevent security issues of changing arbitrary perferences variables. Opinions?

Example usage: At work I made a plugin that reads software defects from an Oracle database and displays the result in a TWiki page, i.e. write BUG:12345:Subject, BUG:12345:Description to show the subject and description of bug 12345. Parameters could be used to create a generic bug report page, i.e. it would be possible to write BUG:%PARAM1%:Subject, BUG:%PARAM1%:Description.

-- PeterThoeny - 13 Feb 2001

why? why not make them named? you have the ability to parse the URL, and then to use those variable names on purpose.. If you use generaic variable names you loose readablilty and have the chance to stuff up easily. (I am fond of LongDescriptiveVariableNames)

-- SvenDowideit - 13 Feb 2001