7
If you already installed CME and Publisher servers then try the following script to add
Enabling Add-ons Service integration with existing Content Manager servers
Example:
.\EnableAddOnService.ps1 -AddOnServiceUrl http://
localhost:83 -AccessManagementUrl http://localhost:85/access-management/connect/token -ClientId fc96aed3-b20e-4dd3-a345-
81e4393224c3 -...
1
It seems indeed that custom resolver addons are executed BEFORE any OOTB resolvers (standard and DXA)
There is currently no way to control that custom resolver addons are executed AFTER all other (OOTB) resolvers.
There is currently no way to control the execution order of multiple custom resolver addons.
We have requested fixes/enhancements with CS.
1
The solution to our problem was to change the
var pubTarget = new PublicationTarget(new TcmUri(_tcmPreview), item.Session);
To
var pubTarget = new TargetType(new TcmUri(_tcmPreview), item.Session)
Seems that in the version 9.5 PublicationTarget is not needed anymore
Only top voted, non community-wiki answers of a minimum length are eligible