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
page_scripts is set to false by default. The documentation explains that you can set it to true, then use type="text/plain" and data-cookiecategory="<category>" to disable third-party scripts until consent is provided for that category. This seems to be the recommended approach.
What's not clear is how consent functionality would work with page_scripts set to false or if there are other benefits of using it that way. For example, do you have to manually manipulate your third-party script tags if going that route?
What is the improvement/update you wish to see?
page_scripts
is set tofalse
by default. The documentation explains that you can set it totrue
, then usetype="text/plain"
anddata-cookiecategory="<category>"
to disable third-partyscript
s until consent is provided for that category. This seems to be the recommended approach.What's not clear is how consent functionality would work with
page_scripts
set tofalse
or if there are other benefits of using it that way. For example, do you have to manually manipulate your third-partyscript
tags if going that route?The documentation link that states "Check manage third party scripts" is also broken.
Link the related docs page, if it exists.
https://github.com/orestbida/cookieconsent/tree/v2.9#readme
The text was updated successfully, but these errors were encountered: