Customer Portal

Get Involved. Join the Conversation.

Topic

    Dev Aditya
    Migration CP 2.0 to 3.7Answered
    Topic posted February 4, 2019 by Dev AdityaGold Trophy: 10,000+ Points 
    31 Views, 3 Comments
    Title:
    Migration CP 2.0 to 3.7
    Summary:
    Migration CP 2.0 to 3.7
    Content:

    Hi Experts,

     

    Currently we are migrating our site from CP version 2 to CP version 3 and we have completed our changes in our development environment. Now while deploying the changes to staging environment we have below queries:

     

    • Do we need to deploy all the files from Development to staging environment or do we only need to deploy the files in which we have made changes.
    • While selecting the files for staging, there are lots of standard files that are present in development but are not present is staging. Do we need to deploy the standard files as well. For example is standard files we are getting options like  cp/customer/assets/themes/mobile/images/CoBrowseLink.png. Do we need to deploy all the files.
    • How the files should be deployed. Do we have to complete all the work in development area and then deploy the changes or we can complete one page and deploy them simultaneously. For example we have fixed the ask page but answers detail page is still pending. So should we deploy the ask page and keep working on detail page or do we need to deploy them together.
    • How does the stage and production environment come into the version 3. Do we need to do anything else apart from deploying the files?

    Thanks,

    Dev

    Best Comment

    Rajan Davis

    Hi Dev,

    The gist of what I have below: try staging with your changes and if you run into issues on staging in CP 3, the errors will guide you on what you will need to change. If you don't see any errors, promoting to production should not create any issues.

    1. I would stage files that were changed first and see if any errors arise. Occasionally I have run into issues with staging and promoting on CP 3.* because of widgets not being correctly referenced/activated. I can see this being a potential issue when migrating between CP 2 and CP 3.*. Generally speaking, if you have no issues staging, you should be fine with promoting your changes to production.

    2. I do not believe you need to deploy standard files unless there are standard widgets that you are using that may require them. I would try to stage without these files and see if there are any errors that may occur if you skip the standard files.

    3. Staging and Production are essentially identical between CP 3.* and CP 2; however, where I have seen the most changes between the portal versions are how they handle widgets. CP 2 was a bit more permissive; however CP 3 requires that you activate widgets through the portal admin page. CP 3 Widgets require yaml files that declare the dependencies or explicitly declarations as what they override.

    Kind Regards,

    Raj

    Comment

     

    • Rajan Davis

      Hi Dev,

      The gist of what I have below: try staging with your changes and if you run into issues on staging in CP 3, the errors will guide you on what you will need to change. If you don't see any errors, promoting to production should not create any issues.

      1. I would stage files that were changed first and see if any errors arise. Occasionally I have run into issues with staging and promoting on CP 3.* because of widgets not being correctly referenced/activated. I can see this being a potential issue when migrating between CP 2 and CP 3.*. Generally speaking, if you have no issues staging, you should be fine with promoting your changes to production.

      2. I do not believe you need to deploy standard files unless there are standard widgets that you are using that may require them. I would try to stage without these files and see if there are any errors that may occur if you skip the standard files.

      3. Staging and Production are essentially identical between CP 3.* and CP 2; however, where I have seen the most changes between the portal versions are how they handle widgets. CP 2 was a bit more permissive; however CP 3 requires that you activate widgets through the portal admin page. CP 3 Widgets require yaml files that declare the dependencies or explicitly declarations as what they override.

      Kind Regards,

      Raj

    • Dev Aditya

      Hi Rajan,

      Thanks for your detailed answer. 

      I have follow up question on your point 2, when we are trying to stage files, we see lot of asset folder items in the list which we is being used in production but still it is saying that it does not exist in stage(Please check the screenshot attached). Only thing I can guess is- as file structure of CP files has changed, that is why it is saying that file does not exist in stage(This is just a guess, please never hesitate to correct my wrong concept). My doubt is, do we still need to migrate it?

       

      Thanks,

      Dev

    • Rajan Davis

      Hi Dev,

      I think it depends. Assets are a bit different in that the system will make a fuss that they are not staged, but they do not typically need to be staged and promoted to be used on the portal unless the file is required within a widget.

      I think the safe thing to do is stage and promote these assets; however, I think you might be okay with skipping these.

      If you run into issues, feel free to reach out.

      Kind Regards,

      Raj