You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i am developing on a local machine and the plugin just creates and endless loop of struggle. when i try to login the error of invalid CSFR token keeps showing, then i delete the cookies, but then of course the frontend asks for the cookies again. everytime the plugin sets a cookie, i get kicked out of the panel, and then we i try to login, it doesnt work of course, because the cookie is again present and the CSFR appears again.
is there a way to deactivate the plugin without having to remove code? would be helpful to have a variable in the config to bypass the plugin and switch back on when needed. otherwise right now i have to comment out or delete code in my php, javascript, etc
The text was updated successfully, but these errors were encountered:
Hey @squareclouds,
Well this is a late response... I hope you find a way to work with this plugin or a better alternative that works for you.
I just want to let you know that there is now a new version released, solving some issues: https://github.com/michnhokn/kirby-cookie-banner/releases/tag/1.2.0
Maybe this is also a solution for you.
hi all,
i am developing on a local machine and the plugin just creates and endless loop of struggle. when i try to login the error of invalid CSFR token keeps showing, then i delete the cookies, but then of course the frontend asks for the cookies again. everytime the plugin sets a cookie, i get kicked out of the panel, and then we i try to login, it doesnt work of course, because the cookie is again present and the CSFR appears again.
is there a way to deactivate the plugin without having to remove code? would be helpful to have a variable in the config to bypass the plugin and switch back on when needed. otherwise right now i have to comment out or delete code in my php, javascript, etc
The text was updated successfully, but these errors were encountered: