Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Feature.FormExtensions.DependencyInjection.config is breaking the Unsubscribe.aspx page on CD instance in Sitecore 10.1.2 #130

Open
dlandrysidlee opened this issue Jan 21, 2022 · 1 comment

Comments

@dlandrysidlee
Copy link

The page /sitecore modules/web/EXM/Unsubscribe.aspx(link to unsubscribe in the email sent with the EXM) returns a 500 on a CD instance.

Steps to reproduce the behavior (environment must be set with CM and CD instances):

  1. Install the module with all required config include files
  2. Send an email from the EXM module
  3. In the received email, click on the Unsubscribe link (brings you to the CD instance, o the page mentionned above)
  4. See error

After some tracking, the dependency injections from Feature.FormExtensions.DependencyInjection.config(last 3 configurators of the config) are preventing the constructor of the page from loading its services.

This is where my digging went before I decided to remove the 3 configurators from Feature.FormExtensions.DependencyInjection.config and redo the SubscribeToList submit action in my project :

  • The object that could not be retrieved was part of the services in the file \App_Config\Sitecore\Marketing.Segmentation.xMgmt\Sitecore.Marketing.Segmentation.config so, I tried adding the ContentDelivery role to the role:require attribute of the file.
  • That resulted in having an error trying to load the Master database object.
  • After some decompilation, I found out that the "module_website" does not have a ContentDatabase configured and it would cause that error; I added the web DB to test it.
  • After that change, I was still getting error trying to load the master DB object. I traced it down to one of the service from the ListManagement dependencies that was trying to load the master DB(hardcoded db name).
@markgibbons25
Copy link

Same issue as #120

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants