ryan Posted September 20, 2019 Posted September 20, 2019 This week’s dev branch version brings you improvements to ProcessWire’s $input->cookie API variable, plus it adds the ability to modify system URLs and paths at runtime. This post also includes some examples to demonstrate just how useful this can be— https://processwire.com/blog/posts/pw-3.0.141/ 16 1
ryan Posted September 20, 2019 Author Posted September 20, 2019 Actually I'm still working on minor details, but I'll have it posted by 5pm EST. 2
wbmnfktr Posted September 20, 2019 Posted September 20, 2019 Quote These banners remind me of how my new refrigerator came with PolarXtraFresh™ and SuperFreshyChill™ stickers prominently stuck all over the front, so I would have to acknowledge and could appreciate its technology. Indeed, I was impressed enough to relocate them as bumper stickers on my car, and while I still don't know what they mean, I feel more confident and respected on the road. ????? 8
szabesz Posted September 20, 2019 Posted September 20, 2019 1 hour ago, wbmnfktr said: PolarXtraFresh™ and SuperFreshyChill™ Thaks Ryan, for the new features and also for the entertainment, which was just as great as the one and only "youtuber's" channel I regularly watch. His similar topic: https://youtu.be/Q6emWqJOTkY?t=1017 2
netcarver Posted September 20, 2019 Posted September 20, 2019 Those sound more like brands of toothpaste or mouthwash to me.
LostKobrakai Posted September 21, 2019 Posted September 21, 2019 > If setting the cookie fails (like due to prior output) ProcessWire remembers it in the session instead, and sets it the response to the next web request (before any output). I‘m wondering if raising an error would actually be the better option. Letting a cookie creation succeed, but not actually creating one might lead to hard to understand bugs. At least the return value should indicate that creation of the cookie was delayed to the next request, even though I can‘t imagine cases where I would want that type of behaviour. 3
bernhard Posted October 3, 2019 Posted October 3, 2019 Hey @ryan I tried setting a different templates folder today but the result seems weird to me. Am I doing it wrong? I'd have expected that if I set the templates location to /site/templates/theme1 the homepage should show /site/templates/theme1/home.php but in fact it shows a 404 because /site/templates/home.php does not exist and the page is taken as not viewable... Is that expected? 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now