| # |
Jul 24th 2017, 15:52 |
 banna |
Is there anything that needs to be changed on server? or it has to be done on my cakephp? I am using default function as you can see in the logout function, and not caching it anywhere |
| # |
Jul 24th 2017, 15:50 |
hmic |
make sure your cache header is setup correctly? do a temporary redirect only? |
| # |
Jul 24th 2017, 15:49 |
banna |
What I am supposed to do to overcome this problem? |
| # |
Jul 24th 2017, 15:48 |
banna |
@hmic It always happens, every time i login to a new browser |
| # |
Jul 24th 2017, 15:47 |
hmic |
banna: browser cache? as you redirect, it will directly go to where it got redirected the first time |
| # |
Jul 24th 2017, 15:44 |
slackebot |
'action' = "login")); } Second time it doesn't even go to logout action |
| # |
Jul 24th 2017, 15:44 |
banna |
I am using cakephp 2.9, On the server i can't logout after logging in second time using two different account To see the issue please visit the url - http://dev.casaparticulares.net/dashboard First login using - tjax78@gmail.com> / test4321 You won't be able to logout second time. public function logout() { $this->Cookie->delete('remember_me'); $this->Auth->logout(); $this->redirect(array('plugin' => false, 'controller' |
| # |
Jul 24th 2017, 15:27 |
hmic |
sure. it will show us the failures of the past. |
| # |
Jul 24th 2017, 15:26 |
cleptric |
I don’t agree, but I’m fine with that :slightly_smiling_face: The future will tell us more ^^ |
| # |
Jul 24th 2017, 15:26 |
hmic |
dont think this needs further discussion |
| # |
Jul 24th 2017, 15:26 |
hmic |
even today, ondrej has the php repo you use on ubuntu - everybody knows how to install from there |
| # |
Jul 24th 2017, 15:25 |
hmic |
ubuntu 18.04 will have it. thats about the time cake4 will be in the wild i guess. so every man and it's dog will have it by then. |
| # |
Jul 24th 2017, 15:24 |
hmic |
if they dont, they do not run their own server. simple as that |
| # |
Jul 24th 2017, 15:24 |
hmic |
and i said, the transition is taking place now, it will need a year to be carried out, but cake4 does too |
| # |
Jul 24th 2017, 15:24 |
cleptric |
If you know how to do it great. But not everyone does |
| # |
Jul 24th 2017, 15:23 |
hmic |
for your standalone server, it's no problem to go for current php verions |
| # |
Jul 24th 2017, 15:23 |
cleptric |
Foe example, not even Hetzner offers php 7.1 on their managed web server right now ^^ |
| # |
Jul 24th 2017, 15:23 |
hmic |
it's the hosters you have been talking about that move there |
| # |
Jul 24th 2017, 15:22 |
cleptric |
Hmm, I don’t see any needs to move to a containerised environment right now. Sure it has his benefits, but for small websites, a stand alone server is just fine. |
| # |
Jul 24th 2017, 15:22 |
hmic |
by introducting so much of bc changes/breakage in cake4, why not show the balls and go all in with the features that are available in the langugage (by then), which are relly usefull not just nice to have ones actually! |
| # |
Jul 24th 2017, 15:21 |
hmic |
so, if cake4 gets released within 2017, you might have a case. if thats not the plan *cough cough* the world will have changed by then (to the better i hope) |
| # |
Jul 24th 2017, 15:20 |
hmic |
cleptric: like i said, everybody moves to containers, needs to, no matter which frameowrk. the hosters will have adapted within a year - all of them, or gone out of business. - my prediction alone of course *not*. |
| # |
Jul 24th 2017, 15:19 |
hmic |
but, with the introduction of the BC and code breaking introduction of middlewares, the upgraded version requirement to 5.6 and things like that - you should have the balls to play the in front of the herd game to the full extend! it could very well be a losing game though. |
| # |
Jul 24th 2017, 15:19 |
cleptric |
Libsodium alone would be super awesome to have for Cake 4. But letting a lot of folks out there standing in the rain because the don’t have a php72 environment is also a bad decision |
| # |
Jul 24th 2017, 15:17 |
hmic |
to make it clear: i am *not* saying cake should get in front of the others. i very much appreciated the long term support and lifetime of the project, and beeing BC to the point of feasibility, maybe beyond even... |
| # |
Jul 24th 2017, 15:17 |
neon1024 |
Pushing the minimum PHP version up also excludes lots of other libraries |
| # |
Jul 24th 2017, 15:16 |
cleptric |
That’s ok IMO |
| # |
Jul 24th 2017, 15:15 |
cleptric |
Php 7.1, the version we picked for Cake 4, will be actively maintained until the end of 2018, with another year of security fixes. |
| # |
Jul 24th 2017, 15:15 |
hmic |
by swicthing from 5.5 to 5.6 during the 3.x lifetime alone is a break that could not be justified by your reasoning @cleptric |
| # |
Jul 24th 2017, 15:14 |
hmic |
there are real live benefints, like inoas mentioned. LOTS of them in more recent php releases! |
| # |
Jul 24th 2017, 15:12 |
hmic |
regarding hosting and php versions: by the time 4.0 will be released, *everything* will be eighter outdated and unsupported - check the php timeline alone - or be run in containers anyways! so go for php-next and keep going for php-next till beta phase starts, then switch to php-next till it's mature. cake does not move this fast. |
| # |
Jul 24th 2017, 15:12 |
jeremyharris |
maybe some examples are the theoretical url builder, the current http client |
| # |
Jul 24th 2017, 15:10 |
jeremyharris |
but keeping the query builder the way it is goes against the “make everything consistent regardless” argument |
| # |
Jul 24th 2017, 15:10 |
dereuromark |
when you dont have any IDE or framework code to see what the method is doing. |
| # |
Jul 24th 2017, 15:09 |
dereuromark |
especially when reading small code snippets either in docs or on SO or some gist somewhere. |
| # |
Jul 24th 2017, 15:09 |
jeremyharris |
is there a reason that the way the query builder looks cannot be applied to other classes? I don’t have a great example at the moment |
| # |
Jul 24th 2017, 15:09 |
dereuromark |
its super useful |
| # |
Jul 24th 2017, 15:08 |
cleptric |
We had the discussion about the query builder and decided not to touch it. That’s ok |
| # |
Jul 24th 2017, 15:07 |
inoas |
prefixing all things with set/get - even the query builder = aweful unproductive - especially when maintaining code. |
| # |
Jul 24th 2017, 15:06 |
inoas |
splitting magic setters/getters, having clear interfaces and less mixed types = really useful yes |
| # |
Jul 24th 2017, 15:06 |
cleptric |
It’s not cosmetic. It’s really useful IMO |