Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Facebook Login successful but not showing - need to refresh the page!
GabrielVinicios
New
Hi! I'm using Vanilla 2.8.3.
On my site, when you login, whether you login to your account you already created or login via Facebook. The homepage doesn't update and still shows that that user has not logged in. You have to refresh the page for it to show.
Why is this happening?
I have tested it in many browsers, same result (Chrome, Firefox, Opera and Edge).
Thanks!
Tagged:
1
Comments
I read that this issue was fixed:
But I'm using 2.8.3 and this continues happens.
I also tried to replace the custom.js in /themes/keystone/js, for this (https://raw.githubusercontent.com/vanilla/vanilla/c1f592981d65baa2db7fb54e25a717ca23fd0b83/themes/keystone/js/custom.js), but the same continues happening.
You can access my forum in https://gvensino.com.br/comunidade/
Vanilla is wonderful and I'm enchanted. I only need social login with facebook to say this is perfect! Thank you!
This is actually a separate error, that I'm working on right now (Will be out in the 3.0 release).
We're missing a `vary: Cookie` header, so you're old page is cached and that's what your seeing. This hasn't been an issue on our hosted service, because our infrastructure was applying new cache headers on top of the base ones.
In any case the fix got merged to master this week, so you can expect a 3.0RC2 which should have the fix.
Thank you for your answer.
Is there a date for 3.0RC2 release?
Or, is there another thing I could do in my server to fix this, while the 3.0RC2 is not released?
The error has already been fixed on GitHub, so you only need to find it. looking at all closed pull requests with the search term "vary" leads to this PR:
You can see what have been changed there and change it in your files accordingly.
Thanks! It worked!
Be careful that you don't have the
AjaxFormstuff on your entry pages though. We're currently holding the RC2 because we're working through some signin page stuff that still has a couple bugs. Make sure if you picked out 2 lines they were onlyand
Don't bring along any of the other ones on there own or you will cause some issues on your sign in page. For example removing the
NO_CACHEdirective from the EntryController will cause bugs without the rest of the stuff that will be coming in RC2.Thanks for this information. Now I have corrected what I did. Thanks again!