Message of the day:
Welcome to SilverStripe | Current stable: https://goo.gl/C4F1T9 | Feature requests: https://goo.gl/EcQ34L | Community Forum: https://forum.silverstripe.org | StripeCon EU 2019! https://stripecon.eu
If you have any SilverStripe related questions, please supply the version of Framework you're using.
Did you flush? 🚽 =
It gets weirder — according to console
navscript.js IS loading… ??!! So in answer to your comment @nightjarnz there is NO error ??
That’s right @nightjarnz … the thing is that
http://HomePage.ss are on the same level, then we have the template folder containing other page types… none of which have the required .js file loading ??
suggest you'll find a console error in the other page types :>
so it's on the main
http://Page.ss 'main' template?
@nightjarnz — that’s the really weird thing… no, the script is NOT on
http://HomePage.ss… and yet it’s running there…
> “X-Forwarded-Proto” < This is how heroku provides the info
Among other bits: > SS_TRUSTED_PROXY_PROTOCOL_HEADER = “X-Forwarded-Proto” This makes SS use that protocol regardless of the lack of HTTPS/SSL on the current request.
Page is the parent class, and the parent of all other subclasses.
for local SSLs we use https://github.com/paulczar/omgwtfssl in docker-compose controlled stack of containers and though the certs are not trusted, they are better than no certs 😄
@mike_henden sounds like you've put the script in the