-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The cookie bar doesn't want to disappear definitely when I click on the OK button #84
Comments
Same issue |
Same issue (ruby 2.6.6) |
I use Ruby 2.6.6 now, same issue. I don't use turbolinks. I think it comes from the file '_consent_banner.html.erb' in views. There is this line to know if cookie bar is display or not : The problem is : 'cookies' variables is equal to a symbol :page (or :pages), so cookies['cookie_eu_consented'] is always equal to nil. How can I managed cookies to set cookies['cookie_eu_consented'] at true ? Is turbolinks mandatory ? I have seen this issue, but nothing works with me : #73 |
Hello community, terminal: |
@frikkl it doesnt work for me tho ... I think the js-cookie is the completely different thing from cookies-eu |
Sorry guys, but I just can't reproduce it. Can someone pls share me a boilerplate where I can reproduce it? I'm now testing it on Rails 5 and 6, works fine :( |
Same issue. I just checked the browser console and found some error there. |
It seems you have a problem with turbolinks, not cookie bar. Can you share a code where you use .clearCache function ? |
I just integrated the gem. No external js is added for same. Any suggestion to fix this, will be really helpful! |
Do you use turbolinks in you Rails app ? What rails version do you have ? |
I am using rails 4.2.6. Yes,Turbolinks used in my application. |
I have the same problem in production and development environment. When I click on the cookies_eu button "OK", the cookie bar disappears as expected. But if I go to another page of my website, sometimes the cookie bar appears again. Where is the problem ? I use Ruby 2.6.5 and Rails 5.2.4.1
The text was updated successfully, but these errors were encountered: