Hi,
As described here: Mailings: Handling of links when changing hostname (migration or onsite), you can set a registry setting with allowed hostnames for the hash calculation of links in the mailings, so that they don't break after mgirating to Online (and you have put in a redirect at the old/OnSite domain).
I have been trying different combinations of getting this to work, but no matter what I do, I get the an error with that the link is invalid:
Example:
Customer domain is 'superoffice.label.company.nl', working link in a mailing for the current onsite environment is:
https://superoffice.label.company.nl/scripts/customer.fcgi?action=ejLink&key=2358:8915:2383:dc31c93739640ec674e393dae1ef0a275c945e7d&sai=1571556
New link in their Online environment would be:
https://online2.superoffice.com/<tenant>/CS/scripts/customer.fcgi?action=ejLink&key=2358:8915:2383:dc31c93739640ec674e393dae1ef0a275c945e7d&sai=1571556
I filled in the registry setting 358 the following CRMScript:
SearchEngine seRegUpdate;
seRegUpdate.addData("registry.value", "superoffice.label.company.nl,online2.superoffice.com");
seRegUpdate.addCriteria("registry.reg_id", "OperatorEquals", "358");
seRegUpdate.update();But accessing the link to the online environment still throws a link not valid error.
How is this supposed to work?
Alle Antworten (6)
It is supposed to work the way you have done it.
You do not need to add the online2.superoffice.com domain to the list, but it should not matter if it is there.
Are you sure that you have only one row with reg_id=358 in the Registry table?
Also, make sure that you use the domain that is in the "External URL" field from the onsite installation (if that differ from the "Internal URL").
Hi Stian,
Yes there is only one record with reg id 358
Updated it to just include the external url of the current onsite installation (which did not diff from internal url):
Sadly it still doesnt work.
And there is a row in the:
s_shipment table with id=2358
s_link table with id=8915
person table with id=2383
?
Problem found, the sample link the customer provided was from a shipment that was send just after we did the test migration.. Using a link of a shipment that is actually in the database, it does work :)