[TYPO3-dev] Problems with a form in my extension and the action attribute

[Peter Klein]

> I have an extension with a form where people can select options in combo
> boxes and then click submit, the display is then updated, the combo boxes
> also reflect the previous choices. Form method was POST

Here you submit a value to your script, and return something, depending on 
what the user selected.
In a chached ext. this will work fine the 1st time, but when a new user 
selects something and submits, you get the value submitted by the 1st user 
due to caching.

As Dmitry described in his blog, $GLOBALS['TSFE']->set_no_cache() is bad, 
because it makes the ENTIRE page uncached, instead of just your ext.

Setting your ext to USER_INT will only make your ext. uncached, but still 
cache the rest of the page content.

--
Peter Klein




"StephenBungert" <stephenbungert at yahoo.de> wrote in message 
news:mailman.30333.1249473759.3168.typo3-dev at lists.netfielders.de...
>
> Buy submit to the database, do you mean it queries the database, or that 
> it
> saves data?  All I do is look up fields from a main table and from some mm
> tables.
>
> I see in the object browser that my extension is USER, can I/should I just
> chaneg it to USER_INT?
>
> Does this just stop caching? If so, is it ok just to keep
> $GLOBALS['TSFE']->set_no_cache();, I read on dmitry's blog that this is 
> bad.
> Is changing an etension to USER_INT also bad?
>
> -----
> -- 
> Stephen Bungert
> -- 
> View this message in context: 
> http://www.nabble.com/Problems-with-a-form-in-my-extension-and-the-action-attribute-tp24825209p24825576.html
> Sent from the TYPO3 Dev mailing list archive at Nabble.com.
>