from AO’s point of view (and assuming logging is done using inline JS) you could either disable “aggregate inline JS” or exclude the inline “cookie notice”-logging JS from optimization by adding a keyword from the inline JS to the list of JS optimization exclusions @michant.
but disabling the logging addon in this plugin might make more sense indeed 😉
frank (ao dev)
Thanks for your reply Frank. The logging is done via inline JS, yes. But I dont really want to disable the inline aggregation completely. As this inline JS is done via wp_head hook there is no handle name that I can exclude, right?
Just to understand it correctly: If there is a line, let’s say
var ginger_logger_url = “<?php bloginfo(“url”); ?>”;
within this inline JS, I can exclude this whole inline JS part with just adding ginger_logger_url to the exclude js list? That would be great! For now I have completely deleted the whole “logger” addon folder, but I’m afraid it will be back with the next update.
Edit: I’m really sorry, but this thread is in the wrong place. It should be related to the “Ginger – EU Cookie Law” plugin.
-
This reply was modified 9 years, 1 month ago by
Michael.
-
This reply was modified 9 years, 1 month ago by
Michael.