Details

      Description

      I am getting lots of errors when trying to install LegacyBridge with eZPlatform master.

      The errors and the necessary steps to reproduce are described in the attached documents:

      In any case, I'm resuming the errors below:

      When executing composer require --update-no-dev "ezsystems/legacy-bridge:^1.0.4"

      Your requirements could not be resolved to an installable set of packages.
       
        Problem 1
          - The requested package sebastian/recursion-context (locked at 1.0.4) exists as sebastian/recursion-context[1.0.0, 1.0.1, 1.0.2, 1.0.5, 1.0.x-dev, 2.0.0, 2.0.x-dev, 3.0.0, dev-master, 3.0.x-dev] but these are rejected by your constraint.
       
       
      Installation failed, reverting ./composer.json to its original content.

      When executing composer require "ezsystems/legacy-bridge:^1.0.4"

      Updating the "app/config/parameters.yml" file
      > Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap
      > eZ\Bundle\EzPublishCoreBundle\Composer\ScriptHandler::clearCache
       
      [Symfony\Component\Config\Exception\FileLoaderLoadException]
      There is no extension able to load the configuration for "ez_publish_legacy" (in /var/www/ezp_18x/app/config/ezplatform.yml). Looked for namespace "ez_publish_legacy", found "framework", "security", "twig", "monolog", "swiftmailer", "assetic", "doctrine", "sensio_framework_extra", "stash", "hautelook_templated_uri", "liip_imagine", "fos_http_cache", "ezpublish", "ez_search_engine_legacy", "ez_io", "ez_publish_rest", "ez_platformui", "ez_systems_ez_support_tools", "nelmio_cors", "white_october_pagerfanta", "oneup_flysystem", "ez_systems_platform_installer", "ez_systems_repository_forms", "ez_search_engine_solr", "content_on_the_fly", "bazinga_js_translation", "jms_translation" in /var/www/ezp_18x/app/config/ezplatform.yml (which is being imported from "/var/www/ezp_18x/app/config/ezplatform_prod.yml").
       
      [Symfony\Component\DependencyInjection\Exception\InvalidArgumentException]
      There is no extension able to load the configuration for "ez_publish_legacy" (in /var/www/ezp_18x/app/config/ezplatform.yml). Looked for namespace "ez_publish_legacy", found "framework", "security", "twig", "monolog", "swiftmailer", "assetic", "doctrine", "sensio_framework_extra", "stash", "hautelook_templated_uri", "liip_imagine", "fos_http_cache", "ezpublish", "ez_search_engine_legacy", "ez_io", "ez_publish_rest", "ez_platformui", "ez_systems_ez_support_tools", "nelmio_cors", "white_october_pagerfanta", "oneup_flysystem", "ez_systems_platform_installer", "ez_systems_repository_forms", "ez_search_engine_solr", "content_on_the_fly", "bazinga_js_translation", "jms_translation"
       
      Script eZ\Bundle\EzPublishCoreBundle\Composer\ScriptHandler::clearCache handling the build event terminated with an exception
      Installation failed, reverting ./composer.json to its original content.
       
      [RuntimeException]
      An error occurred when executing the "'cache:clear --no-warmup'" command:
       
      [Symfony\Component\Config\Exception\FileLoaderLoadException]
       
      There is no extension able to load the configuration for "ez_publish_legacy" (in /var/www/ezp_18x/app/config/ezplatform.yml). Looked for namespace "ez_publish_legacy", found "framework", "sec
      urity", "twig", "monolog", "swiftmailer", "assetic", "doctrine", "sensio_framework_extra", "stash", "hautelook_templated_uri", "liip_imagine", "fos_http_cache", "ezpublish", "ez_search_engine_legacy",
      "ez_io", "ez_publish_rest", "ez_platformui", "ez_systems_ez_support_tools", "nelmio_cors", "white_october_pagerfanta", "oneup_flysystem", "ez_systems_platform_installer", "ez_systems_repository_forms",
      "ez_search_engine_solr", "content_on_the_fly", "bazinga_js_translation", "jms_translation" in /var/www/ezp_18x/app/config/ezplatform.yml (which is being imported from "/var/www/ezp_18x/app/config/ezpl
      atform_prod.yml").
       
      [Symfony\Component\DependencyInjection\Exception\InvalidArgumentException]
       
      There is no extension able to load the configuration for "ez_publish_legacy" (in /var/www/ezp_18x/app/config/ezplatform.yml). Looked for namespace "ez_publish_legacy", found "framework", "sec
      urity", "twig", "monolog", "swiftmailer", "assetic", "doctrine", "sensio_framework_extra", "stash", "hautelook_templated_uri", "liip_imagine", "fos_http_cache", "ezpublish", "ez_search_engine_legacy",
      "ez_io", "ez_publish_rest", "ez_platformui", "ez_systems_ez_support_tools", "nelmio_cors", "white_october_pagerfanta", "oneup_flysystem", "ez_systems_platform_installer", "ez_systems_repository_forms",
      "ez_search_engine_solr", "content_on_the_fly", "bazinga_js_translation", "jms_translation"

      1. legacy-bridge.md
        3 kB
        Eduardo Fernandes
      2. legacy-bridge-default.md
        3 kB
        Eduardo Fernandes
      1. screenshot-ezpmaster.rui-2017-09-11-14-24-02.png
        169 kB

        Issue Links

          Activity

          Hide
          Roland Benedetti added a comment -

          It definitely need to go through the normal flow.
          We need to create stories for that, and save time especially for 3rd line, QA and doc.

          Show
          Roland Benedetti added a comment - It definitely need to go through the normal flow. We need to create stories for that, and save time especially for 3rd line, QA and doc.
          Hide
          André Rømcke added a comment - - edited

          Status update: We are looking into this issue, however as implied in comment above from our PM we haven't added support yet technically, so we need to handle this via our product development workflow as a Story prioritised by PM, as opposed to as a bug via thirdline.

          In short we will need to:

          • Document and if possible simplify installation instructions (with 5.4 legacy kernel, there are some existing PR's on legacy bridge that might help)
          • Document limitations in what we support with such setup (no support for xmltext/flow in platform ui, and no support for richtext and landing page. Also potentially document that support for cache clearing and search index updates across legacy to platform in some cases, and from platform to legacy in more cases, is "best effort" support as there are edge cases)
          • Certify the setup with QA
          • Release new ezpublish-legacy 5.4.x patch release for use with this setup, and if needed new releases of legacy bridge
          Show
          André Rømcke added a comment - - edited Status update: We are looking into this issue, however as implied in comment above from our PM we haven't added support yet technically, so we need to handle this via our product development workflow as a Story prioritised by PM, as opposed to as a bug via thirdline. In short we will need to: Document and if possible simplify installation instructions (with 5.4 legacy kernel, there are some existing PR's on legacy bridge that might help) Document limitations in what we support with such setup (no support for xmltext/flow in platform ui, and no support for richtext and landing page. Also potentially document that support for cache clearing and search index updates across legacy to platform in some cases, and from platform to legacy in more cases, is "best effort" support as there are edge cases) Certify the setup with QA Release new ezpublish-legacy 5.4.x patch release for use with this setup, and if needed new releases of legacy bridge
          Hide
          Bertrand Dunogier added a comment - - edited

          You remember they talked about the custom ezplatform-legacy distro from Carlos and we ended up somewhat agreeing there should be a script or simplifications to install instructions that benefitted all (also ee customers) ?

          Yes, I was part of the decision. We did rule that out because most agreed that it was simple enough with proper install instructions. Maybe it is not. The goal was to avoid a "dilution" of our brands and products that might make marketing and maintenance more complicated.

          I meant ezpublish-legacy, aka legacy kernel, you are thinking about Legacy Bundle
          Well, I was reading something else, and that is why I asked for confirmationAs far as I am concerned, the LegacyKernel refers to eZ\Publish\Core\MVC\Legacy\Kernel or LegacyKernelAware. Those are part of the "legacy kernel", either in ezpublish-kernel@5.4 or legacy-bridge. To my knowledge, ezpublish-legacy is known as "legacy". But okay, it makes more sense that way.

          Show
          Bertrand Dunogier added a comment - - edited You remember they talked about the custom ezplatform-legacy distro from Carlos and we ended up somewhat agreeing there should be a script or simplifications to install instructions that benefitted all (also ee customers) ? Yes, I was part of the decision. We did rule that out because most agreed that it was simple enough with proper install instructions. Maybe it is not. The goal was to avoid a "dilution" of our brands and products that might make marketing and maintenance more complicated. I meant ezpublish-legacy, aka legacy kernel, you are thinking about Legacy Bundle Well, I was reading something else, and that is why I asked for confirmationAs far as I am concerned, the LegacyKernel refers to eZ\Publish\Core\MVC\Legacy\Kernel or LegacyKernelAware . Those are part of the "legacy kernel", either in ezpublish-kernel@5.4 or legacy-bridge. To my knowledge, ezpublish-legacy is known as "legacy". But okay, it makes more sense that way.
          Hide
          André Rømcke added a comment -

          Updated legacy https://github.com/ezsystems/ezpublish-legacy/releases/tag/v2017.08.1

          It should now also be possible to install with dev-master version of ezpublish-kernle which is what QA does here, installing with stable/beta/rc packages continues to work like before.

          Show
          André Rømcke added a comment - Updated legacy https://github.com/ezsystems/ezpublish-legacy/releases/tag/v2017.08.1 It should now also be possible to install with dev-master version of ezpublish-kernle which is what QA does here, installing with stable/beta/rc packages continues to work like before.
          Hide
          André Rømcke added a comment - - edited

          Merged: https://github.com/ezsystems/LegacyBridge/commit/5dd5ecf14e0a909e08347b2724fd91dd6ee8f8ba

          Also updated doc PR.

          Remaining before ready for QA again:

          Show
          André Rømcke added a comment - - edited Merged: https://github.com/ezsystems/LegacyBridge/commit/5dd5ecf14e0a909e08347b2724fd91dd6ee8f8ba Also updated doc PR. Remaining before ready for QA again: https://github.com/ezsystems/LegacyBridge/pull/112 (not a must have for QA scenario, but to avoid loosing binary var files for anyone first installing Platform and then later installing legacy bridge) Legacy Bridge v1.4.0-beta1

            People

            • Assignee:
              Unassigned
              Reporter:
              Eduardo Fernandes (Inactive)
            • Votes:
              1 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: