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

[Ernesto Baschny [cron IT]]

Stefan Geith wrote: on 18.06.2008 11:44:

> 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']...
> 
> When did this behaviour change ?
> Seems it was a bugfix in 4.1.x, but I couldn't find where it happend...

I have had similar issues when upgrading some sites from 4.1.7 which 
defined "global" variables which were not accessible anymore from inside 
functions. It seems that the scope of inclusion of our plugins changed 
somewhere between 4.1.3 and 4.1.6, but I cannot spot the exact location yet.

Cheers,
Ernesto