[TYPO3-core] RFC #10563: Feature: Add Core API function to Extension Management: getEMConfArray()
Sebastian Gebhard
s.gebhard at markenmotiv.de
Mon Mar 2 12:44:29 CET 2009
This is an SVN patch request.
Type: New feature
Bugtracker references:
http://bugs.typo3.org/bug_view_page.php?bug_id=10563
Branches:
trunk
Problem:
Demand for a API function to get clean EM_CONF array/values
Solution:
This patch introduces a new static function getEMConfArray($extKey,
$arrKey) to t3lib_extMgm. It cleans up EM_CONF from old style to TER2
style if needed and returns the hole array or a single value.
Notes:
First paramter of course is the extension key.
Second parameter is optional. If given, the value of this $arrKey in
EM_CONF will be returned. Accessing nestes values is possible by giving
an $arrKey like this: 'constraints|depends'.
If extension, em_conf.php or the configuration key is not found NULL
will be returned.
For cleaning up from old style to TER2 style i refactored
em_index->fixEMCONF(), em_index->depToString(), em_index->stringToDep()
and em_index->splitVersionRange() into the new function. It should be
faster this way.
I avoided to introduce helper functions to t3lib_extMgm to keep it clean.
When this patch is stable em_index should use this new API function.
Regards,
Sebastian Gebhard
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 10563_v1.diff
Url: http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20090302/8a4c63e6/attachment.txt
More information about the TYPO3-team-core
mailing list