[TYPO3-mvc] hidden records seem to be unworkable with extbase + is extbase bloated ?

[Steffen Müller]

Hi.

On 02.05.2011 19:44 Alban Cousinié wrote:
> This could be a solution. Actually I don't understand why overloading
> function createQuery() using
> $query->getQuerySettings()->setRespectEnableFields(FALSE); has no effect on
> hidden records, as it should normally disable enable fields filtering for
> all queries. It seems something doesn't connect properly here. Is this a bug
> or a missing feature ? ;-)
>

Another problem is that
$querySettings->setRespectEnableFields(FALSE)
does not differenciate between deleted and enableFields (which is set in 
TCA['tx_ext_domain_model_foo']['ctrl']['enablecolumns'] and usually 
hidden,starttime,endtime)

So you always find a where clause in your query with:

tx_ext_domain_model_foo.deleted=0 AND
tx_ext_domain_model_foo.hidden=0 AND
(tx_ext_domain_model_foo.starttime<=1304435640) AND
(tx_ext_domain_model_foo.endtime=0 OR
tx_ext_domain_model_foo.endtime>1304435640)

typo3/sysext/extbase/Classes/Persistence/Storage/Typo3DbBackend.php (795)
Typo3DbBackend::addEnableFieldsStatement()
(...)
$statement = t3lib_BEfunc::deleteClause($tableName);
$statement .= t3lib_BEfunc::BEenableFields($tableName);

IMHO this is a bug, deleteClause should not be used here.

Opinions?

-- 
cheers,
Steffen

TYPO3 Blog: http://www.t3node.com/
Twitter: http://twitter.com/t3node