[TYPO3-dam] dam_index external tools

Xavier Perseguers typo3 at perseguers.ch
Thu Apr 17 06:53:12 CEST 2008


Hei Georg,

> IMHO:
> - TYPO3 should have an API-function within the core that allows any 
> Extension to simply checks for existance and executability of any needed 
> external program.
> - All Extensions should use call up this function before executing the 
> external program configured.
> 
> I don't know by heart wether this IMHO needed API-function + it's usage 
> is part of the TYPO3 API documentation; in case NOT in the docu please 
> contribute to it.
> 
> In case more than one API-functions for that purpose are existing, 
> please contribute by suggesting a streamlined version or recommended one.

OK.

> So, in case it's the way, that a check and subsequent extecution a 
> binary works in one extension (you mentioned indexed_saerch), and dioes 
> not work from another extension (whatever dam-service), apperently the 
> "another extension" is not using it in the right way and has to be 
> fixed; yet another option to contribute.

They use two different approaches: indexed_search is asking the user to 
give it the directory containing various external tools (where is catdoc 
located, where is unzip located, where is...) wherever dam_index and 
associated meta indexing services register their mandatory external 
tools as services with standard TYPO3 API. The API then searches for 
these tools in all configured "binary directories" (both standards as 
/bin and /usr/bin and those defined in localconf.php). That is both 
approaches are valid. The problem is that the service registration API 
does not work well with some PHP hardening as already explained. 
indexed_search seems not to perform any additional check once configured.

I personnaly find the dam_index and Cie easier to use as it uses the 
configuration in localconf.php to search for binaries. indexed_search 
asks for every single external tool location. *But* the TYPO3 API should 
be fixed to better work, this is why I sent yesterday a patch on the 
bugtracker to overcome this situation.

Regards
-- 
Xavier Perseguers


More information about the TYPO3-project-dam mailing list