Hi, Thomas Koch wrote : [...] > * I have to change files in the ezproot when installing / uninstalling > extensions. I'm sure, that there are many setups of eZP, where all > developing is done in extensions and the ezproot can't be changed at all. I agree with you. As this file is "auto generated", it should be stored in the var directory like others auto generated files (cache, expiry.php, ...)
> * The script to generate autoloads includes only extensions that are > activated. What am I supposed to do, if I activate different extensions for > different siteaccesses? Or if I even dare to have equal classnames in > different extensions for different clients. (Not nice, but happens.) "Not nice" are not the right words... :-) > May I propose an alternative? > > Every extension, which wants to make use of autoload, should contain an > autoload directory, while leaving the autoloads (with s) directory untouched. > > The following code gives should be executed for every scriptrun and > automatically registers all autoload dirs to ezcBase: [...] I don't have a solution. But don't you think it's too confusing to have "autoload" and "autoloads" directories to permit a "not nice" code ? In fact the real problem is the name of the "autoloads" directory which is not well choosen for a directory where you can write template operators. Cheers -- Damien POBEL http://pwet.fr/blog -- Sdk-public mailing list [email protected] http://lists.ez.no/mailman/listinfo/sdk-public
