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_scriptsis set tofalseby default. The documentation explains that you can set it totrue, then usetype="text/plain"anddata-cookiecategory="<category>"to disable third-partyscripts 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_scriptsset tofalseor if there are other benefits of using it that way. For example, do you have to manually manipulate your third-partyscripttags 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