Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #19026
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Using multiple versions of a component |
| Date | 2022-07-02 02:04 +0200 |
| Message-ID | <ji9gbiF1jsjU1@mid.individual.net> (permalink) |
Recently I came across the followig problem: Using Composer to manage dependencies for a WordPress plugin, in particular to include Twig to make it easier to generate the backend UI. So the code looks similar to this: <?php namespace MyPlugin; use Twig\Loader\FilesystemLoader; use Twig\Environment; require(__DIR__ . '/vendor/autoload.php'); ... However - this caused a problem with another plugin which also use Twig but in a different version. As the other plugin was loaded first the older version of it was already present. Also having multiple autoloaders seems not to be a wise idea anyway. Is there any "best practice" to deal with this or should one just not try to do such things? -- Arno Welzel https://arnowelzel.de
Back to comp.lang.php | Previous | Next — Next in thread | Find similar | Unroll thread
Using multiple versions of a component Arno Welzel <usenet@arnowelzel.de> - 2022-07-02 02:04 +0200 Re: Using multiple versions of a component Ace of diamonds <he12091983@gmail.com> - 2022-07-06 09:19 -0700
csiph-web