[TYPO3-ttnews] fix for tt_news 3.0 news caching update

[Rupert Germann]

hi,

I corrected 2 bugs in SVN which were introduced with my last update.

changelog:
* new feature: added the new pagebrowser from the listview to the tt_news
admin listview (class tx_ttnews_recordlist::renderListNavigation()) 

* fix: the categorycount cache was always written no matter of a cached
value was found or not.

* fix: added missing () around the lifetime part of the getfromcache query
for the internal caching.

* changed the db-engine of the tt_news_cache table to innodb.

greets
rupert


Rupert Germann wrote:

> hi,
> 
> latest news from svn (mostly caching related):
> 
> in short:
> now you can choose in the extensionmanager which caching engine tt_news
> should use.
> 
> Changelog:
> * connected the internal caching from tt_news to the TYPO3 caching
> framework (requires at least TYPO3 4.3). By default it's configured to use
> the DB backend but of course it will work with all other available caching
> backEnds too (tested with memcached, APC, filecache and DB)
> 
> * Added a switch to the extmanager config where one can choose the
> "caching Engine" (options: internal, cachingFramework). If the caching
> framework is not available (TYPO3 < v4.3) tt_news automatically falls back
> to the internal caching.
>  
> * Moved the caching related functions to their own classfile:
> lib/class.tx_ttnews_cache.php
> 
> * changed the "lifetime" handling of cache entries to use the same system
> as the caching framework.
> 
> * changed the fieldnames of table tt_news_cache to make it work with the
> caching framework and the internal caching.
> 
> * fixed bug #11236:  Wrong param passed to getSubCategoriesForMenu
> * fix: moved the call to function initCategories() inside the $codes loop
> because initCategories() requires $this->theCode to be set.
> 
> 
> 
> greets
> Rupert