[TYPO3-dev] COA_INT in extension ?

JoH info at cybercraft.de
Wed Sep 27 19:08:35 CEST 2006


>>> ok, i tried to do this on-the-fly.
>>>
>>> What is wrong, because it doesn't work ?
>>>
>>> $TS['conf']='COA_INT';
>>> $TS['conf.']['10']='TEXT';
>>> $TS['conf.']['10.']['value']=strftime('%D - %H:%M:%S',time());
>>> return $this->cObj->cObjGetSingle($TS['conf'],$TS['conf.']);
>>
>> Well - what exactly doesn't work?
>> Any URL where one could check the result?
>
> yes, of coarse, look at
> http://www.sk-typo3.de/index.php?id=190
> at the bottom (Object COA_INT generated on-the-fly)
> It's cached, that's the problem.
>
> vg Steffen
> (btw- waiting for your response on emails :) )

Well - it seems the difference here is the "value" part.
In my original example the configuration was done like this:

basket = COA_INT
basket {
    wrap = <hr />|
    10 = TEXT
    10.value = Basket (COA_INT):
    20 = USER
    20.userFunc = tx_cachetest_pi1->callTimeBasket
}

This means: Each time the COA_INT is replaced, the same userFunc is setting
the time.

In your case the setup looks like this after PHP created the array:

basket = COA_INT
basket {
    10 = TEXT
    10.value = Day - 00:00:00
}

Since this setup is in no way a dynamic setup and the TS you generated is
cached anyway, the result will always be the same, because the TS stays the
same.

The whole COA_INT thingie only makes sense, if there is something inside the
setup that is created dynamically.

HTH

Joey

(BTW: Which E-mail are we talking about? Did I miss something while
switching to a better server?)

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your knob sometimes!)
Dieter Nuhr, German comedian
openBC: http://www.cybercraft.de
T3 cookbook: http://www.typo3experts.com






More information about the TYPO3-dev mailing list