Isotope noch nicht kompatibel mit Contao 4.11

[seibtph]

Bei der Installation von Isotope unter Contao 4.11 kommt es zu folgendem Fehler:

You have requested a non-existent parameter "kernel.root_dir". Did you mean one of these: "kernel.project_dir", "kernel.build_dir", "kernel.cache_dir", "kernel.logs_dir"?

Es würde helfen kernel.root_dir durch kernel.project_dir zu ersetzen (in der Plugin.php unter system/modules/isotope/library/Isotope/ContaoManager).

[fritzmg]

To be more accurate: Isotope is not compatible with Symfony 5 without this change. You could downgrade symfony/http-kernel to ^4 as a workaround until this is fixed in Isotope.

[TB1234]

Das scheint nicht mehr mit der 4.11.1 zu funktionieren. Dort erhalte ich folgende Fehlermehldung, wenn ich versuche 'symfony/http-kernel' auf '^4' zu setzen...

$ /usr/bin/php7.4-cli -q -dmax_execution_time=0 -dmemory_limit=-1 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Paris /homepages/25/d107277713/htdocs/contao/web/contao-manager.phar.php composer require symfony/http-kernel=^4 --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction

/homepages/25/d107277713/htdocs/contao/composer.json has been updated

# Process terminated with exit code 0
# Result: OK


> Resolving dependencies using Composer Cloud v3.0.1
!!! Current server is sponsored by: Contao Association !!!


[7.3MiB/0.27s] Loading composer repositories with package information
[11.8MiB/0.86s] Updating dependencies
[18.5MiB/0.93s] Your requirements could not be resolved to an installable set of packages.
[18.5MiB/0.93s] 
  Problem 1
    - symfony/framework-bundle v5.2.4 requires symfony/http-kernel ^5.2.1 -> found symfony/http-kernel[v5.2.1, v5.2.2, v5.2.3, v5.2.4] but it conflicts with your root composer.json require (^4).
    - contao/manager-bundle 4.11.1 requires symfony/framework-bundle 4.4.* || 5.2.* -> satisfiable by symfony/framework-bundle[v5.2.4].
    - contao/manager-bundle is locked to version 4.11.1 and an update of this package was not requested.

[18.5MiB/0.93s] Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.
[8.9MiB/0.94s] Memory usage: 8.87MB (peak: 20.64MB), time: 0.94s.
[8.9MiB/0.94s] Finished Composer Cloud resolving.


# Cloud Job ID HJ8E4FoobYhmu78SLKUDCliQgg2KSaXC1uydDVhgu0VFJHe5d0FuDIlFc8uuQOVnyyQ9LxjeQO0vNwfuLywTG3lQSCd1htaEbDiJArDNq3qeuBIQWOcf failed

[fritzmg]

You need to run composer update after altering your composer.json.

[TB1234]

Oh, yes, this fix the problem. But I was not able to fix it directly via the contao manager. I have to manage it via the console. I am not able to change the version and make a composer update.

[fritzmg]

You can do that via the Contao Manager too. You can run composer update via the Maintenance section. See the description and screenshot here for example.

[TB1234]

Yes, I know. But this did not work! Sorry if my explanation was not clear enough. The reason seems that I am not able to change the version numbers via contao manager without a composer install this call failed and so the changes were not written to the file. So I was not able to do this via the manager. I have realy to do this via the file system...

[fritzmg]

Yes, you cannot add such a dependency, or a conflict, via the Contao Manager. You need to edit the composer.json manually and then you can run a composer update via the Contao Manager and take advantage of the resolver cloud (if you need to).

[aschempp]

fixed in 7026a4c

[xApep]

@aschempp or @fritzmg
wasn't that fixed in 2.7?

I'm doing clean install, contao 4.11.1 and current Isotope 2.7 but the problem is the same.

And when i try to downgrade sy...

[netzarbeiter]

yes, the issue has been fixed. But the version with the fix has not been released yet. You have to wait for Isotope eCommerce 2.7.1.

[fritzmg]

@xApep as previously mentioned you could in the meantime downgrade the affected Symfony package manually.

[xApep]

@netzarbeiter aaaa 2.7.1 - thought that was fixed in .0 - thank your for the info.

@fritzmg I tried as you can see in the screen shot but the problem is with other dependency.

Anyhow, do you guys know which contao version is fully compatible with isotope 2.7.0?

[fritzmg]

@xApep you need to run a full composer update after adding the dependency or conflict.

[xApep]

Thanks @fritzmg
but I have installed isotope latest .dev version and it works fine, since the patch is there.