Hi,
We have an EPiServer CMS application (v.10.10.4.0) that we host in azure (one staging and one production environment). They are setup to use ssl bindings.
I've done the following in both our environments:
- Created a visitor group that has an GeoLocation criteria.
- Personalized a page in an content area (using the GeoLocation criteria)
- Given access to the visitor group using "Set access rights" in the admin panel (dunno if this is required?)
We're using the GeoLocationProvider that is shipped with EPiServer to try to personalize content.
We're filtering out content by using ContentArea.FilteredItems.
When I VPN to an NA server I can see that that the personalization is working in production, but it fails to do so in our staging environment. So I guess you'll be saying that there's a diff in our setup right? But I've checked every setting and it's the same as our production site (except host names, bindings etc - staging doesn't use www prefix). The code and EPiServer version is the same in both environments. The config is the same (except connectionStrings). So what am I missing?
Should the GeoLocation work (out of the box) or is there something else I need to setup in config/code to get this working? Is there like a magic button in the CMS admin I forgot to press?
I'm guessing that one part of the answer lies in the FilteredItems property, so if anyone has some deep knowledge about how the underlying code works (GetFilteredFragments, ISecurityDescriptor, IRoleSecurityDescriptor) I'd be very interested in reading your input.