[TYPO3-english] TYPO3 6.2 access start & stop datetime not respected in frontend?!

[Nicola Cerchiari]

Hi Philipp,
I just tested your suggestion and the start&stop datetimes are not taken
into any account with config.no_cache=1 in the list method.
the only way I have to "hide" a record in the list is to disable it and it
immediately reflect the change.
Setting a stop datetime on a record throw an error on the show method page
though.

Can you confirm that the standard findAll() action should respect the
enableFields?

Thanks for your priceless help,
Nicola


2014-04-16 11:13 GMT+02:00 Philipp Gampe <philipp.gampe at typo3.org>:

> Hi Nicola,
>
> Nicola Cerchiari wrote:
>
> > What worries me is the non-coherent behaviour between the list and show
> > methods, as both pages have the same configuration, even about caching.
> > I even tried to set "list" as a non-cacheable action but the behaviour
> > does not change.
>
> The show action is a new cache entry for TYPO3 as it has a different set of
> parameters.
> Normally all page requests are cached as full page for a given set of
> parameters. You can turn set of with the no_cache setting or the
> corresponding get parameters.
>
> > I'll try anyways to disable the more caching as possible to avoid any
> > doubt and do more testing.
>
> Try config.no_cache=1 in your TS setup. If it works then, you can move on
> to
> find out why the "enabled fields" configuration is not taken into account
> for the expiration of the page cache.
>
> Best regards
> --
> Philipp Gampe – PGP-Key 0AD96065 – TYPO3 UG Bonn/Köln
> Documentation – Active contributor TYPO3 CMS
> TYPO3 .... inspiring people to share!
>
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>



-- 
*Nicola Cerchiari*