Textpattern Support Forum

Hi Julián,

Looks like a very sensible thing to do, thanks. I’ll include it in the next update.

Adi

Thanks, Adi.
Not sure if intentionally, but I’m letting you know that the plugin shows as v0.4beta (and the opening post of this thread still doesn’t mention this new version).

Hi Adi,

I installed “adi_variable 0.4”.
Is there a solution for make it work with cnk_versionning?
A request for Maniqui and johnstephens in 2009

Thanks

maniqui wrote:

Adi, I was thinking this the other day: why not save the adi_variables on its own table (or maybe just in prefs table? because, it’s just one entry…). The only “backward compatibility” issue I see is that you may need to create a tag to include the vars, as txp:output_form probably won’t work, as the “form” holding the adi_variables, well, won’t be located in the “txp_form” table…

Hi maniqui – thanks for helping sacripant out.

WRT an adi_variables database table – I’m not sure about that. On reflection, I quite like the way the variables are in “plain sight” – i.e. visible to eyeballs & smd_where_used. And I don’t think the prefs table is really the place to put them either.

MarcoK wrote:

A little question. Why must use a form? You can’t call a function that get all variable set public and insert them into an global $variable array?

Hi Marco. Just stumbled across your query. Apologies for not addressing it sooner.

To answer your question, the variable values have to be stored somewhere. I chose to do it in a form, using txp:variable tags – for several reasons. Firstly it seemed like a good idea at the time, secondly it was visible (e.g. to smd_where_used), and thirdly it could be edited manually just like any other form. The other advantage is that by setting up the variables using standard txp:variable tags, I’m covered if the internal variable system changes.

The other option is to store the values in a separate database table, which has been requested before – and despite being stubborn, I haven’t totally discounted! Just want to concentrate on the 4.5 updates at the moment.