Thanks Lee, this was a very simple solution to ensuring that a specific page is served over https (at the moment I have just theone document type to flag). Having the dashboard permanently visible is very useful as, for me, takes the pressure off worrying about running locally without https as it is so easy to set up on live.
Soon I will be adding a new area to the website and all pages in that area will need to be protected via https. Is the setting inherited from parent nodes (and therefore I only need to flag the restricted area node) or will I need to need to explicitly flag each document type to be https? No issue either way, just may change the way I plan things.
Are any of the settings inherited from ancestors?
Thanks Lee, this was a very simple solution to ensuring that a specific page is served over https (at the moment I have just theone document type to flag). Having the dashboard permanently visible is very useful as, for me, takes the pressure off worrying about running locally without https as it is so easy to set up on live.
Soon I will be adding a new area to the website and all pages in that area will need to be protected via https. Is the setting inherited from parent nodes (and therefore I only need to flag the restricted area node) or will I need to need to explicitly flag each document type to be https? No issue either way, just may change the way I plan things.
Many thanks.
Lotte
Hi Lotte,
The code doesn't do any inheritance/recursive look-ups, only uses the data from the current (requested) page.
So yes you'd need to specify each DocType (or Template) alias.
Cheers, Lee.
Understood. Many thanks
Lotte
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.