[TYPO3-dev] Include of plugins changed from 4.1.0 to 4.1.7 ?

Stefan Geith typo3dev2008.nospam1 at geithware.de
Wed Jun 18 12:25:52 CEST 2008


Dmitry Dulepov [typo3] schrieb:
> Hi!
> 
> Stefan Geith wrote:
>> I have some plugins, that start like this:
>>
>> <snip>
>> ...
>> if (isset($TYPO3_LOADED_EXT["sg_userdata"])) {
>>     require_once(t3lib_extMgm::extPath("sg_userdata")....);
>> }
>> class tx_sgsmallads_pi1 extends txsg_pibase {
>> ...
>> </snip>
>>
>> So $TYPO3_LOADED_EXT was directly available.
>>
>> One of my customers reported, that this doesn't work
>> after an update from 4.1.0 to 4.1.7
>>
>> I now have to use ...$GLOBALS['TYPO3_LOADED_EXT']...
> 
> Please, use t3lib_extMgm::isLoaded('sg_userdata') API call instead. 
> $TYPO3_LOADED_EXT is not a variable for common use. It may even cease to 
> exist in future.


Ah - OK, thanks! I will use that now.

But: when did the behaviour of including plugins change ?
Since when $TYPO3_LOADED_EXT is no longer available without $GLOBALS ?
Seems to me if it was one of the Bugfixes from 4.1.0 to 4.1.7 ...

-

Stefan




More information about the TYPO3-dev mailing list