Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Add feedback Subscribe
Product Content Marketing
Categories CMS + CMP Publishing
Created by Guest
Created on Mar 4, 2024

RELATED FEEDBACK

Enhance CMP CMS connector to support multiple sites per CMS codebase instance

Currently the first version of the CMP to CMS connector only support a scenario of one codebase to CMP instance. Therefore if a client has multiple CMP instances connected to different multisite instances in the CMS this does not work.

For example my client has the following

  • Canada - Instance of CMP, shared EMEA instance of the CMS 12 codebase

  • UK - Instance of CMP, shared EMEA instance of the CMS 12 codebase

And therefore we would want the Canada site (which has a separate site in the CMS) to connect to their CMP instance and vice versa for the UK site. I believe this would require current configuration setup in the appSetting.json to be moved to a CMS admin area that can be controlled per site and the middleware adjusted if possible.



  • Post comment
  • Guest
    Reply
    |     Mar 8, 2024

    As the overall global manager of this project, it creates sensitivity when we can only give access to the integration to one country rather than another - we will not be able to deploy this without a resolution, as it will cause internal difficulties. Could we expedite a solution?