I'll give that a try, will have the request filter as a fallback
any benefit of one over the other?
I see how you're doing that now
I have it in the PageController currently, so just a matter of getting it on all requests
thns @wmk, I'll have a peak... my use case is adding the HSTS header to all requests, CMS and non-CMS...
is there an equivalent in CMS 3 for the
HTTPMiddleware in CMS 4? not seeing anything in the docs
my guess is it's not currently normal procedure as you could have content adjusted that you don't wish to go live yet, let's say you have it in a campaign or something... moving a page (in a gridfield or in the site tree) would then publish those changes, and depending on your setup, any related objects that page "$owns"
we generally don't need to do the display logic stuff... but bringing the form over from another system, so trying to keep it consistent where we can... will be minimal js
na, a filter form for a particular class
figured as much... ya, we've stayed away from entwine in FE stuff, and don't really use it in SS anymore for CMS... we always use the module for CMS stuff, but would've made quick work of some logic on the FE if it wasn't entwine... oh well