[TYPO3-dam] DAM indexing with dam_scheduler / dam_cron

[Lorenz Ulrich]

Hi Frank

There is a pending RFC in the DAM list that sets file_name, file_path 
and file_type exclude to 0 because this is also a UX problem.

Would this solve the entire problem? I guess not because this way the 
indexer can write to tx_dam but not to tx_dam_cat_mm. Can't you 
(theoretically) give the exclude field rights to the _cli_scheduler 
user? Or doesn't this work?


Best regards,


Lorenz

Am 15.03.2011 15:41, schrieb Frank Nägler:
> Hi @ all,
> after update to the latest version of DAM, the problem is not fixed.
>
> But I have found the real problem with the indexer.
> I Don't know if this bug is a core bug or a DAM-Indexer bug.
>
> The problem are the exclude fields. After setting all fields from exclude=1 to exclude=0 the indexer works fine.
> The indexer use tx_dam_db::insertUpdateData which use an instance of t3lib_TCEmain to insert or update the dam records.
>
> The user _cli_scheduler which starts the index process has no access to the exclude fields, which results in broken categories as described and in broken records in tx_dam, because file_path and file_name for example are per default exclude fields.
>
> _Frank
>