[TYPO3-mvc] Bug in AbstractRepository

Andreas Wolf typo3ml at andreaswolf.info
Fri Jul 23 22:39:01 CEST 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Steffen,

Am 23.07.10 15:07, schrieb Steffen Ritter:
> You can disable / hide existing records, add hidden records. But you are
> not able to change them again:
> 
> reason: Tx_Extbase_Persistence_Repository::update calls
> $existingObject = $this->findByUid($uid);
> $this->replace($existingObject, $modifiedObject);
> 
> but findByUid() never will find hidden records...

I discussed this with Jochen in Elmshorn, as I stumbled across the same
problem a few weeks ago.

This behavior is what you would normally expect, e.g. when selecting
records for rendering a web page. By default the enableFields are
respected, i.e. deleted, hidden and datetime (I'm not sure about
fe_groups). You can turn this off completely via the method
setRespectEnableFields() in Persistence\Typo3QuerySettings.

Making this configurable per setting is on my ToDo list, I just didn't
have time to really dig into that. I'm also not sure about how the
default query settings are determined, as the QueryFactory always
creates a new QuerySettings object for each built query.

Regards

Andreas

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxJ/eUACgkQHWtXp155bP8EYwCeMiHvyngbKBICUr74i69ByGHM
UMwAn1jFg310lQOVcHgck/QhKn0+udMH
=kjOt
-----END PGP SIGNATURE-----


More information about the TYPO3-project-typo3v4mvc mailing list