#Enhanced0 debatiendo

I've only just come across this when searching for a solution to the same issue in incognito mode, for the users list in setup. With the pointers here and elsewhere, it turns out that Chrome incognito does indeed block cross-domain cookies by default: 

https://support.google.com/chrome/answer/9845881?hl=en#zippy=%2Chow-incognito-mode-works

And the fix of enabling them via the site settings sliders in the URL bar does resolve it:

Hope this helps (belatedly!) anyone else looking at this. 

Keiji,

I actually ran into a Pre-install validation error using the link above. After some research, I found this has been created as a known issue and the workaround can be found here: https://issues.salesforce.com/issue/a028c00000sv9cBAAQ/nonprofit-success-packnpsp-pre-install-validation-has-failed-when-upgrading-enhanced-recurring-donationserd?_ga.

This article pointed me to this installation page, which worked for me: https://install.salesforce.org/products/npsp/8ce5f4be/enhanced-recurring-donations. Posting here in case someone else needs it as well.

Hi @Gidi Abramovich and thank you for these questions.

1. I can see the 'Redirect previous My Domain URLs to your current My Domain' option in my sandboxes, but not in production. 

Is there a reason for that? 

That option is only available after you deploy a change to your My Domain. Otherwise, there are no previous My Domain URLs to redirect. My guess is that enhanced domains are deployed in your sandbox, which is a deployed My Domain change.

The other reason this option can be unavailable is if you deployed a change and then clicked Remove Previous My Domain. (Like the checkbox, that button is only visible after you deploy a change to your My Domain.)

2. I was reading the 'Prepare for the End of Redirections for Non-Enhanced Domains' article.

I want to make sure I understand correctly. 

Our Community URL is https://[Our Company Name].force.com.

Can this URL redirection be used after Winter '25 is released on our org? (Based on what I understand, this URL redirection will stop upon Winter '25 release, but I want to be sure I understand correctly).

Your *.force.com site URL is redirected until Winter '25. Those redirections stop with that release. We recommend that all customers use the time between when they deploy enhanced domains and when those redirections stop to transition to the new site URLs. We recommend these steps:

1) To help uncover any place the old site URL is used in your org configuration, temporarily disable those redirections during testing. (You can re-enable the redirections afterwards.) See Disable Redirects for Your Previous Force.com Site URLs for more info.

2) Notify your customers/users about the new URL. Although the redirections are in place, it's an extra step in getting them to the new URL. Plus, that's part of the transition for when the old *.force.com URL isn't redirected anymore. For some high-level guidance, see Notify Users and Customers About a My Domain Change. 

3) Log My Domain Hostname Redirections and use that log to determine where your old URL is being used. This can help you encourage your visitors to update their bookmarks and links.

I hope that this helps!

@Morgyn-Britney Abbey​ I know what you've described is pretty common in general, but I'll leave specific advice for the Community (cc'ing the @Fundraising​ and #Recurring Donations​ folks). You'll be happy to know that the new #Enhanced Recurring Donations​ product allows you to modify the dollar amount (and other fields) of a Recurring Donation and set a specific "Effective Date" so the change can be applied in the future automatically. Meaning, if you get a donor calling in to increase the amount they are giving but ask for it to start in two months, you can set that up on the existing RD, and forget it. On the effective date, the change is applied. Also, only 1 future Opty is created and the totals are a bit different, so you shouldn't have any options with Fixed Length.

Check out the upgrade guide to see if updating is right for your org 🙂