[TYPO3-commerce] SVN version of commerce disables page cache completely

[Franz Koch]

Hi Dimitry,

> Ingo Schmitt wrote:
>> Yes, it was already discussed in the list and I don't really have a 
>> solution that will work for me. If you look in the Code, the 
> 
> Easiest solution would be USER_INT. At the moment if there are 20 USER 
> objects on the page, they all will have to render. All GIFBUILDER images 
> too, all menus, everything, all the time.

hmm, wasn't there a guy called Dimitry who probably intended to improve 
the caching features of TYPO3 ;-)


Back to topic (at least a bit):
----------------
USER_INT might be a temporary solution to avoid set_no_cache, because:

In the way the basketHash of commerce is currently used, pi1 could also 
be set to USER_INT without slowing down the website. That's because the 
basketHash contains the sessionID of the fe_user and changes on every 
modification of the basket - so after all pi1 is in 95% generating a 
page from scratch anyway as far as I see.
The second problem is the pageBrowser, which evaluates all piVars for 
integer values, and if one value is not integer (like the basketHash), 
it will force a set_no_cache on every click on the pageBrowser. So the 
listView with pageBrowser will also never be cached - even worse, it 
forces set_no_cache due to the basketHash.

So caching pi1 is just a waste of space in the cache-table right now. 
But I already said that somewhere in this list without response if I 
remember correctly.

I at least modified my local install of pi1 to cache the pages 
completely, where the caches are generated for each combination of 
usergroups that occur and the given discounts to the fe_users (the 
discount stuff is a addon I coded for a customer). So prices are cached 
correctly according to the users settings and the visibility settings 
are also taken into account for the caches.

But caching the pages with the default templates cause one problem. 
Currently the quantity of a article in the basket is also shown in the 
order fields of a article in list and singleView - which will lead to 
wrong caches for most of the users. So you have to disable this to get 
clean cached pages. To have the same 'functionality', maybe some JS 
combined with a basket-cookie could do the trick.


Sorry, got off topic again. But maybe I'll get some response in this 
topic, as it's also cache related and there is another set_no_cache issue.

--
Greetings,
Franz