Textpattern Support Forum

colak wrote:

Vote for core:)

+1 :)

One of the basics of my idea was to leave no traces in the database.

Er, are forms not in the database now?

I guess you mean no new table, right?

Last edited by Mary (2008-05-23 08:12:29)

Couldn’t this be done by giving a name attribute to a well introduced tag, <txp:text />?

Uli, insert <pre><txp:php>print_r($GLOBALS);</txp:php></pre> somewhere in your template.

wet, your fingers are inspired…

A sci-fi feature request:

Imagine…
Imagine a future functionality (a plug-in?) on the admin side… that looks (parses) for declared <txp:variable name="varname" value="" /> on top of templates and then, somewhere in the admin interface (probably in a tab we want to make accessible for our clients… or not), it renders (automagically and on-the-fly) little form, made from a label (txp:variable name value) and a text input field (prefilled with txp:variable value value) for each txp:variable for every variable in every template.
Then, using that form, we/our-clients can rewrite the value of any variable on any template (that means, we set a new value, hit “Submit”, then TXP magic dust goes to the template, looks for the corresponding txp:variable name="name" tag and rewrites it with the new value for value.

Some ideas about this:

• no need for storing the variable name/value on the database
• no need to give access to template tab to our clients if, for some reason, we/they need to change the value for a variable.
• we will be able to create some on-the-fly mechanisms for controlling template logic, and so, the HTML output

Example:

<txp:variable name="closed_for_vacation" value="no" />
<txp:variable name="display_banner" value="yes" />
// ...
// ...
<txp:if_variable name="closed_for_vacation" value="yes">
We are closed for vacations. Come back later.
<txp:else />
It's open. We are here.
</txp:if_variable>
//...
//...
<txp:if_variable name="display_banner" value="yes">
Super mega banner.
<txp:else />
No banner here.
</txp:if_variable>

Again, for those two declared variables, there is a magic parser that looks for txp:variable and creates on the fly the two label/text input fields for changing the current value to a new one.
Client changes the value, hits submit, the value is replaced on the tag (on the template).
Then, clients will be able to control the chunks of conditional code, in other words, of the output, in a new way.

Am… I… missing… something?

Last edited by maniqui (2008-05-28 05:43:16)