Update von 4.4.47 auf 4.9.

Hallo ins Forum
Ich beschäftige mich gerade auf einem Testserver für ein Update von einer 4.4.47-Version auf die 4.9.

Contao läuft auf einem Webserver von hostpoint.ch und folgende Module sind installiert:
- euf_grid
- euf_news_meta
- mobile_menu
- contao-slick-bundle
- m17-sticky-backend-footer
- RockSolid AntiSpam
- Easy Themes

Der Contao-Manager bricht nach einiger Zeit mit folgender Meldung ab:

Code:

---

$ /usr/local/php72/bin/php -q /home/wivision/www/contao49.wivisions.ch/web/contao-manager.phar.php composer require contao/manager-bundle=4.9.* contao/news-bundle=4.9.* contao/calendar-bundle=4.9.* --no-suggest --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction

/home/wivision/www/contao49.wivisions.ch/composer.json has been updated

# Process terminated with exit code 0
# Result: OK


$ /usr/local/php72/bin/php -q /home/wivision/www/contao49.wivisions.ch/web/contao-manager.phar.php composer remove contao/core-bundle contao/installation-bundle --no-update --no-scripts --no-ansi --no-interaction

contao/core-bundle is not required in your composer.json and has not been removed
contao/installation-bundle is not required in your composer.json and has not been removed

# Process terminated with exit code 0
# Result: OK


> Resolving dependencies using Composer Cloud v2.2.4

[5.7MiB/0.21s] Loading composer repositories with package information
[6.1MiB/0.29s] Updating dependencies
[2131.7MiB/32.08s] Your requirements could not be resolved to an installable set of packages.
[2131.7MiB/32.08s]
  Problem 1
    - Conclusion: don't install symfony/framework-bundle v4.4.5
    - Conclusion: don't install symfony/framework-bundle v4.4.4
    - Conclusion: don't install symfony/framework-bundle v4.4.3
    - Conclusion: don't install symfony/framework-bundle v4.4.2
    - Conclusion: don't install contao/manager-bundle 4.9.1
    - contao/manager-bundle 4.9.0 requires contao/core-bundle 4.9.0 -> satisfiable by contao/core-bundle[4.9.0].
    - Installation request for contao/manager-bundle 4.9.* -> satisfiable by contao/manager-bundle[4.9.0, 4.9.1].
    - wa72/htmlpagedom v1.4.2 requires symfony/dom-crawler ^2.3 <2.8 | ^2.8.3 | ^3.0.1 | ^4 <4.3 -> satisfiable by symfony/dom-crawler[v2.3.0, v2.3.1, v2.3.10, v2.3.11, v2.3.12, v2.3.13, v2.3.14, v2.3.15, v2.3.16, v2.3.17, v2.3.18, v2.3.19, v2.3.2, v2.3.20, v2.3.21, v2.3.22, v2.3.23, v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.3, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.3.38, v2.3.39, v2.3.4, v2.3.40, v2.3.41, v2.3.42, v2.3.5, v2.3.6, v2.3.7, v2.3.8, v2.3.9, v2.4.0, v2.4.1, v2.4.10, v2.4.2, v2.4.3, v2.4.4, v2.4.5, v2.4.6, v2.4.7, v2.4.8, v2.4.9, v2.5.0, v2.5.1, v2.5.10, v2.5.11, v2.5.12, v2.5.2, v2.5.3, v2.5.4, v2.5.5, v2.5.6, v2.5.7, v2.5.8, v2.5.9, v2.6.0, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.46, v2.7.47, v2.7.48, v2.7.49, v2.7.5, v2.7.50, v2.7.51, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.40, v2.8.41, v2.8.42, v2.8.43, v2.8.44, v2.8.45, v2.8.46, v2.8.47, v2.8.48, v2.8.49, v2.8.5, v2.8.50, v2.8.52, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.17, v3.3.18, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.10, v3.4.11, v3.4.12, v3.4.13, v3.4.14, v3.4.15, v3.4.16, v3.4.17, v3.4.18, v3.4.19, v3.4.2, v3.4.20, v3.4.21, v3.4.22, v3.4.23, v3.4.24, v3.4.25, v3.4.26, v3.4.27, v3.4.28, v3.4.29, v3.4.3, v3.4.30, v3.4.31, v3.4.32, v3.4.33, v3.4.34, v3.4.35, v3.4.36, v3.4.37, v3.4.38, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v3.4.9, v4.0.0, v4.0.1, v4.0.10, v4.0.11, v4.0.12, v4.0.13, v4.0.14, v4.0.15, v4.0.2, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8, v4.0.9, v4.1.0, v4.1.1, v4.1.10, v4.1.11, v4.1.12, v4.1.2, v4.1.3, v4.1.4, v4.1.5, v4.1.6, v4.1.7, v4.1.8, v4.1.9, v4.2.0, v4.2.1, v4.2.10, v4.2.11, v4.2.12, v4.2.2, v4.2.3, v4.2.4, v4.2.5, v4.2.6, v4.2.7, v4.2.8, v4.2.9].
    - wa72/htmlpagedom v1.4.2 requires symfony/dom-crawler ^2.3 <2.8 | ^2.8.3 | ^3.0.1 | ^4 <4.3 -> satisfiable by symfony/dom-crawler[v2.3.0, v2.3.1, v2.3.10, v2.3.11, v2.3.12, v2.3.13, v2.3.14, v2.3.15, v2.3.16, v2.3.17, v2.3.18, v2.3.19, v2.3.2, v2.3.20, v2.3.21, v2.3.22, v2.3.23, v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.3, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.3.38, v2.3.39, v2.3.4, v2.3.40, v2.3.41, v2.3.42, v2.3.5, v2.3.6, v2.3.7, v2.3.8, v2.3.9, v2.4.0, v2.4.1, v2.4.10, v2.4.2, v2.4.3, v2.4.4, v2.4.5, v2.4.6, v2.4.7, v2.4.8, v2.4.9, v2.5.0, v2.5.1, v2.5.10, v2.5.11, v2.5.12, v2.5.2, v2.5.3, v2.5.4, v2.5.5, v2.5.6, v2.5.7, v2.5.8, v2.5.9, v2.6.0, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.46, v2.7.47, v2.7.48, v2.7.49, v2.7.5, v2.7.50, v2.7.51, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.40, v2.8.41, v2.8.42, v2.8.43, v2.8.44, v2.8.45, v2.8.46, v2.8.47, v2.8.48, v2.8.49, v2.8.5, v2.8.50, v2.8.52, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.17, v3.3.18, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.10, v3.4.11, v3.4.12, v3.4.13, v3.4.14, v3.4.15, v3.4.16, v3.4.17, v3.4.18, v3.4.19, v3.4.2, v3.4.20, v3.4.21, v3.4.22, v3.4.23, v3.4.24, v3.4.25, v3.4.26, v3.4.27, v3.4.28, v3.4.29, v3.4.3, v3.4.30, v3.4.31, v3.4.32, v3.4.33, v3.4.34, v3.4.35, v3.4.36, v3.4.37, v3.4.38, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v3.4.9, v4.0.0, v4.0.1, v4.0.10, v4.0.11, v4.0.12, v4.0.13, v4.0.14, v4.0.15, v4.0.2, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8, v4.0.9, v4.1.0, v4.1.1, v4.1.10, v4.1.11, v4.1.12, v4.1.2, v4.1.3, v4.1.4, v4.1.5, v4.1.6, v4.1.7, v4.1.8, v4.1.9, v4.2.0, v4.2.1, v4.2.10, v4.2.11, v4.2.12, v4.2.2, v4.2.3, v4.2.4, v4.2.5, v4.2.6, v4.2.7, v4.2.8, v4.2.9].
    - symfony/dom-crawler v2.3.0 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.1 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.10 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.11 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.12 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.13 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.14 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.15 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.16 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.17 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.18 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.19 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.2 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.20 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.21 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.22 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.23 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.24 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.25 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.26 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.27 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.28 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.29 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.3 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.30 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.31 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.32 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.33 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.34 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.35 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.36 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.37 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.38 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.39 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.4 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.40 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.41 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.42 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.5 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.6 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.7 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.8 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.3.9 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.4.0 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.4.1 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.4.10 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.4.2 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.4.3 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.4.4 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.4.5 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.4.6 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.4.7 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.4.8 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.4.9 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.5.0 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.5.1 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.5.10 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.5.11 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.5.12 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.5.2 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.5.3 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.5.4 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.5.5 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.5.6 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.5.7 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.5.8 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.5.9 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.6.0 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.6.1 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.6.10 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.6.11 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.6.12 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.6.13 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.6.2 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.6.3 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.6.4 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.6.5 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.6.6 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.6.7 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.6.8 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.6.9 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.0 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.1 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.10 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.11 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.12 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.13 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.14 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.15 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.16 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.17 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.18 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.19 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.2 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.20 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.21 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.22 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.23 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.24 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.25 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.26 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.27 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.28 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.29 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.3 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.30 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.31 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.32 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.33 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.34 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.35 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.36 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.37 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.38 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.39 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.4 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.40 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.41 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.42 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.43 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.44 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.45 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.46 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.47 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.48 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.49 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.5 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.50 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.51 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.6 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.7 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.8 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.7.9 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.10 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.11 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.12 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.13 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.14 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.15 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.16 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.17 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.18 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.19 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.20 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.21 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.22 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.23 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.24 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.25 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.26 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.27 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.28 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.29 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.3 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.30 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.31 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.32 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.33 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.34 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.35 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.36 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.37 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.38 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.39 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.4 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.40 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.41 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.42 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.43 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.44 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.45 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.46 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.47 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.48 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.49 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.5 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.50 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.52 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.6 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.7 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.8 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v2.8.9 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.0.1 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.0.2 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.0.3 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.0.4 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.0.5 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.0.6 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.0.7 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.0.8 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.0.9 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.1.0 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.1.1 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.1.10 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.1.2 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.1.3 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.1.4 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.1.5 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.1.6 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.1.7 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.1.8 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.1.9 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.0 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.1 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.10 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.11 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.12 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.13 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.14 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.2 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.3 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.4 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.5 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.6 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.7 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.8 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.2.9 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.0 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.1 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.10 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.11 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.12 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.13 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.14 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.15 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.16 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.17 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.18 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.2 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.3 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.4 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.5 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.6 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.7 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.8 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.3.9 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.0 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.1 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.10 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.11 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.12 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.13 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.14 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.15 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.16 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.17 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.18 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.19 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.2 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.20 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.21 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.22 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.23 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.24 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.25 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.26 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.27 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.28 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.29 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.3 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.30 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.31 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.32 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.33 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.34 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.35 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.36 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.37 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.38 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.4 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.5 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.6 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.7 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.8 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v3.4.9 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.0 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.1 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.10 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.11 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.12 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.13 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.14 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.15 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.2 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.3 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.4 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.5 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.6 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.7 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.8 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.0.9 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.1.0 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.1.1 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.1.10 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.1.11 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.1.12 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.1.2 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.1.3 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.1.4 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.1.5 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.1.6 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.1.7 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.1.8 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.1.9 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.2.0 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.2.1 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.2.10 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.2.11 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.2.12 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.2.2 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.2.3 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.2.4 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.2.5 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.2.6 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.2.7 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.2.8 conflicts with symfony/framework-bundle[v4.4.0].
    - symfony/dom-crawler v4.2.9 conflicts with symfony/framework-bundle[v4.4.0].
    - contao/core-bundle 4.9.0 requires symfony/framework-bundle 4.4.* -> satisfiable by symfony/framework-bundle[v4.4.0, v4.4.1, v4.4.2, v4.4.3, v4.4.4, v4.4.5].
    - Conclusion: don't install symfony/framework-bundle v4.4.1
    - Installation request for wa72/htmlpagedom (locked at v1.4.2) -> satisfiable by wa72/htmlpagedom[v1.4.2].

[2131.8MiB/32.08s] <warning>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.</warning>
[434.6MiB/33.79s] Memory usage: 434.58MB (peak: 2133.16MB), time: 33.79s.
[434.6MiB/33.79s] Finished Composer Cloud resolving.


# Cloud Job ID aAOmeXr7v3DoMs25kBN2HUgHV5LtxDgN1fe3EYNe1hoCXsJhySYcXxkUcTYiDlmaMLXc3UWoUPwe7ArK8kr1deSPNWxT failed

---

### Der Hintergrundprozess wurde unerwartet beendet ###

---

Da bin ich aber eindeutig noch zu unerfahren um zu wissen, wo ich da bezgl. der Conflicts ansetzen muss.

Kann mir da wer weiterhelfen?

RockSolid AntiSpam benötigst du nicht mehr. Die Funktionalität ist inzwischen im Core. Kannst Du als erstes deinstallieren.
Der Konflikt tritt auf durch
wa72/htmlpagedom

Irgendwer bringt diese Abhängigkeit mit.

Hast Du alles zur Aktualisierung ausgewählt?
Welche PHP-Version wird verwendet?

Ja, es waren nicht alle Pakete zur Aktualisierung ausgewählt.

Zitat:

---

Zitat von mlweb

RockSolid AntiSpam benötigst du nicht mehr. Die Funktionalität ist inzwischen im Core. Kannst Du als erstes deinstallieren.
Der Konflikt tritt auf durch
wa72/htmlpagedom

Irgendwer bringt diese Abhängigkeit mit.

Hast Du alles zur Aktualisierung ausgewählt?
Welche PHP-Version wird verwendet?

---

Es wird PHP 7.2.28 verwendet.
Ich denke ja. Ich habe den Core und alle Plugins ausgewählt.

ich habe eben geschaut ob ich in den Abhängigkeiten wa72 entdecke. Jedoch Fehlanzeige.
Ich wollte bereits das euf_meta und das rocksolid rauslöschen. Jedoch bekomme ich eine Fehlermeldung:

Code:

---

Schließen
$ /usr/local/php72/bin/php -q /home/wivision/www/contao49.wivisions.ch/web/contao-manager.phar.php composer remove madeyourday/contao-rocksolid-antispam --no-update --no-scripts --no-ansi --no-interaction

madeyourday/contao-rocksolid-antispam is not required in your composer.json and has not been removed

# Process terminated with exit code 0
# Result: OK


> Resolving dependencies using Composer Cloud v2.2.4

 Aufgabe ID 08ZGk6qJU6ZwULONRHvV5zV8pB0D0s5OdFodgpuW4PUQZXhwpXjAvUZwiTlWwK8TBLbleJYfBl20N3dfXhD7ecdGsDNj8dfr4 aktiv seit 45 Sekunden [6.1MiB/0.39s]

---

Zitat:

---

Zitat von Twitt

Ich denke ja. Ich habe den Core und alle Plugins ausgewählt.

---

Du musst zuvor alle Pakete zum Update markieren. Oder über die Wartung ein composer update durchführen.

Zitat:

---

Zitat von Spooky

Ja, es waren nicht alle Pakete zur Aktualisierung ausgewählt.

---

Woran genau hast Du das gesehen?

Daran:

Code:

---

Installation request for wa72/htmlpagedom (locked at v1.4.2)

---

Könnte natürlich auch sein, dass

Code:

---

"wa72/htmlpagedom": "1.4.2"

---

in der composer.json steht, aber das bezweifle ich.

Zitat:

---

Zitat von Spooky

Du musst zuvor alle Pakete zum Update markieren. Oder über die Wartung ein composer update durchführen.

---

Ich habe nun versucht das zu tun was du mir geraten hast spooky. Ich hoffe ich hab das richtig gemacht.
Unter "Systemwartung" Composer-Abhängigkeiten -> Installer ausführen.

So der so bricht er mir den Kosolentask ab.


In der Composer.json steht momentan:

Code:

---

{
    "type": "project",
    "require": {
        "codefog/contao-mobile_menu": "^2.7",
        "contao/calendar-bundle": "^4.4",
        "contao/conflicts": "*@dev",
        "contao/manager-bundle": "4.4.*",
        "contao/news-bundle": "^4.4",
        "erdmannfreunde/contao-news-meta": "^1.0",
        "erdmannfreunde/euf_grid": "^2.2",
        "heimrichhannot/contao-slick-bundle": "^1.3",
        "jrgregory/m17-sticky-backend-footer": "^2.0",
        "madeyourday/contao-rocksolid-antispam": "^2.0",
        "terminal42/contao-easy_themes": "^2.2"
    },
    "extra": {
        "contao-component-dir": "assets"
    },
    "scripts": {
        "post-install-cmd": [
            "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
        ],
        "post-update-cmd": [
            "Contao\\ManagerBundle\\Composer\\ScriptHandler::initializeApplication"
        ]
    }
}

---

Zitat:

---

Zitat von Twitt

Unter "Systemwartung" Composer-Abhängigkeiten -> Installer ausführen.

---

Du musst

• Zuerst natürlich die Contao Version ändern.
• Dann bei "Composer-Abhängigkeiten" ein composer update ausführen (Drop-Down Menü).

Zitat:

---

Zitat von Twitt

So der so bricht er mir den Kosolentask ab.

---

Du musst immer die gesamte Konsolenausgabe posten, ansonsten wissen wir nicht, was falsch gelaufen ist.

Zitat:

---

Zitat von Spooky

Du musst

• Zuerst natürlich die Contao Version ändern.
• Dann bei "Composer-Abhängigkeiten" ein composer update ausführen (Drop-Down Menü).

---

Ok, ich habe zuerst die Contao-Version geändert, heisst von 4.4.x auf 4.9x umgestellt. Ich habe aber nicht die Änderungen durchgeführt, da er mir immer abbricht.
Dann habe ich unter Composer-Abhängigkeiten ein Update via Drop-down durchgeführt.

Dann hat er mir wieder abgebrochen mit der Meldung:

Konsolen-Task abgebrochen und der Inhalt ist wie folgt:

Code:

---

> Resolving dependencies using Composer Cloud v2.2.4

# Job ID 0XMYmOQlk0TGVDLfeSl2X7XPq1EwY2somNkNq9jUYx2DM6gQoZCA0DI89muQvaXkCzs7GeXj7dONyG4vGXU80vuXgW59in3A40bRolK8gLJ completed in 37 seconds
# Memory usage: 489.75MB (peak: 2477.22MB), time: 36.34s.

$ /usr/local/php72/bin/php -q /home/wivision/www/contao49.wivisions.ch/web/contao-manager.phar.php composer install --prefer-dist --no-dev --no-progress --no-suggest --no-ansi --no-interaction --optimize-autoloader

contao/manager-plugin: Generating plugin class...
contao/manager-plugin: ...done generating plugin class

 // Clearing the cache for the prod environment with debug                     
 // false                                                                     

 [OK] Cache for the "prod" environment (debug=false) was successfully cleared. 


 // Warming up the cache for the prod environment with debug                   
 // false                                                                     

 [OK] Cache for the "prod" environment (debug=false) was successfully warmed. 


 Trying to install assets as relative symbolic links.

 --- --------------------------------------------- ------------------
      Bundle                                        Method / Error   
 --- --------------------------------------------- ------------------
  ?  ContaoCoreBundle                              relative symlink 
  ?  ContaoNewsBundle                              relative symlink 
  ?  HeimrichHannotContaoUtilsBundle              relative symlink 
  ?  ContaoCalendarBundle                          relative symlink 
  ?  HeimrichHannotContaoMultiColumnEditorBundle  relative symlink 
  ?  HeimrichHannotContaoSlickBundle              relative symlink 
 --- --------------------------------------------- ------------------

 [OK] All assets were successfully installed.                                 

Added the system/initialize.php file.
20:15:39 ERROR    [console] Error thrown while running command "contao:install --env=prod". Message: "The path "system/config/tcpdf.php" exists and is not a symlink." ["exception" => LogicException { …},"command" => "contao:install --env=prod","message" => "The path "system/config/tcpdf.php" exists and is not a symlink."]

In SymlinkUtil.php line 80:
                                                                 
  The path "system/config/tcpdf.php" exists and is not a symlink. 
                                                                 

contao:install [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command> [<target>]

Loading composer repositories with package information
Installing dependencies from lock file
Nothing to install or update
Package oyejorge/less.php is abandoned, you should avoid using it. No replacement was suggested.
Generating optimized autoload files
> Contao\ManagerBundle\Composer\ScriptHandler::initializeApplication
Script Contao\ManagerBundle\Composer\ScriptHandler::initializeApplication handling the post-install-cmd event terminated with an exception

In ScriptHandler.php line 113:
                                                                             
  An error occurred while executing the "contao:install" command: 20:15:39 ER 
  ROR    [console] Error thrown while running command "contao:install --env= 
  prod". Message: "The path "system/config/tcpdf.php" exists and is not a sym 
  link." ["exception" => LogicException { …},"command" => "contao:install --e 
  nv=prod","message" => "The path "system/config/tcpdf.php" exists and is not 
  a symlink."]                                                               
                                                                             
  In SymlinkUtil.php line 80:                                                 
                                                                             
    The path "system/config/tcpdf.php" exists and is not a symlink.           
                                                                             
                                                                             
  contao:install [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version 
  ] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [- 
  -] <command> [<target>]                                                     
                                                                             

install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--no-suggest] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--ignore-platform-reqs] [--] [<packages>...]


# Process terminated with exit code 1
# Result: General error


---

### Der Hintergrundprozess wurde unerwartet beendet ###

---

Zitat:

---

Du musst immer die gesamte Konsolenausgabe posten, ansonsten wissen wir nicht, was falsch gelaufen ist.

---

ich kopiere jeweils das, was im Fenster mit dem roten Balken mitgeteilt wird. Was fehlt denn da noch?
Oder reden/schreiben wir hier nicht vom selben?

Du musst zuerst die Contao Version ändern, dann das composer update durchführen.

Zitat:

---

Zitat von Spooky

Du musst zuerst die Contao Version ändern, dann das composer update durchführen.

---

Zitat:

---

Zitat von Twitt

Ok, ich habe zuerst die Contao-Version geändert, heisst von 4.4.x auf 4.9x umgestellt. Ich habe aber nicht die Änderungen durchgeführt, da er mir immer abbricht.
Dann habe ich unter Composer-Abhängigkeiten ein Update via Drop-down durchgeführt.

---

Salut spooky, das habe ich doch oben geschrieben.?

Das Problem ist, wenn ich die Version ändere und dann versuche, im Manager das Update auf 4.9 laufen zu lassen, bricht er mir ab :-/.

Nein, du hast geschrieben, dass du dann wieder ganz normal die Änderungen anwenden wolltest, anstatt so wie von mir vorgeschlagen ein composer update über die Wartung durchzuführen. Zumindest interpretiere ich denen Post so.

Zitat:

---

Zitat von Spooky

Nein, du hast geschrieben, dass du dann wieder ganz normal die Änderungen anwenden wolltest, anstatt so wie von mir vorgeschlagen ein composer update über die Wartung durchzuführen. Zumindest interpretiere ich denen Post so.

---

Ok, nochmal zur Verständigung damit wir beide vom gleichen schreiben:
Ich habe Zuerst bei der Contao-Version bei der Version auf das Zahnrad getippt, dann aus 4.4.* eine 4.9.* gemacht.
Dann bin ich in die Systemwartung gegangen und unter "Composer-Abhängigkeiten" via Dropdown ein Update ausgeführt.

Ist doch richtig so oder?

Zitat:

---

Zitat von Twitt

Ok, ich habe zuerst die Contao-Version geändert, heisst von 4.4.x auf 4.9x umgestellt. Ich habe aber nicht die Änderungen durchgeführt, da er mir immer abbricht..

---

Hab ich nun nochmals versucht und er gibt mir folgenden Fehler aus:

Code:

---

> Resolving dependencies using Composer Cloud v2.2.4

# Job ID char4EC9RmS3iMlShHV1lDHhNk8xqigeuxEW0L6R0WtQG6jZr1PcrkvD3pbsZTDDnRGGq3nBD41IMfKd completed in 166 seconds
# Memory usage: 489.8MB (peak: 2477.27MB), time: 161.94s.

$ /usr/local/php72/bin/php -q /home/wivision/www/contao49.wivisions.ch/web/contao-manager.phar.php composer install --prefer-dist --no-dev --no-progress --no-suggest --no-ansi --no-interaction --optimize-autoloader

contao/manager-plugin: Generating plugin class...
contao/manager-plugin: ...done generating plugin class

 // Clearing the cache for the prod environment with debug                     
 // false                                                                     

 [OK] Cache for the "prod" environment (debug=false) was successfully cleared. 


 // Warming up the cache for the prod environment with debug                   
 // false                                                                     

 [OK] Cache for the "prod" environment (debug=false) was successfully warmed. 


 Trying to install assets as relative symbolic links.

 --- --------------------------------------------- ------------------
      Bundle                                        Method / Error   
 --- --------------------------------------------- ------------------
  ?  ContaoCoreBundle                              relative symlink 
  ?  ContaoNewsBundle                              relative symlink 
  ?  HeimrichHannotContaoUtilsBundle              relative symlink 
  ?  ContaoCalendarBundle                          relative symlink 
  ?  HeimrichHannotContaoMultiColumnEditorBundle  relative symlink 
  ?  HeimrichHannotContaoSlickBundle              relative symlink 
 --- --------------------------------------------- ------------------

 [OK] All assets were successfully installed.                                 

Added the system/initialize.php file.
12:06:39 ERROR    [console] Error thrown while running command "contao:install --env=prod". Message: "The path "system/config/tcpdf.php" exists and is not a symlink." ["exception" => LogicException { …},"command" => "contao:install --env=prod","message" => "The path "system/config/tcpdf.php" exists and is not a symlink."]

In SymlinkUtil.php line 80:
                                                                 
  The path "system/config/tcpdf.php" exists and is not a symlink. 
                                                                 

contao:install [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command> [<target>]

Loading composer repositories with package information
Installing dependencies from lock file
Nothing to install or update
Package oyejorge/less.php is abandoned, you should avoid using it. No replacement was suggested.
Generating optimized autoload files
> Contao\ManagerBundle\Composer\ScriptHandler::initializeApplication
Script Contao\ManagerBundle\Composer\ScriptHandler::initializeApplication handling the post-install-cmd event terminated with an exception

In ScriptHandler.php line 113:
                                                                             
  An error occurred while executing the "contao:install" command: 12:06:39 ER 
  ROR    [console] Error thrown while running command "contao:install --env= 
  prod". Message: "The path "system/config/tcpdf.php" exists and is not a sym 
  link." ["exception" => LogicException { …},"command" => "contao:install --e 
  nv=prod","message" => "The path "system/config/tcpdf.php" exists and is not 
  a symlink."]                                                               
                                                                             
  In SymlinkUtil.php line 80:                                                 
                                                                             
    The path "system/config/tcpdf.php" exists and is not a symlink.           
                                                                             
                                                                             
  contao:install [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version 
  ] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [- 
  -] <command> [<target>]                                                     
                                                                             

install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--no-suggest] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--ignore-platform-reqs] [--] [<packages>...]


# Process terminated with exit code 1
# Result: General error


---

### Der Hintergrundprozess wurde unerwartet beendet ###

---

Du musst system/config/tcpdf.php löschen und dann nochmal ein composer install oder update machen.

Zitat:

---

Zitat von Spooky

Du musst system/config/tcpdf.php löschen und dann nochmal ein composer install oder update machen.

---

Wiederum ein Fehler:

Code:

---

> Resolving dependencies using Composer Cloud v2.2.4

# Job ID ssxRvJVjnPenec9egd1jItjWB2EG9vEB8nyMzKL8kQpj6vbrPspA168GP7n63n1EmHteWDnI4wfczIWdWIDCxE8M9 completed in 48 seconds
# Memory usage: 489.8MB (peak: 2477.27MB), time: 48.49s.

$ /usr/local/php72/bin/php -q /home/wivision/www/contao49.wivisions.ch/web/contao-manager.phar.php composer install --prefer-dist --no-dev --no-progress --no-suggest --no-ansi --no-interaction --optimize-autoloader


# Process terminated with exit code 143
# Result: Termination (request to terminate) [signal 15]


---

### Der Hintergrundprozess wurde unerwartet beendet ###

---

Habe es wiederum so gemacht:
- Die Datei: system/config/tcpdf.php gelöscht
- von 4.4.* auf 4.9* gewechselt
- unter Abhängigkeiten via Dropdown ein Update durchgeführt.

Versuche es einfach nochmal

Zitat:

---

Zitat von Spooky

Versuche es einfach nochmal

---

Danke spooky, hab ich - wieder mit dem Ergebnis:

Code:

---

> Resolving dependencies using Composer Cloud v2.2.4

# Job ID whYdfSJooVGLgRzWc5AuPOijbqudhfshzsYZ31OxGra5649aRUrqLiVRfVanDqVt6hbfzPc7RJ6 completed in 60 seconds
# Memory usage: 489.81MB (peak: 2477.28MB), time: 57.23s.

$ /usr/local/php72/bin/php -q /home/wivision/www/contao49.wivisions.ch/web/contao-manager.phar.php composer install --prefer-dist --no-dev --no-progress --no-suggest --no-ansi --no-interaction --optimize-autoloader

contao/manager-plugin: Generating plugin class...
contao/manager-plugin: ...done generating plugin class

 // Clearing the cache for the prod environment with debug                     
 // false                                                                     

 [OK] Cache for the "prod" environment (debug=false) was successfully cleared. 


 // Warming up the cache for the prod environment with debug                   
 // false                                                                     

 [OK] Cache for the "prod" environment (debug=false) was successfully warmed. 


 Trying to install assets as relative symbolic links.

 --- --------------------------------------------- ------------------
      Bundle                                        Method / Error   
 --- --------------------------------------------- ------------------
  ?  ContaoCoreBundle                              relative symlink 
  ?  ContaoNewsBundle                              relative symlink 
  ?  HeimrichHannotContaoUtilsBundle              relative symlink 
  ?  ContaoCalendarBundle                          relative symlink 
  ?  HeimrichHannotContaoMultiColumnEditorBundle  relative symlink 
  ?  HeimrichHannotContaoSlickBundle              relative symlink 
 --- --------------------------------------------- ------------------

 [OK] All assets were successfully installed.                                 

Added the system/initialize.php file.
Symlinked the system/config/tcpdf.php file.

 --- --------------------------------------------- ----------------------------------------------------------------
      Symlink                                      Target / Error                                                 
 --- --------------------------------------------- ----------------------------------------------------------------
  !  web/files/wivisions/bilder                    Skipped because files/wivisions will be symlinked.             
  !  web/files/wivisions/theme_wv                  Skipped because files/wivisions will be symlinked.             
  ?  web/files/wivisions                          files/wivisions                                               
  ?  web/system/modules/easy_themes/html          system/modules/easy_themes/html                               
  ?  web/system/modules/euf_grid/assets            system/modules/euf_grid/assets                                 
  ?  web/system/modules/m17StickyBEFooter/assets  system/modules/m17StickyBEFooter/assets                       
  ?  web/system/modules/mobile_menu/assets        system/modules/mobile_menu/assets                             
  ?  system/themes/flexible                        The path "system/themes/flexible" exists and is not a symlink. 
  ?  web/assets                                    The path "web/assets" exists and is not a symlink.             
  ?  web/system/themes                            The path "web/system/themes" exists and is not a symlink.     
  ?  system/logs                                  The path "system/logs" exists and is not a symlink.           
 --- --------------------------------------------- ----------------------------------------------------------------

Loading composer repositories with package information
Installing dependencies from lock file
Nothing to install or update
Package oyejorge/less.php is abandoned, you should avoid using it. No replacement was suggested.
Generating optimized autoload files
> Contao\ManagerBundle\Composer\ScriptHandler::initializeApplication
Script Contao\ManagerBundle\Composer\ScriptHandler::initializeApplication handling the post-install-cmd event terminated with an exception

In ScriptHandler.php line 113:
                                                                   
  An error occurred while executing the "contao:symlinks" command: 
                                                                   

install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--no-suggest] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--ignore-platform-reqs] [--] [<packages>...]


# Process terminated with exit code 1
# Result: General error


---

### Der Hintergrundprozess wurde unerwartet beendet ###

---

Hab das Gefühl, da is der Wurm drin. Obs besser ist, die Site runterzuziehen und nochmals ne neue Kopie der Originalsite zu erstellen...?

Du musst die beanstandeten Dateien löschen.

Kann es sein, dass du diese Contao Installation irgendwie kopiert hattest?

Zitat:

---

Zitat von Spooky

Du musst die beanstandeten Dateien löschen.

---

Ich verstehe noch nicht genau was in der Fehlermeldung gemeint ist:
Meinst du diese:

Code:

---

  !  web/files/wivisions/bilder                    Skipped because files/wivisions will be symlinked.             
  !  web/files/wivisions/theme_wv                  Skipped because files/wivisions will be symlinked.             
  ?  web/files/wivisions                          files/wivisions                                               
  ?  web/system/modules/easy_themes/html          system/modules/easy_themes/html                               
  ?  web/system/modules/euf_grid/assets            system/modules/euf_grid/assets                                 
  ?  web/system/modules/m17StickyBEFooter/assets  system/modules/m17StickyBEFooter/assets                       
  ?  web/system/modules/mobile_menu/assets        system/modules/mobile_menu/assets                             
  ?  system/themes/flexible                        The path "system/themes/flexible" exists and is not a symlink. 
  ?  web/assets                                    The path "web/assets" exists and is not a symlink.             
  ?  web/system/themes                            The path "web/system/themes" exists and is not a symlink.     
  ?  system/logs                                  The path "system/logs" exists and is not a symlink.

---

Zitat:

---

Kann es sein, dass du diese Contao Installation irgendwie kopiert hattest?

---

Ja ich hab die Installation 1:1 kopiert und mit einer neuen Datenbank - aber den alten Daten - versehen um so einen Test des Updates auf die 4.9 zu machen.
Was wäre besser gewesen?

Zitat:

---

Zitat von Twitt

Ich verstehe noch nicht genau was in der Fehlermeldung gemeint ist:
Meinst du diese:

Code:

---

  !  web/files/wivisions/bilder                    Skipped because files/wivisions will be symlinked.             
  !  web/files/wivisions/theme_wv                  Skipped because files/wivisions will be symlinked.             
  ?  web/files/wivisions                          files/wivisions                                               
  ?  web/system/modules/easy_themes/html          system/modules/easy_themes/html                               
  ?  web/system/modules/euf_grid/assets            system/modules/euf_grid/assets                                 
  ?  web/system/modules/m17StickyBEFooter/assets  system/modules/m17StickyBEFooter/assets                       
  ?  web/system/modules/mobile_menu/assets        system/modules/mobile_menu/assets                             
  ?  system/themes/flexible                        The path "system/themes/flexible" exists and is not a symlink. 
  ?  web/assets                                    The path "web/assets" exists and is not a symlink.             
  ?  web/system/themes                            The path "web/system/themes" exists and is not a symlink.     
  ?  system/logs                                  The path "system/logs" exists and is not a symlink.

---

---

Diese Dateien:

Code:

---

  ?  system/themes/flexible                        The path "system/themes/flexible" exists and is not a symlink. 
  ?  web/assets                                    The path "web/assets" exists and is not a symlink.             
  ?  web/system/themes                            The path "web/system/themes" exists and is not a symlink.     
  ?  system/logs                                  The path "system/logs" exists and is not a symlink.

---

Sollte auch rot markiert sein in der Ausgabe.

Zitat:

---

Zitat von Twitt

Ja ich hab die Installation 1:1 kopiert und mit einer neuen Datenbank - aber den alten Daten - versehen um so einen Test des Updates auf die 4.9 zu machen.
Was wäre besser gewesen?

---

Besser wäre eine richtige Deployment Strategie ;). Bei einer Kopie musst du darauf achten, dass du nicht die Symlinks mit kopierst. Du kannst dich auch an folgende Anleitung halten: https://erdmann-freunde.de/logbuch/contao-4-4-umziehen/

Zitat:

---

Zitat von Spooky

Diese Dateien:

Code:

---

  ?  system/themes/flexible                        The path "system/themes/flexible" exists and is not a symlink. 
  ?  web/assets                                    The path "web/assets" exists and is not a symlink.             
  ?  web/system/themes                            The path "web/system/themes" exists and is not a symlink.     
  ?  system/logs                                  The path "system/logs" exists and is not a symlink.

---

Sollte auch rot markiert sein in der Ausgabe.

---

Nein ist in der Ausgabe nicht rot markiert.
Vielleicht eine blöde Frage. Heisst das ich müsste die darin befindlichen Dateien löschen oder was genau müsste ich damit tun?

Zitat:

---

Zitat von Spooky

Besser wäre eine richtige Deployment Strategie ;). Bei einer Kopie musst du darauf achten, dass du nicht die Symlinks mit kopierst. Du kannst dich auch an folgende Anleitung halten: https://erdmann-freunde.de/logbuch/contao-4-4-umziehen/

---

Ok, statt weiter an diesem Flickwerk zu basteln. Mache ich nun mal gleich das ganze mit dieser Anleitung und schaue ob das dann besser kommt. :-)

Zitat:

---

Zitat von Twitt

Vielleicht eine blöde Frage. Heisst das ich müsste die darin befindlichen Dateien löschen oder was genau müsste ich damit tun?

---

Du musst die Dateien oder Ordner löschen, die dort angegeben sind.

Zitat:

---

Zitat von Spooky

Du musst die Dateien oder Ordner löschen, die dort angegeben sind.

---

Ich bin nun in der Endphase und habe eine Seite genau nach EF-Richtlinien auf einen Testserver geladen.

Nun meine Frage fürs Update auf 4.9: Gehe ich nun so vor dass ich beim Core von 4.4.* auf 4.9.* ändere und dann die Änderungen ausführe oder
dass ich nach der Änderung zuerst im Composer bei Abhängigkeiten ein Update durchführe?

Entweder zuerst alle Pakete zum Update markieren und dann die Version ändern und alles anwenden.

Oder die Version ändern und dann wie bereits erwähnt das composer update über die Wartung im Contao Manager durchführen.

Zitat:

---

Zitat von Twitt

Ich bin nun in der Endphase und habe eine Seite genau nach EF-Richtlinien auf einen Testserver geladen.

Nun meine Frage fürs Update auf 4.9: Gehe ich nun so vor dass ich beim Core von 4.4.* auf 4.9.* ändere und dann die Änderungen ausführe oder
dass ich nach der Änderung zuerst im Composer bei Abhängigkeiten ein Update durchführe?

---

Hab mich a bisserl zu früh gefreut. Im Frontend erscheint die Seite noch nicht "ein Fehler ist aufgetreten"

unter var/logs sind die letzten Einträge folgende:

Code:

---

[2020-03-10 16:59:59] request.INFO: Matched route "contao_index". {"route":"contao_index","route_parameters":{"_token_check":true,"_controller":"Contao\\CoreBundle\\Controller\\FrontendController::indexAction","_scope":"frontend","_route":"contao_index"},"request_uri":"https://2020ct49.wivisions.ch/","method":"GET"} []
[2020-03-10 16:59:59] security.INFO: Attempting SimplePreAuthentication. {"key":"frontend","authenticator":"Contao\\CoreBundle\\Security\\ContaoAuthenticator"} []
[2020-03-10 16:59:59] app.CRITICAL: An exception occurred. {"exception":"[object] (Exception(code: 0): Could not find template \"j_colorbox_c4_lightbox_wv\" at /home/wivision/www/2020ct49.wivisions.ch/vendor/contao/core-bundle/src/Resources/contao/library/Contao/TemplateLoader.php:153)"} []
[2020-03-10 16:59:59] request.INFO: Matched route "contao_catch_all". {"route":"contao_catch_all","route_parameters":{"_scope":"frontend","_token_check":true,"_controller":"Contao\\CoreBundle\\Controller\\FrontendController::indexAction","_url_fragment":"favicon.ico","_route":"contao_catch_all"},"request_uri":"https://2020ct49.wivisions.ch/favicon.ico","method":"GET"} []
[2020-03-10 16:59:59] security.INFO: Attempting SimplePreAuthentication. {"key":"frontend","authenticator":"Contao\\CoreBundle\\Security\\ContaoAuthenticator"} []
[2020-03-10 16:59:59] request.ERROR: Uncaught PHP Exception Symfony\Component\HttpKernel\Exception\NotFoundHttpException: "Page not found: https://2020ct49.wivisions.ch/favicon.ico" at /home/wivision/www/2020ct49.wivisions.ch/vendor/contao/core-bundle/src/EventListener/ExceptionConverterListener.php line 112 {"exception":"[object] (Symfony\\Component\\HttpKernel\\Exception\\NotFoundHttpException(code: 0): Page not found: https://2020ct49.wivisions.ch/favicon.ico at /home/wivision/www/2020ct49.wivisions.ch/vendor/contao/core-bundle/src/EventListener/ExceptionConverterListener.php:112, Contao\\CoreBundle\\Exception\\PageNotFoundException(code: 0): Page not found: https://2020ct49.wivisions.ch/favicon.ico at /home/wivision/www/2020ct49.wivisions.ch/vendor/contao/core-bundle/src/Resources/contao/controllers/FrontendIndex.php:63)"} []

---

Hast du mir einen Tipp, was da noch nicht funzt?

Zitat:

---

Zitat von Twitt

Hab mich a bisserl zu früh gefreut. Im Frontend erscheint die Seite noch nicht "ein Fehler ist aufgetreten"

---

Benutze den Debug-Modus und poste den Stack Trace.

Zitat:

---

Zitat von Spooky

Benutze den Debug-Modus und poste den Stack Trace.

---

Sorry verstehe nur Bahnhof spooky.

Erster Google Hit für "contao debug-modus stack trace": https://docs.contao.org/manual/de/system/debug-modus/ ;)

Zitat:

---

Zitat von Spooky

Erster Google Hit für "contao debug-modus stack trace": https://docs.contao.org/manual/de/system/debug-modus/ ;)

---

Danke spooky, das hab ich gefunden, ich hab mehr das Problem mit dem Setzen von Passwort und Benutzername weil ich nicht weiss wie ich mit der Kommandozeile das geregelt kriege. Ich arbeite nur über den CM. :-(

Du bist doch jetzt auf Contao 4.9 » https://docs.contao.org/manual/de/sy...4-8-und-hoeher

Zitat:

---

Zitat von Spooky

Du bist doch jetzt auf Contao 4.9 » https://docs.contao.org/manual/de/sy...4-8-und-hoeher

---

Sorry, nein da ich im Frontend ja noch einen Fehler bekam.
Soll ich das Update auf 4.9 einfach mal durchführen?

Stacktrace der 4.4.47 Version:

Code:

---

Exception:
Could not find template "j_colorbox_c4_lightbox_wv"

  at vendor/contao/core-bundle/src/Resources/contao/library/Contao/TemplateLoader.php:153
  at Contao\TemplateLoader::getDefaultPath('j_colorbox_c4_lightbox_wv', 'html5')
    (vendor/contao/core-bundle/src/Resources/contao/library/Contao/TemplateLoader.php:111)
  at Contao\TemplateLoader::getPath('j_colorbox_c4_lightbox_wv', 'html5')
    (vendor/contao/core-bundle/src/Resources/contao/library/Contao/Controller.php:82)
  at Contao\Controller::getTemplate('j_colorbox_c4_lightbox_wv', 'html5')
    (vendor/contao/core-bundle/src/Resources/contao/library/Contao/TemplateInheritance.php:324)
  at Contao\Template->getTemplatePath('j_colorbox_c4_lightbox_wv', 'html5')
    (vendor/contao/core-bundle/src/Resources/contao/library/Contao/TemplateInheritance.php:87)
  at Contao\Template->inherit()
    (vendor/contao/core-bundle/src/Resources/contao/library/Contao/Template.php:268)
  at Contao\Template->parse()
    (vendor/contao/core-bundle/src/Resources/contao/classes/FrontendTemplate.php:52)
  at Contao\FrontendTemplate->parse()
    (vendor/contao/core-bundle/src/Resources/contao/pages/PageRegular.php:733)
  at Contao\PageRegular->createFooterScripts(object(LayoutModel))
    (vendor/contao/core-bundle/src/Resources/contao/pages/PageRegular.php:229)
  at Contao\PageRegular->prepare(object(PageModel))
    (vendor/contao/core-bundle/src/Resources/contao/pages/PageRegular.php:46)
  at Contao\PageRegular->getResponse(object(PageModel), true)
    (vendor/contao/core-bundle/src/Resources/contao/controllers/FrontendIndex.php:308)
  at Contao\FrontendIndex->renderPage(object(Collection))
    (vendor/contao/core-bundle/src/Resources/contao/controllers/FrontendIndex.php:74)
  at Contao\FrontendIndex->run()
    (vendor/contao/core-bundle/src/Controller/FrontendController.php:42)
  at Contao\CoreBundle\Controller\FrontendController->indexAction()
    (vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php:151)
  at Symfony\Component\HttpKernel\HttpKernel->handleRaw(object(Request), 1)
    (vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php:68)
  at Symfony\Component\HttpKernel\HttpKernel->handle(object(Request), 1, true)
    (vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php:200)
  at Symfony\Component\HttpKernel\Kernel->handle(object(Request))
    (web/app_dev.php:68)

---

Ich habe nun auch das fehlende Template wieder in den Template Ordner gelegt. Der Fehler im Frontend ist aber immer noch.

Zitat:

---

Zitat von Twitt

Sorry, nein da ich im Frontend ja noch einen Fehler bekam.

---

In der 4.4 kommt der Fehler?

Zitat:

---

Zitat von Twitt

Soll ich das Update auf 4.9 einfach mal durchführen?

---

Naja, da das dein ultimatives Ziel ist, würde ich sagen: ja ;)

Zitat:

---

Zitat von Twitt

Ich habe nun auch das fehlende Template wieder in den Template Ordner gelegt. Der Fehler im Frontend ist aber immer noch.

---

Welcher Fehler?

Zitat:

---

Zitat von Spooky

In der 4.4 kommt der Fehler?

---

Ja, der Fehler im Frontend. Ich habe jedoch am Trace gesehen, dass ein Template fehlt. Habe dieses dazugenommen und alle Caches etc. gelöscht.
Somit hats geklappt.

Zitat:

---

Zitat von Spooky

Naja, da das dein ultimatives Ziel ist, würde ich sagen: ja ;)

---

Bin ich grad dabei. Allerdings läuft seit ca. 5min :
Composer-Pakete werden hinzugefügt...
contao/manager-bundle=4.9.*, contao/news-bundle=4.9.*, contao/calendar-bundle=4.9.*

und im Fenster steht:

Code:

---

$ /usr/local/php72/bin/php -q /home/wivision/www/2020ct49.wivisions.ch/web/contao-manager.phar.php composer require contao/manager-bundle=4.9.* contao/news-bundle=4.9.* contao/calendar-bundle=4.9.* --no-suggest --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction

/home/wivision/www/2020ct49.wivisions.ch/composer.json has been updated

---

Ich lass ihn jetzt aber mal laufen. Ich gehe davon aus, der braucht seine Zeit fürs Update ...

Hm, wie bist du hier nun vorgegangen? Hast du nun, wie mehrmals empfohlen, zuerst die Contao Version geändert und dann über die Wartung ein composer update angestoßen?

Zitat:

---

Zitat von Spooky

Hm, wie bist du hier nun vorgegangen? Hast du nun, wie mehrmals empfohlen, zuerst die Contao Version geändert und dann über die Wartung ein composer update angestoßen?

---

Ich habe die von dir empfohlene erste Variante ausgeführt.

Zitat:

---

Zitat von Spooky

Entweder zuerst alle Pakete zum Update markieren und dann die Version ändern und alles anwenden.

Oder die Version ändern und dann wie bereits erwähnt das composer update über die Wartung im Contao Manager durchführen.

---

Allerdings steht immer noch "Composer-Pakete werden hinzugefügt". Kann jetzt nicht sagen ober hängt oder installiert... Soll ich mal die zweite Variante versuchen?

Der Task hat sich vermutlich aufgehängt.

Zitat:

---

Zitat von Spooky

Der Task hat sich vermutlich aufgehängt.

---

Möglich. Habe die Site nochmals geladen und dann ist er friedlich durchgelaufen mit dem Update. Bin gerade dabei die Caches zu leeren und im Backend unter Systemwartung alles zu bereinigen. Einzig beim Installtool habe ich die folgenden Tabellen in der Datenbank noch nicht bereinigt:

Code:

---

DROP TABLE tl_cron
DROP TABLE tl_session
Spalten löschen

ALTER TABLE tl_content DROP youtubeStop
ALTER TABLE tl_content DROP youtubeStart
ALTER TABLE tl_form_field DROP fsType
ALTER TABLE tl_layout DROP doctype
ALTER TABLE tl_log DROP ip
ALTER TABLE tl_member DROP activation
ALTER TABLE tl_member DROP autologin
ALTER TABLE tl_member DROP loginCount
ALTER TABLE tl_module DROP flashJS
ALTER TABLE tl_module DROP flashID
ALTER TABLE tl_module DROP interactive
ALTER TABLE tl_module DROP source
ALTER TABLE tl_module DROP altContent
ALTER TABLE tl_module DROP flashvars
ALTER TABLE tl_module DROP transparent
ALTER TABLE tl_module DROP size
ALTER TABLE tl_module DROP totalLength
ALTER TABLE tl_module DROP cols
ALTER TABLE tl_theme DROP defaultImageDensities
ALTER TABLE tl_user DROP loginCount

---

Wusste nicht, ob ich die definitiv rausschmeissen darf und es sich um Überbleibsel von frühreren Contao-Versionen handelt?

Und noch ne Frage bezgl. dem Debug-Modus: Kann ich die Datei .env sowie das File "--NAME" wieder löschen oder muss ich in der Kommandozeile noch was rückgängig machen?

Zitat:

---

Zitat von Twitt

Wusste nicht, ob ich die definitiv rausschmeissen darf und es sich um Überbleibsel von frühreren Contao-Versionen handelt?

---

Generell gilt: du solltest nur das löschen, wo du dir absolut sicher bist, dass du es nicht mehr brauchst. Ansonsten, wenn du dir nicht sicher bist, kannst du es auch einfach lassen. Das stört den Betrieb nicht (außer in Ausnahmefällen).

Zitat:

---

Zitat von Twitt

Und noch ne Frage bezgl. dem Debug-Modus: Kann ich die Datei .env sowie das File "--NAME" wieder löschen oder muss ich in der Kommandozeile noch was rückgängig machen?

---

Was meinst du mit "--NAME"?

Zitat:

---

Zitat von Spooky

Generell gilt: du solltest nur das löschen, wo du dir absolut sicher bist, dass du es nicht mehr brauchst. Ansonsten, wenn du dir nicht sicher bist, kannst du es auch einfach lassen. Das stört den Betrieb nicht (außer in Ausnahmefällen).

---

Jup, genau so sehe ich das auch. Drum hab ich nachgefragt. Ich hab sie jetzt einfach mal dringelassen.

Zitat:

---

Zitat von Spooky

Was meinst du mit "--NAME"?

---

Als ich in der Kommandozeile ein Passwort vergeben musste, hat er mir ins Wurzelverzeichnis eine Datei ".env" und eine Datei "--wivisions" (wivisions wohl weil ich den Benutzer so nannte) gelegt.
Ich wusste jetzt nicht ob ich diese beiden Dateien wieder löschen darf, da ich den Debugmodus nicht mehr benötige und in 4.9 dieser dann via Manager aufrufbar ist.