XF 2.2 Force privacy policy - URL not viewable if it's a thread

Mr Lucky

Well-known member
If a privacy policy is on a thread, and the thread URL is referenced in options as the custom URL, then when forcing re-acceptance the link to the privacy policy in the acceptance notice is not working.

The notice itself dismisses if people tick the acceptance box, it's just that they can't see the policy.

It works fine with the default URL as a help page of course but I took the following to mean it should work as a thread.
We are able to detect if the route path of the configured privacy/terms URL actually matches that of the route path being accessed in the current request and allow those pages to be viewable.
I had a feeling this was something to do with the Force privacy policy agreement route whitelist box but putting the route there doesn't seem to make any difference. (And I'm not the only person having an problem with this.

Also there seems to be nothing (searhable) in the manual about this.
 
Solution
In my testing if you set the privacy policy to a custom URL which is a thread, e.g. http://example.com/threads/a-thread.123/ then any requests to that thread specifically should be allowed to go through automatically and you don't need to specify any whitelist routes. Whitelisting routes is for when there may be multiple pages involved in privacy policy/terms and rules. For example, you might have a forum with several threads which represent your various policies. You wouldn't need to whitelist the forum (because that'd be your custom URL), but you would need to whitelist all of the thread URLs that you want people to be able to view.

All I can suggest is you verify that the custom URL is exactly how it would be...

Chris D

XenForo developer
Staff member
In my testing if you set the privacy policy to a custom URL which is a thread, e.g. http://example.com/threads/a-thread.123/ then any requests to that thread specifically should be allowed to go through automatically and you don't need to specify any whitelist routes. Whitelisting routes is for when there may be multiple pages involved in privacy policy/terms and rules. For example, you might have a forum with several threads which represent your various policies. You wouldn't need to whitelist the forum (because that'd be your custom URL), but you would need to whitelist all of the thread URLs that you want people to be able to view.

All I can suggest is you verify that the custom URL is exactly how it would be generated on the forum.

This means if it's a thread the thread title in the URL should be identical to the thread title as it would be in the current URL, the custom URL should end in a trailing slash and the URL probably shouldn't include e.g. anything like /post-1234 which would be anchor to a specific post in the thread.

If you can let us know exactly what you've entered as the custom URL we may be able to verify whether it should bypass the policy acceptance page.
 
Solution

Mr Lucky

Well-known member
Solved!!!!

It was due to a redirect. I had changed the thread title (probably years ago) from Privacy to Privacy Policy, hence the URL had changed but it redirected (and with the old URL in the options and link in the footer still worked of course)

Was: https://cafesaxophone.com/threads/privacy.29426/

Now: https://cafesaxophone.com/threads/privacy-policy.29426/

So obviously the redirect does not work in the acceptance notice!
 
Top